Authoritative but accessible information on Java programming fundamentals As one of the most popular programming languages …. Skip to main content. Start your free trial. Introduction to the Personal Software Process by. Book description This newest book from Watts Humphrey is a hands-on introduction to basic disciplines of software engineering. Show and hide more. Despite the circumstances, he managed to develop a total of 62 programs and 15 distinct versions of PSP implementations in three years.
However, many questions remained, such as how to apply CMM principles to small organisations or to the work of a small software team, because the CMM principles focused more on assuring that the management system provided full support and assistance to the development engineers.
Initially, Humphrey intended to apply CMM principles to write a small program. However, in a small group setting, Humphrey conceded that is not generally possible to have dedicated process specialists; hence, every engineer must participate at least part-time in process improvement.
Engineers can certainly benefit from a more detailed process, and it is thus required to deal overtly with actual practices in software development and to show engineers precisely how to apply the CMM process principles. As a result, the PSP was invented to convince software engineers that improvement requires change, and changing the behaviour of software engineers is a nontrivial problem.
Humphrey also asserted that the PSP design is based on the principles of consensus planning and quality, providing an internal reference point for software quality before its public release.
One of the principles also espoused by Humphrey is that every engineer is different; therefore, engineers must plan their work based on their own personal data. Occasionally, an engineer may be a doubting Thomas ; i.
Although engineers may be willing to make a few minor changes, engineers generally hold fairly closely to what has worked for them in the past, unless they can be convinced that a new method is more effective.
The second principle implied in the PSP is that engineers should use well-defined and measured processes to consistently improve their own performance. Altogether, engineers need to understand their personal performance, measures of the time they spend on each job step, defect injection and removal as well as the size of the product they produce.
Subsequently, engineers are required to produce quality products and, to do this, they must plan, measure, and track product quality; the overall message is to focus on quality from the outset of the project. 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. Time measurement: 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. PSP 1 — This level includes the planning of time and scheduling. PSP 2 — This level introduces the personal quality management ,design and code reviews.
Recommended Articles.
0コメント