| 4.4.2-4-1 Ensure bus design meets the mission performance requirements |
Phase A |
Phase B |
Phase C |
|
Pre-Phase A, as applicable, ensure the design satisfies the requirements under the conditions specified by the Design Reference Mission. There should be a realistic worst-case scenario to show that the requirements can be met with margin. Phase A onward, the derived CONOPS should be in a particular document (Flight Requirements and Ops documents) or operations working group products. Some mission concepts may not be directly translated to bus system requirements in terms of the overall mission operability. The bus system must be validated against how the components (including units, assemblies, sub-assemblies and parts) will be used for that particular application.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B
|
| 4.4.2-4-2 Ensure trade studies were conducted and the design baseline satisfies mission requirements |
Phase A |
Phase B |
Phase C |
|
Ensure that all trade studies are realizable in terms of technology used and conform to bus system requirement and physical constraints. Check that viable candidates received appropriate consideration. Ensure the analysis of alternatives has identified the baseline as the best value.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.2-4-3 Ensure bus technology readiness and risk burn-down plan have been assessed |
Phase A |
Phase B |
Phase C |
|
Ensure bus system technologies, including manufacturing, supplier readiness and programmatic readiness, are mature enough to support the development timeline. Check that the risk mitigation plans are sufficient, funded and conclude at the right time.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.2-4-4 Ensure bus hardware and software functions are described in the bus specification |
Phase A |
Phase B |
Phase C |
|
Ensure that descriptive functions for subsystems and units (including software) are detailed enough for new personnel to understand how the unit or subsystem behaves both individually and within the system.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.2-4-5 Ensure bus hardware and software are identified as heritage, modified, or new |
Phase B |
Phase C |
|
Ensure heritage qualification adequacy is documented by analysis and test
|
NA
|
NA
|
Objective Criteria for Heritage Hardware Reuse, TOR-2010(8591)-19; Reuse of Hardware and Software Products, TOR-2009(8546)-8604
|
| 4.4.2-4-6 Ensure all defined contract deliverables and relevant contractor data are complete and accurate to support design reviews |
Phase A |
Phase B |
Phase C |
|
Ensure all relevant data is readily available and delivered to support design reviews and design forums.
|
NA
|
NA
|
Space Vehicle Systems Engineering Handbook, TOR-2006(8506)-4494
|
| 4.4.2-4-7 Ensure that any potentially systemic design issues are considered for a Design Advisory |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Any design or architecture issue that has severe, systemic, or widespread consequences is a potential candidate for a Design Advisory. Design Advisories provide the community with timely and interim notification of an important design issue which may ultimately be captured in a specification or standard.
|
NA
|
NA
|
NA
|