Personal software process
The Personal Software Process ( PSP ) is a method for software developers to optimize themselves and improve quality.
It was developed by Watts S. Humphrey at the Software Engineering Institute (SEI) at Carnegie Mellon University / Pittsburgh in order to give software developers a method with which they can actually implement the requirements of the Capability Maturity Model (CMM) can.
The benefit of PSP is that you learn to assess yourself better. This can be B. relate to cost estimates or to the estimation of error rates. On the other hand, there is time and discipline that you have to invest in writing down your own working hours and the errors you have observed. The comparison between the original estimate and the actual value determined later can stimulate the investigation of possible reasons for discrepancies. The observed data can provide an impetus, e.g. B. to adjust his estimates in the future, to seek further training or to look for relief early on.
PSP was originally designed as a paper and pencil method, but tools are now available.
The Team Software Process (TSP) was developed for teams .
Objectives
The PSP is intended to support the developer in achieving the following goals:
- Improving planning and cost estimation skills
- Improve the quality of their work
Tools
The following tools are intended to support the programmer in creating the metrics required for PSP:
- Leap
- Process dashboard
- PSP Eclipse plugin
- PSP Studio
- Hackystat .
literature
- Watts S. Humphrey: PSP (SM) - A Self-Improvement Process for Software Engineers . Addison-Wesley, 2005, ISBN 0-321-30549-3
- Watts S. Humphrey: Introduction to the Personal Software Process . Addison-Wesley, 1997, ISBN 0-201-54809-7
- Watts S. Humphrey: A Discipline for Software Engineering . Addison-Wesley, 1995, ISBN 0-201-54610-8