360 likes | 556 Views
Introduction to The Personal Software Process and The Team Software Process. Dr. Kaan Kurtel. The Baseline Personal Process. What Is a Process?. A process is the sequence of steps required to do a job.
E N D
Introduction toThe Personal Software ProcessandThe Team Software Process Dr. Kaan Kurtel
What Is a Process? • A process is the sequence of steps required to do a job. • The software process establishes the technical and management framework for applying methods, tools, and people to the software task. • The process definition; • Identifies roles, • specifies tasks, • establishes measures, • provides exit and entry criteria for the major steps. • As better methods are found, they can be incorporated into the process definition. • This helps all teams learn and it shows new teams how to take advantage of the experiences of their predecessors.
The PSP0 Proces • PSP0 is a simple, defined, personal process. • Make a plan. • Use your current design and development methods to produce a small program. • Gather time and defect data on your work. • Prepare a summary report.
Why Forms Are Helpful? • Determine what is to be done. • Decide how to do it. • Do it. • Check to make sure it is correct. • Fix any problems. • Deliver the final results.
The PSP0 Process Elements Requirements Planning Development Design Code Compile Test Postmortem Finished product, Process data, Summary report
The PSP0 Baseline Process Flows Requirements Planning guide Design Logs Logs Time and defect logs Code Process Scripts Development Compile Test Project Plan Summary Postmortem Finished product Project and process summary report
PSP0 Process Script • Watts S. Humphrey, “PSP: A Self-Improvement Process for Software Engineers”, Addison Wesley Professional, 2005.
PSP0 Planning Script • Watts S. Humphrey, “PSP: A Self-Improvement Process for Software Engineers”, Addison Wesley Professional, 2005.
PSP0 Development Script • Watts S. Humphrey, “PSP: A Self-Improvement Process for Software Engineers”, Addison Wesley Professional, 2005.
PSP0 Postmortem Script • Watts S. Humphrey, “PSP: A Self-Improvement Process for Software Engineers”, Addison Wesley Professional, 2005.
PSP0 Measures • PSP0 has two measures: • The time spent per phase • The defects found per phase
Time Recording • Record the same basic data: • The project or program being worked on • The process phase for the task • The date and time you started and finished working on the task • Any interruption time • The net or delta time worked on the task • Comments
The PSP0 Time Recording Log • Watts S. Humphrey, “PSP: A Self-Improvement Process for Software Engineers”, Addison Wesley Professional, 2005.
Time Recording Log Instructions • Watts S. Humphrey, “PSP: A Self-Improvement Process for Software Engineers”, Addison Wesley Professional, 2005.
The PSP Time Recording Log Ali Caliskan GraphColor 20.01.2011 9:10 9:47 9 + 7 21 Boss + Phone
PSP Defect Recording Log • Watts S. Humphrey, “PSP: A Self-Improvement Process for Software Engineers”, Addison Wesley Professional, 2005.
Defect Recording Ali Caliskan 20.01.2011 GraphColor 20 1 C M 1 “;” missing 20 2 C M 1 Not decl. var
Watts S. Humphrey, “PSP: A Self-Improvement Process for Software Engineers”, Addison Wesley Professional, 2005.
PSP Defect Recording Log Instructions • Watts S. Humphrey, “PSP: A Self-Improvement Process for Software Engineers”, Addison Wesley Professional, 2005.
Defect Types • Watts S. Humphrey, “PSP: A Self-Improvement Process for Software Engineers”, Addison Wesley Professional, 2005.
The PSP0 Project Plan Summary • Time in phase • Defects injected • Defects removed
The PSP0 Project Plan Summary • Watts S. Humphrey, “PSP: A Self-Improvement Process for Software Engineers”, Addison Wesley Professional, 2005.
PSP0 Plan Summary Instructions • Watts S. Humphrey, “PSP: A Self-Improvement Process for Software Engineers”, Addison Wesley Professional, 2005.
Summary • Three forms: • Time recording log • Defect recording log + defect type standartd • Project plan summary
References • Watts S. Humphrey, “PSP: A Self-Improvement Process for Software Engineers”, Addison Wesley Professional, 2005. • DAAD project “Joint Course on Software Engineering”, ww2.informatik.hu-berlin.de/swt/ intkoop/daad/herc2005/talks/PSP.ppt, 2005. • Watts S. Humphrey, “Three Dimensions of Process Improvement,” CROSSTALK, February 1998.