The SEI CMM which is reference model for raising the maturity levels of software and predicts the most expected outcome from the next project undertaken by the organizations does not tell software developers about how to analyze, design, code, test and document the software products, but expects that the developers use effectual practices. The Personal Software Process realized that the process of individual use is completely different from that required by the team.
Personal Software Process (PSP) is the skeleton or the structure that assist the engineers in finding a way to measure and improve the way of working to a great extend. It helps them in developing their respective skills at a personal level and the way of doing planning, estimations against the plans.
Objectives of PSP :
The aim of PSP is to give software engineers with the regulated methods for the betterment of personal software development processes.
The PSP helps software engineers to:
- Improve their approximating and planning skills.
- Make promises that can be fulfilled.
- Manage the standards of their projects.
- Reduce the number of faults and imperfections in their work.
Personal Software Process recommend that the developers should structure the way to spend the time.The developer must measure and count the time they spend on different activities during the development.
PSP Planning :
The engineers should plan the project before developing because without planning a high effort may be wasted on unimportant activities which may lead to a poor and unsatisfactory quality of the result.
Levels of Personal Software Process :
Personal Software Process (PSP) has four levels-
- PSP 0 –
The first level of Personal Software Process, PSP 0 includes Personal measurement , basic size measures, coding standards.
- PSP 1 –
This level includes the planning of time and scheduling .
- PSP 2 –
This level introduces the personal quality management ,design and code reviews.
- PSP 3 –
The last level of the Personal Software Process is for the Personal process evolution.
Don’t stop now and take your learning to the next level. Learn all the important concepts of Data Structures and Algorithms with the help of the most trusted course: DSA Self Paced. Become industry ready at a student-friendly price.
- Modern Principles Of Software Development
- Software Engineering | Project size estimation techniques
- Types of Software Testing
- Software Testing | Basics
- Software Engineering | Architectural Design
- Software Engineering | Halstead’s Software Metrics
- Beta Testing | Software Testing
- Software Engineering | Debugging Approaches
- Pairwise Software Testing
- Software Engineering | COCOMO Model
- Software Engineering | Classification of Software Requirements
- Software Engineering | Classical Waterfall Model
- Software Engineering | Iterative Waterfall Model
- Software Engineering | Spiral Model
- Software Engineering | Requirements Engineering Process
- Software Engineering | Requirements Elicitation
- Software Engineering | System configuration management
- Software Engineering | Challenges in eliciting requirements
- Software Engineering | Classification of Software
- Software Engineering | Rapid application development model (RAD)
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to email@example.com. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.