The final
step was to compare the numbers and types of Tetra Release 2 defects with
the numbers of the reference line.
The effectiveness of the "prevention tool-set" was measured
in the quantity and types of defects found in the second release of the
project.
The prevention actions which were found to be effective
could then be integrated into the OSSP to improve quality and cycle time
for all the projects in MCIL.
The impact on the OSSP, including changes to Review Guidelines,
changes to the Phase Kickoffs and improved Testing Process, are considered
to be part of the PIE results.
The Expected Outcomes : The expected outcomes of the PIE
project are :
-
A framework for establishing a Defect Prevention program
in a software development environment
-
A list of improvement actions to be taken by the Tetra project
development group in order to prevent defects, including :
-
Method to number the Requirements in the SRS document
-
A Writing Strategy procedure to reduce the ambiguities in
the Requirement Specification phase
-
A utility to support/implement the Writing Strategy
-
Improved Software Requirement Specifications (SRS) template
-
Formalized Context Diagram / Feature Interface Chart for
the Requirement and Design phases
-
Improved Review Checklists for all phases of the development
life-cycle
-
Causal Analysis procedures and meeting guidelines
-
Improved Kickoff meeting templates and guidelines, for all
phases of the development process
-
Testing Strategy.
- Improved quality of the Tetra product, including
:
-
Decrease in the overall number of defects found in the various
development phases
-
Shift in the distribution of defects, by phases
-
Lower development costs
-
Shorter cycle time.
|
|
Plans & expected outcome
|
 |
|
|
Starting scenario
|
|
|
|
Implementation of the improvement actions |
