Software test plan review is conducted as part of the code plan review.
Alarms: Test planning is done with or after coding, resulting in a tendency to "track" the code.
Escapes: Develop and review test plan before coding starts.
Benefits: Test plans, system design, and coding will be
consistent.
System test team is comprised of representatives from software design and coding.
Alarms: User/customer representatives are not on the test team; software designers and programmers are evaluating their own efforts.
Escapes: Include system users on test team; use programmers as observers and consultants, but not as test team participants.
Benefits: System test team will unearth software
problems which can be corrected prior to acceptance test.
Verification and validation are performed as part of integration and test phase.
Alarms: Verification and validation are not performed for requirements in production design phase.
Escapes: Require verification and validation as
continuing effort from the requirements phase
through design and coding phases.
Benefits: System
design and coding will be adequately verified and validated.
Software is tested in accordance with DoD-STD-1679A.
Alarms: Design and coding walk-throughs and tests at module and subsystem levels are not required; software is considered error free if no failures occur during DoD-STD-1679A stress test.
Escapes: Establish a comprehensive program of internal review and testing for all phases of design and coding using operational personnel to review.
Benefits: Software errors will be detected during initial design coding.
"Manufacturing Plan"Best Practices: How to Avoid Surprises in the World 's Most Complicated Technical Process. Department of the Navy; Reliability, Maintainability, and Quality Assurance Directorate (NAVSO P-6071), March 1986,pp. 5-19 to 5-23
