PSP: the background Chair of Softw are Engineering CMMI: Capability Maturity Model Integration Software Engineering (originally: CMM) Prof. Dr. Bertrand Meyer From late 1980s, Software Engineering Institute March–June 2007 (At Carnegie-Mellon University, funded by the US Department of Defense) Goal: assess the maturity of the software process of an organization, especially its reproducibility Five levels of maturity: � Initial Lecture 2: The Personal Software Process � Managed � Defined � Quantitatively managed � Optimizing 2 Software Engineering, lecture 1: Personal Soft ware Process for Engineers: Introduction to PSP 2 CMMI: management visibility TSP, PSP Process Characteristics Level Management Visibility Team Software Process In Out Focus is on continuous Personal Software Process Optimizing quantitative improvement Outgrowth of CMMI work Process is measured Quantitatively In Out and controlled Managed Directs work of teams and individuals for higher quality Process is characterized for the organization and Defined In Out is proactive PSP is part of TSP Process is characterized Managed In Out for projects and is often reactive Process is unpredictable, Initial poorly controlled, and In Out reactive 3 4 Software Engineering, lecture 1: Personal Soft ware Process for Engineers: Introduction to PSP 3 Software Engineering, lecture 1: Personal Soft ware Process for Engineers: Introduction to PSP 4 About this presentation Management support This lecture describes the PSP as seen by its authors The initial TSP objective is to convince management to let the team be self-directed, meaning that it: It does not necessarily imply endorsement of every idea � Sets its own goals The symbol indicates points that seem arguable � Establishes its own roles � Decides on its development strategy � Defines its processes � Develops its plans � Measures, manages, and controls its work 5 6 Software Engineering, lecture 1: Personal Soft ware Process for Engineers: Introduction to PSP 5 Software Engineering, lecture 1: Personal Soft ware Process for Engineers: Introduction to PSP 6 1
Management support Management support Management will support you as long as you: Management will agree to your managing your own work as long as they believe that you are doing a superior job. � Strive to meet their needs To convince them of this, you must: � Provide regular reports on your work � Convince them that your plans are sound � Maintain and publish precise, accurate plans � Do quality work � Measure and track your work � Respond to changing needs � Regularly show that you are doing superior work � Come to them for help when you have problems The PSP helps you do this 7 8 Software Engineering, lecture 1: Personal Soft ware Process for Engineers: Introduction to PSP 7 Software Engineering, lecture 1: Personal Soft ware Process for Engineers: Introduction to PSP 8 PSP principles PSP essential practices The quality of a software system is determined by the quality of its worst component � Measure, track, and analyze your work The quality of a component is governed by the individual � Learn from your performance variations who developed it, and especially by the quality of the process he or she used to develop it � Incorporate lessons learned into your personal practices Every software professional is responsible for his or her personal process. Key to quality is each individual developer’s skill, commitment, and personal process discipline 9 10 Software Engineering, lecture 1: Personal Soft ware Process for Engineers: Introduction to PSP 9 Software Engineering, lecture 1: Personal Soft ware Process for Engineers: Introduction to PSP 10 What does a PSP provide? PSP fundamentals A stable, mature PSP allows you to As a personal process, PSP includes: � Estimate and plan your work � Defined steps � Meet your commitments � Forms � Resist unreasonable commitment pressures � Standards � A measurement and analysis framework for characterizing and managing your personal work You will also � A defined procedure to help improve your personal � Understand your current performance performance � Improve your expertise as a professional 11 12 Software Engineering, lecture 1: Personal Soft ware Process for Engineers: Introduction to PSP Software Engineering, lecture 1: Personal Soft ware Process for Engineers: Introduction to PSP 11 12 2
The PSP process flow A progressive approach PSP is introduced in six upward-compatible steps Requirements Requirements At each step: Planning Planning Design Design � Write one or more modules Code Code guide guide Scripts Scripts Logs Logs Logs � Gather and analyze data on your work Compile Compile Test Test Project Project � Use results to improve your personal performance summary summary Postmortem PM Project and process Project and process Finished product Finished product data summary report data summary report 13 14 Software Engineering, lecture 1: Personal Soft ware Process for Engineers: Introduction to PSP Software Engineering, lecture 1: Personal Soft ware Process for Engineers: Introduction to PSP 13 14 The steps Goals at each level PSP0: Establish a measured performance baseline TSP Team development PSP1: Make size, resource, and schedule plans PSP2 PSP2.1 PSP2: Practice defect and yield management Design templates Code reviews Design reviews PSP1.1 PSP1 Task planning Size estimating Schedule planning Test report PSP0 PSP0.1 Current process Time recording Coding standard Defect recording Size measurement Defect type standard Process improvement proposal (PIP) 15 16 Software Engineering, lecture 1: Personal Soft ware Process for Engineers: Introduction to PSP Software Engineering, lecture 1: Personal Soft ware Process for Engineers: Introduction to PSP 15 16 PSP0 PSP0 setup Objective: PSP2.1 PSP2 PSP0 is a simple, defined, personal process: � Demonstrate use of defined Design templates Code reviews Design reviews process for small programs � Incorporate basic PSP1.1 � Make a plan PSP1 Task planning measurements in process Size estimating Schedule planning Test report � Use your current design and development methods to � Minimize changes to your produce a small program PSP0 personal practices PSP0.1 Current process Time recording � Gather time and defect data on your work Coding standard Defect recording Size measurement Defect type standard Process improvement proposal (PIP) � Prepare a summary report 17 18 Software Engineering, lecture 1: Personal Soft ware Process for Engineers: Introduction to PSP Software Engineering, lecture 1: Personal Soft ware Process for Engineers: Introduction to PSP 17 18 3
Recommend
More recommend