| 4.5.6-10-1 Ensure hardware and software requirement buy-offs are completed as appropriate for the payload |
Phase D1 |
|
Ensure requirements are verified to the lowest level. Ensure any exceptions are addressed prior to approval. Ensure all requirement buy-off decisions are documented.
|
NA
|
NA
|
Space Vehicle Test and Evaluation Handbook, TOR-2011(8591)-2
|
| 4.5.6-10-2 Ensure all units and components have met their requirements and verification evidences are documented |
Phase B |
Phase C |
Phase D1 |
|
Ensure reworked units are tested in accordance with applicable specifications and standards. Ensure verification progress is tracked using the verification ledger/matrix.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook (TOR-2006(8506)-4494)
|
| 4.5.6-10-3 Ensure payload has met all of its requirements and evidences are documented |
Phase D1 |
|
Ensure that unit-to-bus system level testing verifies performance at temperatures and other environmental extremes at all levels of testing. Ensure that unit level testing stresses the unit as built to reveal issues at the lowest level of build and test. Ensure verification progress is tracked using the verification ledger/matrix.
|
NA
|
NA
|
Space Vehicle Test and Evaluation Handbook, TOR-2011(8591)-2
|
| 4.5.6-10-4 Ensure all payload development anomalies and failures are documented and dispositioned in accordance with approved processes |
Phase D1 |
|
Ensure that all components related to the anomaly are evaluated for overstress, including Acceptance Data Packages, Qualification Test Reports and raw test data when available. Ensure that any cross-program systemic issue is submitted to problem alerting processes.
|
NA
|
NA
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, ITE chapter.
|
| 4.5.6-10-5 Ensure review of all verification and corrective action data for all developed hardware and software |
Phase D1 |
|
Ensure all stakeholders review all test data and discrepancy documentation and have an opportunity to provide comments and recommendations for corrective action.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook (TOR-2006(8506)-4494; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 4.5.6-10-6 Ensure that system failure recovery modes perform as anticipated |
Phase D1 |
|
Ensure analyses and test results from system recovery and failure mode evaluations are reviewed for satellite and payload subsystems behavior as designed when encountering emergency and off-nominal scenarios (including but not limited to satellite tumbling (loss of attitude control), loss of power or heating/cooling, loss of ground commanding, processor halts, single-event upsets, etc.).
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook (TOR-2006(8506)-4494)
|
| 4.5.6-10-7 Ensure end-to-end system performance and data flow to end users meets requirements |
Phase D1 |
|
Ensure that Navigation experts review end-to-end test results and analyses provided to support end-to-end requirement verifications. Ensure that non-nominal scenarios (such as raw and processed data storage, external users, distributed or broadcast channels, and channels that require changes to data protocol) are included in the validation and verification.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook (TOR-2006(8506)-4494)
|