| 2.2.1-2-1 Ensure system and lower-level specification requirements are objectively verifiable |
Phase A |
Phase B |
|
Ensure all requirements' verification methods are captured and reviewed for completeness and proper method selection.
|
NA
|
System/Segment Specification (SSS); Configuration Item (Hardware, Software and Firmware) Requirements Specifications
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494,Program Requirements Verification chapter, Exit criteria; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Requirements Analysis Chapter
|
| 2.2.1-2-2 Ensure technical requirements document and system specification are complete and accurate |
Phase A |
Phase B |
|
Ensure all user requirements flowed down into the system/mission specification. Ensure all deficiencies and ambiguities in the detailed requirements are identified, documented and corrected. Ensure system/mission specification is placed under program level configuration control.
|
SFWC 2.1.1.2.1, SFWC 2.1.1.2.4
|
System/Segment Specification (SSS); Capability Development Document (CDD)
|
System Engineering Requirements and Products, TOR 2005(8533)-3, RevB (Also published as SMC-S-001) or equivalent; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Requirements Analysis Chapter
|
| 2.2.1-2-3 Ensure that the selected functional baseline meets all requirements with appropriate contingency and margins |
Phase A |
Phase B |
Phase C |
|
System functional baseline is established, approved, and customer/contractor concur on system/mission requirements. Functional requirements are identified and evaluated.
|
SFWC 2.1.1.3, SFWC 2.1.1.4.1
|
System/Segment Specification (SSS)
|
TOR-2004(3909)-3360 Rev 1, Systems Engineer's Major Reviews for National Security Space System Programs, SRR exit criteria
|
| 2.2.1-2-4 Ensure contractor provides justification for proposed requirement waivers, deviations, and/or deletion |
Phase A |
|
Ensure waivers, deviations, and/or deletions do not affect operations concepts, related requirements or abilities to validate and verify requirements.
|
NA
|
NA
|
TOR-2004(3909)-3360 Rev 1, Systems Engineer's Major Reviews for National Security Space System Programs, SRR exit criteria
|
| 2.2.1-2-5 Ensure inadequacies of existing capabilities or systems that the program is expected to improve or replace are identified and documented |
Phase A |
|
Ensure review of new systems' performance requirements to cover present inadequacies.
|
NA
|
NA
|
TOR-2004(3909)-3360 Rev 1, Systems Engineer's Major Reviews for National Security Space System Programs, SRR exit criteria
|
| 2.2.1-2-6 Ensure that all system requirements are defined at exit of the System Requirements Review |
Phase A |
|
Ensure at exit of system requirements review that all system requirements are frozen. Ensure the requirement documents under configuration management, and no outstanding TBD/TBR/TBS requirements exist that would significantly change the system architecture and schedule. Identify and document any requirements that are not fully defined, lien, or temporarily waived and track to completeness.
|
NA
|
Design Review Data Package; System/Segment Specification (SSS)
|
TOR-2004(3909)-3360 Rev 1, Systems Engineer's Major Reviews for National Security Space System Programs, SRR exit criteria
|
| 2.2.1-2-7 Ensure the preliminary requirements compliance matrix (requirement vs. capability matrix) is assessed |
Phase A |
|
Ensure matrix assessment covers all areas of the operational concepts. Ensure there are no waivers or deviations in any of the requirements in the matrix.
|
NA
|
Design Review Data Package
|
TOR-2004(3909)-3360 Rev 1, Systems Engineer's Major Reviews for National Security Space System Programs, SRR exit criteria
|
| 2.2.1-2-8 Ensure documentation of government imposed specifications/standards, processes, and practices to include implemented tailoring |
Phase A |
|
Ensure accepted technical baseline accurately reflects the accepted risk posture of the program. Ensure Program access to list of compliance documents on contract. Identify and document Program risk acceptance in regards to decisions made to tailor requirements in core specifications and standards.
|
NA
|
Integrated Master Plan (IMP) ; Statement of Work (SOW)
|
TOR-2004(3909)-3360 Rev 1, Systems Engineer's Major Reviews for National Security Space System Programs, SRR exit criteria
|
| 2.2.1-2-9 Ensure an unambiguous set of priorities among cost, schedule, performance, and supportability is defined |
Phase A |
|
Ensure requirements can meet cost, schedule, and supportability constraints. Ensure design/cost/performance trades which affect system requirements are coordinated with the users. Ensure direction to contractors is not made without regard to contractual limitations.
|
AFMAN 63-119 A14.2
|
NA
|
TOR-2004(3909)-3360 Rev 1, Systems Engineer's Major Reviews for National Security Space System Programs, SRR exit criteria; AFMAN 63-119 or equivalent
|
| 2.2.1-2-10 Ensure top-level program schedule encompasses consistent, integrated major milestones (SDR, PDR, CDR, IOC, FOC), identification of critical path and major schedule dependences |
Phase A |
|
Ensure the schedule is realistic, with stakeholder review and concurrence of milestones major dependences. Ensure Integrated Master Schedule is perceptive (correct events and dependences, and schedule metrics are reasonable).
|
NA
|
Integrated Master Schedule (IMS)
|
TOR-2004(3909)-3360 Rev 1, Systems Engineer's Major Reviews for National Security Space System Programs, SRR exit criteria
|
| 2.2.1-2-11 Ensure preliminary information security plan is assessed |
Phase A |
|
Ensure all security aspects of developing and deriving requirements are addressed.
|
NA
|
System Security Plan
|
TOR-2004(3909)-3360 Rev 1, Systems Engineer's Major Reviews for National Security Space System Programs, SRR exit criteria
|
| 2.2.1-2-12 Ensure operational views (OV-1/2/3, OV-6c) and technical view (TV-1), if required, are assessed |
Phase A |
|
Ensure views are reviewed by stakeholders and end users.
|
NA
|
System/Segment Architecture Description; System CONOPS; System Security Plan
|
TOR-2004(3909)-3360 Rev 1, Systems Engineer's Major Reviews for National Security Space System Programs, SRR exit criteria
|
| 2.2.1-2-13 Ensure requirement changes are efficiently modified in the contract, and flowed down to subcontractors and all affected lower-level documentation |
Phase B |
Phase C |
Phase D1 |
|
Ensure means exist for efficiently changing the contract in response to changes in systems requirements documentation. Ensure requirement changes are flowed to all affected documentation, including concepts of operations, interfaces, and Test and Evaluation Master Plan (TEMP).
|
AFMAN 63-119 A2.8
|
NA
|
AFMAN 63-119 or equivalent; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Requirements Analysis and Validation Chapter
|