Purpose

Requirements

•     Time Recording Log (and instructions)
•     Defect Recording Log (or Defect Tally form)
•     Defect Type Standard
•     Software Specification

Planning

1. On the Time Log enter your name, date, and the name of the module you are constructing.
2. Enter zero in the LOC Start field.

Design

1. Record the start time and activity code for this phase in the Time Recording Log.
2. Read the Software Specification. If there is ambiguity, inconsistency, omission or other error, notify the author of the Specification.
3. 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.
4. This phase ends when you have a clear enough solution that you are ready to translate it into source code.
5. You may include writing any test cases in this phase, as long as they are written prior to coding.
   
6. Record the Stop time for this phase in the Time Recording Log and compute the Delta time.

Code

1. Record the start time and activity code for this phase in the Time Recording Log.
2. Write the code for the unit, translating the design into actual programming language statements. Be sure to conform to the class coding standard.
3. Record in the Defect Tally form any defects you find in your design work.
4. Type the code into the source file for your module using a text editor.  Do not use an IDE.
   
5. This phase is finished when you are ready to compile your module the first time.
   
6. Record the Stop time for this phase in the Time Recording Log and compute the Delta time.

Compile

1. Record the start time and activity code for this phase in the Time Recording Log.
2. Compile the module.
3. Repair the source code for any errors reported by the compiler.
4. 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).
5. Repeat steps B - D until the compiler reports no errors. This phase ends with the first clean compile.
6. Record the Stop time for this phase in the Time Recording Log and compute the Delta time.

Test

1. Record the start time and activity code for this phase in the Time Recording Log.
2. Execute the compiled module, providing the input data as required by the Specification.
3. Verify the correctness of your solution using whatever testing techniques you normally use.
   
4. Repair the source code for any defects you find.
5. Each change you make to the source code is recorded as a separate defect in the Defect Recording Log.
6. 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.

Copyright © 1999 by John Dalbey