| 4.5.6-3-1 Ensure all system and space vehicle requirements are fully decomposed and appropriately allocated to the payload |
Phase A |
Phase B |
Phase C |
|
Ensure all system requirements defined at System Requirements Review are verifiable, and requirements are decomposed into the space vehicle and payload design by Systems Design Review. Ensure design feasibility is demonstrated by Preliminary Design Review and design shown to meet all requirements by Critical Design Review. Ensure system specifications and payload specifications are completed at System Design Review with preliminary version completed to unit/component at Preliminary Design Review and final version 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.5.6-3-2 Ensure requirements from applicable specifications and standards are identified and allocated to the payload |
Phase A |
Phase B |
Phase C |
|
Ensure that specification and standard requirements and any program critical design review requirements that affect the payload are reflected in the space system requirements. Ensure all payload requirements are defined at the system requirements review are verifiable; requirements are decomposed into space vehicle 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.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Requirements Chapter; Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.5.6-3-3 Ensure payload 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 final requirements 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.5.6-3-4 Ensure unit requirements/specifications are self compatible within the payload |
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.5.6-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.5.6-3-6 Ensure end-to-end data flow, RF requirements, and channel requirements are identified, complete, and allocated |
Phase A |
Phase B |
Phase C |
|
Ensure that allocation of program requirements to the payload subsystem and units are complete and reasonable. Ensure areas of payload risk (schedule, cost, technical) are identified and tracked regularly until risk is burned down to low/acceptable.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook (TOR-2006(8506)-4494)
|
| 4.5.6-3-7 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
|