In the U.S. Department of Defense integrated acquisition lifecycle[1][2] the technical section has multiple acquisition technical reviews.[3] Technical reviews and audits assist the acquisition and the number and types are tailored to the acquisition.[4] Overall guidance flows from the Defense Acquisition Guidebook chapter 4,[5] with local details further defined by the review organizations.[6][7][8][9] Typical topics examined include adequacy of program/contract metrics, proper staffing, risks, budget, and schedule.
In NASA's engineering design life cycle, design reviews are held for technical and programmatic accountability and to authorize the release of funding to a project.[10] A design review provides an in-depth assessment by an independent team of discipline experts and managers that the design (or concept) is realistic and attainable from a programmatic and technical sense.
Design review is also required of medical device developers as part of a system of design controls described in the US Food and Drug Administration's governing regulations in 21CFR820. In 21CFR820.3(h), design review is described as "documented, comprehensive, systematic examination of the design to evaluate the adequacy of the design requirements, to evaluate the capability of the design to meet these requirements, and to identify problems". The FDA also specifies that a design review should include an independent reviewer.
Review process
The list of reviews done by an effort and the content, nature, process, and objectives any review uses vary enormously by the organization involved and the particular situation of the effort. For example, even within the U.S. Department of Defense, system requirements review cases include, for example, (1) a 5-day perusal of each individual requirement, or (2) a 2-day discussion of development plan documents allowed only after the system requirements have been approved and the development documents reviewed with formal action items required, or (3) a half-day PowerPoint with content determined by the project manager with attendance limited to high-level (non-technical) stakeholders with no output other than the PM being able to claim "SRR done".
Some of the reviews that may be done on an effort include:
Mission concept review (MCR)
The MCR affirms the mission need and examines the proposed mission's objectives and the concept for meeting those objectives.
System requirements review (SRR)
The SRR examines the functional requirements and performance requirements defined for the system and the preliminary program or project plan and ensures that the requirements and the selected concept will satisfy the mission.
Mission definition review (MDR)
See also
- Critical path method
- Engineering design process
- Systems Development Life Cycle
- Technical peer review