A System Requirements Review (SRR) is a formal review conducted to ensure that system requirements have been completely and properly identified and that a mutual understanding between the government and contractor exists. It ensures that the system under review can proceed into initial systems development and that all system and performance requirements derived from the Initial Capabilities Document (ICD) or draft Capability Development Document (CDD) are defined and testable, and are consistent with cost, schedule, risk, technology readiness, and other system constraints.

Definition: The System Requirements Review (SRR) is a multi-disciplined technical review to ensure that the developer understands the system requirements and is ready to proceed with the initial system design.

Purpose of System Requirements Review (SRR)

The purpose of an SRR is to assess the system requirements captured in the system specification. This ensures that the system requirements are consistent with the approved materiel solution, Initial Capabilities Document (ICD), enabling concepts, technology maturation, maturity of interdependent systems, and available technologies identified in the Materiel Solutions Analysis (MSA) phase. An SRR is important in understanding the system performance, cost, and scheduling impacts that the defined requirements will have on a system.

System Requirements Review (SRD) Checklist

The following checklist and questions provide the user with a great place to ensure all aspects of an SRR are covered within a program. Using the checklist/questions will ensure a successful review is conducted.

Checklist: SRR Risk Assessment Checklist Pre-Award

Checklist: System Requirements Review (SRR) Checklist

Questions: System Requirements Review (SRR) Exit Questions

Completion of the System Requirements Review (SRR) should provide the following:

1. An approved system performance specification with sufficiently conservative requirements to provide for design trade space for the Engineering, Manufacturing, and Development (EMD) phase,
2. A preliminary allocation of system requirements to hardware, human, and software subsystems,
3. A preliminary Identification of all software components (tactical, support, deliverable, non-deliverable, etc.),
4. A comprehensive risk assessment for EMD,
5. An approved EMD phase Systems Engineering Plan (SEP) that addresses cost and critical path drivers, and
6. An approved Life-Cycle Sustainment Plan (LCSP) defines the product support plan and sustainment concepts with the corresponding metrics.

System Requirements Review (SRR) Item Reviews

All relevant documentation should be reviewed, including:

• Feasibility Analysis (results of technology assessments and trade studies to justify system design approach)
• System Operational Requirements
• System Maintenance Concept
• Functional Analysis (top-level block diagrams)
• Significant system design criteria (reliability, maintainability, logistics requirements, etc.)
• Draft System Specification and any initial draft Performance Item Specifications
• Systems Engineering Planning
• Test and Evaluation Master Plan (TEMP)
• Draft top-level Technical Performance Measurements (TPM)
• System design documentation (layout drawings, conceptual design drawings, selected supplier components data, etc.)

System Requirements Review (SRR) Standards

IEEE 5288.2 “Standard for Technical Reviews and Audits on Defense Programs” is the standard for technical reviews and audits to be performed throughout the acquisition life cycle for the US Department of Defense (DoD) and other defense agencies. This standard guides the DoD and contractor on what is required during an SRR.

AcqNotes Tutorial

Systems Requirements Review (SRR) Responsibilities

Program Manager (PM) responsibilities associated with an SRR include: [1]

• Approving, funding, and staffing the SRR as planned in the Systems Engineering Plan (SEP) developed by the Systems Engineer.
• Managing and approving changes to the system performance specification.
• Establishing the plan for System Functional Review (SFR) in applicable contract documents, including the SEP, Integrated Master Schedule (IMS), and Integrated Master Plan (IMP).
• Ensuring the plan includes subject matter experts to participate in each review.

Systems Engineer responsibilities associated with an SRR include:

• Ensuring all performance requirements, both explicit and derived, are defined and traceable (both directions) between requirements in the draft Capabilities Development Document (CDD) including Key Performance Parameters (KPPs), Key System Attributes (KSAs), other system attributes, and the system performance specification.
• Ensuring verification methods are identified for all system requirements.
• Ensuring risk items associated with system requirements are identified and analyzed, and mitigation plans are in place.
• Ensuring adequate plans are in place to complete the technical activities to proceed from SRR to the SFR.
• Ensuring plans to proceed to SFR allow for contingencies.
• Ensuring all interfaces are documented for the SoS and included in the performance specification

AcqLinks and References:

• [1] Defense Acquisition Guidebook (DAG) – CH 3-3.3.2 System Requirements Review
• SRR Exit Questions
• System Requirements Review Checklist
• SRR Risk Assessment Checklist Pre-Award
• NAVAIR Instruction 4355.19D – Systems Engineering Technical Review Process
• SRR Analysis Checklist – Naval Air Warfare Center
• OSD Guide to Best Practices Using Engineering Standards – April 2017
• INCOSE – SRR Document

Updated: 10/26/2022

Rank: G1