Psp personal software process

All metrics are recorded on worksheets or templates. Finally, development tasks are identified and a project schedule is created. High level design. External specifications for each component to be constructed are developed and a component design is created. Prototypes are built when uncertainty exists. All issues are recorded and tracked. High level design review. Formal verification methods are applied to uncover errors in the design. Metrics are maintained for all important tasks and work results.

The component level design is refined and reviewed. Code is generated, reviewed, compiled, and tested. Using the measures and metrics collected, the effectiveness of the process is determined. You only have to fill in the estimates, before you start. Similarly, this section tracks how many defects you fixed during each phase. The time log sheet is intended to help you keep detailed records of how much time to the minute you spend in each of the phases.

Most of the columns should be self-explanatory. When you find a defect, you should fill in. Inject — the phase in which the defect was originally added use the phase names as given on the right, so that the automatic totals will work. Type — the type of defect; a reference to the different types is given on the right. Fix ref. This helps you keep track of whether your bug fixing activities are actually adding more bugs!

The phases of development are as follows: Planning — Informal design, thinking about the problem Design — More formal design, making design documents, taking notes about program structure, etc. Code — Actually writing code Compile — Compiling code, including time needed to get libraries, include files, makefiles, etc. 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. 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.