With the popularity of software engineering knowledge, software engineers know that to develop high quality software, we must improve the process of software production. At present, the industry is recognized by CMU / SEI's software ability maturity model SW-CMM is the current best software process, and CMM has become an actual software process industry standard. However, although CMM provides a powerful software process improvement framework, only tells us "what should be doing", but did not tell us "what should be done", did not provide specific knowledge and skills required to achieve critical process domains.
In order to make up for this lack, Humphrey hosted the development of the individual software process (PSP). PSP is a self-sustained improvement process that can be used to control, manage, and improve personal work. It is a structured framework including software development tables, guides, and procedures. PSP is relatively independent with specific techniques (programming language, tools or design methods), which can be applied to almost any software engineering task. PSP can explain the principle of individual software process; help software engineers make an accurate plan; determine the steps to improve product quality to improve product quality; establish a benchmark for the improvement of metrics; the changes in the ability of software engineers.
There are 12 PSPs related to PSP in 18 key process areas of the CMM1.1. It is statistically related to 70% of software project development costs depending on the skill, experience and work habits of software developers. Therefore, as a software developer can accept PSP training, the upgrade of the unit software capabilities is a powerful guarantee.
CMM focuses on the macro management of software processes in the software enterprise, facing software development units, and PSP focuses on micro optimization of software processes in the enterprise, and is software developers. The two support each other, complement each other, and it is not possible.
The following is a summary of the "individual software process" reading. Extract the content of the work of its own or project group. After you test, decide whether you recommend it to everyone.
1. [Individual Software Process] process improvement
2. Time Management of [Individual Software Process]
3. [Individual Software Process] Develop Plan - Stage Program & Product Plan
4. [Individual Software Process] - Decree - Manage Time
5. [Individual Software Process] Defect Management - Defect & Defect Find Technology
6. [Individual Software Process] Defect Management - Code Review
7. [Individual Software Process] Defect Management - C Code Review Guide and Checklist 8. Defect Management of [Individual Software Process] - Coding Standard 9. [Individual Software Process] Defect Management - Defect Prediction
