Basic PSP Process Script
Purpose
To guide you in construction of module level
programs.
Requirements
Phases
Planning
- On the Time Log enter your name, date, and the name of the
module you are constructing.
- Enter
zero in the LOC Start field.
Design
- Record the start time and activity code for this phase in the
Time Recording Log.
- Read the Software Specification. If there is ambiguity,
inconsistency, omission or other error, notify the author of the
Specification.
- When the requirements are clear, create a design of a
solution. This is any kind of outline of the solution that you
create before writing actual programming statements. For example,
a design might be a class diagram, flowchart, pseudocode, or
interaction diagrams. Record your design in whatever form you
normally use.
- This phase ends when you have a clear enough solution that you
are ready to translate it into source code.
- You may include writing any test cases in this phase, as long
as they are written prior to coding.
- Record the Stop time for this phase in the Time Recording Log
and compute the Delta time.
Code
- Record the start time and activity code for this phase in the
Time Recording Log.
- Write the code for the unit, translating the design into
actual programming language statements. Be sure to
conform to the class coding standard.
- Record in the Defect Tally form any defects you find in your
design work.
- Type the code into the source file for your module using a text
editor. Do not use an IDE.
- This phase is finished when you are ready to compile your
module the first time.
- Record the Stop time for this phase in the Time Recording Log
and compute the Delta time.
Compile
- Record the start time and activity code for this phase in the
Time Recording Log.
- Compile the module.
- Repair the source code for any errors reported by the compiler.
- Each change you make to the source code is recorded as a
separate defect in the Defect Recording Log (or Defect Tally form).
(Don't count compiler errors; multiple error messages may result from a
single defect).
- Repeat steps B - D until the compiler reports no errors. This
phase ends with the first clean compile.
- Record the Stop time for this phase in the Time Recording Log
and compute the Delta time.
Test
- Record the start time and activity code for this phase in the
Time Recording Log.
- Execute the compiled module, providing the input data as
required by the Specification.
- Verify the correctness of your solution using whatever testing
techniques you normally use.
- Repair the source code for any defects you find.
- Each change you make to the source code is recorded as a
separate defect in the Defect Recording Log.
- Repeat steps B - D until you are satisfied that the code is
correct.
Summary
Print and complete the
Project Summary Form
following these
directions.
PSP Products
- A completed software module, ready for
submission.
- Completed Time and Defect Recording Logs.
- Completed Project Summary Form.
Document History
3/27/08 JD Simplified into a "Basic" script for use
with QA challenge programs.
4/13/03 JD Revised for Spring 2003 (removed Post
Mortem phase)
Copyright © 1999 by John Dalbey