| 2.2.1-1-1 Ensure a rigorous requirements definition, allocation, and flow-down process to the unit level is implemented |
Phase A |
Phase B |
Phase C |
|
Ensure all program requirements defined at the system requirements review, are verifiable, and reflect the latest Capabilities Based Requirements Document. Ensure the requirements are decomposed, allocated and defined by systems design review, design feasibility demonstrated by the preliminary design review, and the design is shown to meet all requirements by the critical design review. Ensure the system specification and applicable interface control documents are completed at the system design review; preliminary completed to unit/component at preliminary design review; and the final at critical design review. Ensure that the requirements are fully decomposed and appropriately allocated to all subcontractors.
|
SFWC 2.1.1.4, SFWC 2.1.1.4.5; AFMAN 63-119 A13.1; AFMAN 63-119 A13.2.1
|
System Requirements Document; System Requirements Allocation Matrix; Design Review Data Package; Configuration Item (Hardware, Software and Firmware) Requirements Specifications; System/Segment Specification (SSS)
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494,Program Requirements Verification chapter; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Requirements Analysis Chapter; AFMAN 63-119 or equivalent
|
| 2.2.1-1-2 Ensure requirements from applicable specifications and standards are identified and allocated to the program as applicable |
Phase A |
Phase B |
Phase C |
|
Ensure specifications, standards and any program critical design review requirements are reflected in the space system requirements. Ensure all requirements are defined at the system requirements review are verifiable; requirements are decomposed into space vehicle and ground payload system and subsystems design by payload system design review, to the unit level with design feasibility demonstrated by preliminary design review and design shown to meet all requirements by critical design review.
|
SFWC 2.1.1.2, SFWC 3.1
|
Design Review Data Package; Configuration Item (Hardware, Software and Firmware) Requirements Specifications; System Requirements Document; Integrated Master Plan (IMP)
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 2.2.1-1-3 Ensure unit requirements/specifications are self compatible within the system |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure the unit-to-unit requirements are compatible (e.g. no contradictions and that the requirements are verifiable).
|
NA
|
Configuration Item (Hardware, Software and Firmware) Requirements Specifications
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 2.2.1-1-4 Ensure a reasonable closure plan exists for all to be resolved and to be determined requirements, and evaluate their potential effect on the design and component selection |
Phase A |
Phase B |
Phase C |
|
Ensure all to be resolved requirements are identified at payload system Design Review and closed at Preliminary Design Review.
|
NA
|
Design Review Data Package
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 2.2.1-1-5 Ensure requirements changes are flowed appropriately throughout the system's documentation |
Phase B |
Phase C |
Phase D1 |
|
Ensure all changes are properly understood in terms of source, corrective actions, change control, execution, and verification.
|
SFWC 2.1.1.1, SFWC 2.1.1.2, SFWC 3.1; AFMAN 63-119 A4.12
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Requirements chapter; AFMAN 63-119 or equivalent
|
| 2.2.1-1-6 Ensure derived system performance requirements are allocated and validated |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure the system performance is fully defined, allocated and validated in appropriate requirements documents. Ensure that derived requirements don't exceed the intent of program requirements.
|
SFWC 2.1.1.4, SFWC 3.20, SFWC 3.22, SFWC 2.1.1.4.5
|
System Requirements Allocation Matrix; System Verification and Validation Plan
|
NA
|
| 2.2.1-1-7 Ensure completeness of requirements |
Phase A |
Phase B |
|
Provide an independent trace of applicable Government(and or customer) policy and directives to the requirements set.
|
NA
|
System/Segment Specification (SSS)
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494,Program Requirements Verification chapter; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Requirements Analysis Chapter
|
| 2.2.1-1-8 Ensure system requirements are traceable, measurable, and verifiable |
Phase A |
Phase B |
|
Ensure an independent requirements trace of the system level specification to the lower level Segment specifications is performed. Ensure no orphan requirements. Ensure allocation and traceability to all interface control documents.
|
SFWC 2.1.1.2.2
|
System/Segment Specification (SSS); System Requirements Allocation Matrix
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494,Program Requirements Verification chapter; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Requirements Analysis Chapter
|
| 2.2.1-1-9 Ensure requirements for integration and deployment processes are defined |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Ensure all requirement sources, such as integration, operational concepts, deployment, site activation, and transition have traceable and allocated requirements.
|
SFWC 3.21
|
System/Segment Specification (SSS); System Test Plan
|
TOR-2013-00219, Assessing and Preparing for Operational Readiness
|