| 4.4.11-3-1 Ensure all system and space vehicle requirements are fully decomposed and appropriately allocated to the subsystem |
Phase A |
Phase B |
Phase C |
|
Ensure all system requirements defined at System Requirements Review are verifiable, requirements are decomposed into the space vehicle with subsystem design by Systems Design Review, with design feasibility demonstrated by Preliminary Design Review and design shown to meet all requirements by Critical Design Review. System specifications and subsystem specifications completed at System Design Review, preliminary completed to unit/component at Preliminary Design Review, with final at Critical Design Review.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook (TOR-2006(8506)-4494; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 4.4.11-3-2 Ensure requirements from applicable specifications and standards are identified and allocated to the subsystem |
Phase A |
Phase B |
Phase C |
|
Ensure that specification and standard requirements and any program Critical Design Review requirements that affect the Subsystem are reflected in the space vehicle requirements. Ensure all system requirements defined at System Requirements Review are verifiable, requirements are decomposed into space vehicle subsystem design by System Design Review, design feasibility demonstrated by Preliminary Design Review and design shown to meet all requirements by Critical Design Review.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Requirements Chapter; Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.11-3-3 Ensure subsystem specification requirements are completely allocated to the unit level |
Phase A |
Phase B |
Phase C |
|
Ensure all necessary units have been identified, and unit specifications are complete, according to program phase. Ensure driving unit requirements are defined by System Design Review, preliminary specifications by Preliminary Design Review and finals by Critical Design Review.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook (TOR-2006(8506)-4494; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 4.4.11-3-4 Ensure unit requirements/specifications are self compatible within the subsystem |
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
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 4.4.11-3-5 Ensure a reasonable closure plan exists for all TBR and TBD requirements, and evaluate their potential effect on the design and component selection |
Phase A |
Phase B |
Phase C |
|
Ensure all TBR and TBD requirements identified at System Design Review, are closed at Preliminary Design Review.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 4.4.11-3-6 Ensure late requirement changes are consistent with system level requirements |
Phase D1 |
|
Ensure that any late changes are properly understood in terms of root causes, corrective actions, change planning, execution, and verification. Ensure impact to design, testing, verification as well as schedule, cost and overall risk is assessed.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Requirements chapter
|
| 4.4.11-3-7 Ensure that fault path requirements are complete |
Phase C |
|
Ensure that all units in fault path are identified, ensure that requirements reflect a fault path that recognizes all units/circuits in a given path.
|
NA
|
NA
|
TOR 2009(8591)-14, Effective Fault Management Guidelines
|