Software Critical Design ReviewAdd to favorites
Software Critical Design Review (CDR) should be performed at the Computer Software Configuration Item (CSCI) level for software intensive systems. The primary purpose of the software CSCI CDR is to determine if the completed detailed design meets the specified requirements established in the pertinent developmental baseline (functional/performance) specification, and the design is complete and ready to be implemented (i.e., coded and unit tested). The SRSs should be reviewed for changes and traceability to the completed detailed design. Impact of changes in requirements should be analyzed for impact to the detailed software design. Where necessary, software requirements should be reallocated and designs adjusted to be consistent and complete. Analysis should include internal and external interfaces. The verification requirements and procedures should be analyzed for consistency and completeness. 
Software CSCI designs should be analyzed for consistency with the CS&S design architecture and interfaces with other elements of the system design. Where incremental development is being used, the CSCI design should be reviewed for completeness and consistency for each increment scheduled to be completed. Design allocations between and among the planned increments should be analyzed and reviewed. 
The main exit criteria of the software CDR are: 
- Detail level software CSCI designs are established and reviewed, and are determined to be complete and ready for implementation.
- Confirmation that the software CSCI requirements, as specified in the contractor developmental baseline specifications, are satisfied by the detailed design description.
- Software CSCI test descriptions are complete.
- Draft software CSCI test procedures are complete.
- Detailed software CSCI design and interface descriptions are complete.
- Software CSCI development progress metrics are updated to reflect current development and design status.
- Software CSCI development files are established and maintained current.
- Software CSCI development estimates are updated as part of the balance and control process.
- CS&S risks (including those related to cost, schedule, and performance) have been identified and mitigation plans have been developed.
AcqLinks and References:
-  USAF Weapon Systems Software Management Guidebook – Appendix F
- Mil-STD-498 “Software Development and Documentation” – 5 Dec 1994
- MIL-STD-498 “Application and Reference Guidebook” – 3 Jan 1996
- Software Development Plan Information Outline
- Template: Software Development Plan – SPAWAR
- Website: MIL-STD-498 Software Documentation
- Website: DCMA Software Acquisition Management