The Proceedings of the Information Systems Education Conference 2000: §115 Home Papers/Indices prev (§114) Next (§116)

Paper (refereed) Information Systems Curriculum

Recommended Citation: Hirmanpour, I and S Khajenoori. Personal Software Process Technology: An Experiential Report. In The Proceedings of the Information Systems Education Conference 2000, v 17 (Philadelphia): §115.

Personal Software Process Technology: An Experiential Report

Refereed

Iraj Hirmanpour    [a1] [a2]
Department of Computing and Mathematics
Embry Riddle Aeronautical University    [u1] [u2]
Daytona Beach, Florida, USA    [c1] [c2]

Soheil Khajenoori    [a1] [a2]
Department of Computing and Mathematics
Embry Riddle Aeronautical University    [u1] [u2]
Daytona Beach, Florida, USA    [c1] [c2]

Process improvements within software development occur at three different levels: the organizational level, the project/team level, and at the individual engineer -- or personal -- level. The Software Engineering Institute (SEI) of Carnegie Mellon University has developed process improvement models tailored to each of these levels. The Capability Maturity Model (CMM)3 deals with organization issues, the Team Software Process (TSP)1, currently under validation testing, address improvements in project or team development processes, and the Personal Software Process (PSP)1. The focus of this paper is on individual software engineer's issues addressed by the PSP. The Personal Software Process (PSP) provides a framework that individual software engineers can use to define, instrument, and continuously improve their individual processes. After five years of experience in teaching PSP in both academic and industry settings, we have gained some insights into the challenges and rewards of transitioning this technology into an organization's software development practices. Our industrial experiences included work with the Motorola Paging Products Group; Boeing Corporation's Space Division and the Naval Oceanographic Office (NAVO). In this paper, we will relate our experiences with the transition of PSP technology into these three organizations. We will describe various approaches taken with industrial PSP training, and report data to validate the benefits of PSP. We will further describe some barriers to PSP training, the challenges of post-training activities, and offer conclusions about the transition process.

Keywords: personal software process, PSP, defect management, defect prevention, CMM, TSP

Read this refereed paper in Adobe Portable Document (PDF) format. (159 K bytes)
Preview this refereed paper in Plain Text (TXT) format. (24 K bytes)

CDpic
Comments and corrections to
webmaster@isedj.org