4.2.11. System Functional Review
4.2.11. System Functional Review
The System Functional Review (SFR) is held to evaluate whether the system functional baseline satisfies the end-user requirements and capability needs and whether functional requirements and verification methods support achievement of performance requirements. At completion of the SFR, the system’s functional baseline is normally taken under configuration control.
The functional baseline describes the system’s performance (functional, interoperability, and interface characteristics) and the verification required to demonstrate the achievement of those specified characteristics. It is directly traceable to the operational requirements contained in the Initial Capabilities Document (ICD) and draft Capability Development Document (CDD). The Program Manager establishes Government control of the functional baseline at the SFR and verifies it through Functional Configuration Audits (FCA) leading up to the system level FCA or the System Verification Review (SVR). For additional information, see DAG section 4.3.7. Configuration Management Process.
A successful SFR, which typically occurs during the Technology Development (TD) phase, reduces the risk of continuing the technical effort toward the Preliminary Design Review (PDR). The SFR is used to:
- Assess whether a balanced definition of the system’s major elements has been developed, including their functionality and performance requirements
- Assess whether the system functional baseline is technically achievable with regard to cost, schedule, and performance
- Confirm that the system performance specification (typically put on contract) is realistic and provides a sound technical foundation for preliminary design
- Establish functional baseline and verification criteria to be used during FCA
Roles and Responsibilities
The unique Program Manager responsibilities associated with an SFR include:
- Approve, fund, and staff the SFR as planned in the Systems Engineering Plan (SEP) developed by the Systems Engineer
- Manage and approve changes to the system performance specification
- Establish the plan to PDR in applicable contract documents including the SE Management Plan (SEMP), Integrated Master Schedule (IMS), and Integrated Master Plan (IMP)
- Ensure the plan includes independent subject matter experts to participate in each review
- Control the configuration of the Government-controlled subset of the functional baseline
- Chair the configuration control board (CCB) for the system performance specification and other documentation used to control the system functional baseline
The unique Systems Engineer responsibilities associated with an SFR include:
- Ensure adequate plans are in place to complete the necessary technical activities to proceed from SFR to PDR
- Ensure plans to proceed to PDR allow for contingencies
- Ensure all performance requirements, both explicit and derived, are defined and traceable (both directions) between requirements in the draft CDD to include Key Performance Parameters (KPPs), Key System Attributes (KSAs), other system attributes, and the system performance specification (see CJCSI 3170.01 JCIDS)
- Ensure verification methods are identified for all requirements
- Ensure risk items associated with functional requirements are identified and analyzed, and mitigation plans are in place
Inputs and Review Criteria
The SFR criteria are developed to best support the program’s technical scope and risk and are documented in the program’s SEP at Milestone A. Figure 4.2.11.F1 provides the end-to-end perspective and the integration of SE technical reviews and audits across the acquisition life cycle.
Figure 4.2.11.F1. Weapon System Development Life Cycle
Table 4.2.11.T1 defines the suggested SFR products and associated review criteria. The review should not begin until these criteria are considered met and any prior technical review is completed and its action items closed. If the program’s Technology Development Strategy (TDS) includes competing contractual efforts, an SFR should be held with each participating developer. A readiness assessment tool for SFR preparation is the DoD SFR Checklist. This is a best practice review.
Table 4.2.11.T1. SFR Products and Criteria
|
Product
|
SFR Criteria
|
|
System Functional Baseline Documentation
|
- Understood and assessed to be achievable within cost and schedule constraints
- Established functional baseline by mapping requirements to hardware, software, and human elements of the system
- Documented performance requirements traced to (draft) CDD requirements and reflecting clear linkage to the system of system (SoS) context(s) (including use in multiple operational environments)
- Documented performance requirements reflect design considerations
- Documented verification requirements, including testing, for FCA/SVR
|
|
Major System Element Definition
|
- Documented preliminary allocated requirements optimized through analyses (including functional analysis and sensitivity analysis), trade studies, and risk assessments
|
|
Risk Assessment
|
- Identified and documented risks, including ESOH mitigation measure requirements, at levels that warrant continued engineering development
|
|
Technical Plans
|
- Established detailed plan/schedule, sufficiently resourced to continue design and development
|
Outputs and Products
The Technical Review Chair determines when the review is complete. Once the products have been reviewed and approved in SFR, they provide a sound technical basis for proceeding into preliminary design.
DAG Tutorial 
