| 4.4.12-1-1 Ensure an independent software modeling and analysis is performed |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure assessment of mission-critical hardware and software performance to determine risk involved in meeting performance requirements. Evaluate critical flight software areas with a view toward software testing using independent testing methods such as desk checking, complexity analysis, discrete event simulation, performance modeling and independent high-fidelity test beds running the contractor's code. Compare results against contractor's results. Ensure that any simulation/emulation facilities provide sufficient information to diagnose faults as these facilities may also be necessary for anomaly resolution later in the program.
|
NA
|
NA
|
TOR-2006(8506)-5749, "Mission Assurance Tasks for Software"; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter
|
| 4.4.12-1-2 Ensure Independent Verification and Validation is performed |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Perform and document an independent verification and validation analysis of the software architecture, design and code for systems that have either mission-critical functions, high-risk functions, or high levels of complexity. This task should start at the earliest requirements analysis phase, in preparation for Phase B of the acquisition cycle. Develop a verification and validation plan and approach for the software architecture, design and/or code to be analyzed. Identify tools to be applied and the resultant products that will document the assessment and its findings/recommendations from independent assessment such as Independent Program Assessment (IPA).
|
NA
|
NA
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter; IEEE Std 1012(TM)-2004, IEEE Standard for Software Verification and Validation
|
| 4.4.12-1-3 Ensure independent software technology analysis is performed |
Phase 0 |
Phase A |
|
Ensure analysis of the software-related technologies appropriate to the program, and provide recommendations as to technologies that would be beneficial is performed. Such technologies include computer hardware technologies as well as software product and process technologies. Include assessment of technology benefits and risks.
|
NA
|
NA
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter
|
| 4.4.12-1-4 Ensure software reliability/maintainability/availability analysis is performed |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure an independent analysis of software reliability, maintainability and availability is performed. Collect applicable data and use appropriate modeling techniques. Ensure software is appropriately incorporated into the system reliability, maintainability, availability analyses.
|
NA
|
NA
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter
|
| 4.4.12-1-5 Ensure software safety analysis is performed |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure an independent analysis of software safety is performed. Ensure use of appropriate software safety analysis techniques, such as fault tree analysis and failure modes and effects analysis. Ensure software is appropriately incorporated into the system safety analyses.
|
NA
|
NA
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter
|
| 4.4.12-1-6 Ensure an independent evaluation of the software system architecture that addresses the overall software system across space segments or subsystems is performed |
Phase 0 |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure an independent software architecture evaluation is performed that includes the categories of architecture fundamentals, architecture documentation, architecture evaluation framework as described in referenced ATM. Tailor the criteria in the framework according to the objectives of the evaluation, the phase of the program, and the level of required mission assurance. Evidence of the results of the evaluation may be stored in Evalica and results linked to iMAT. Brief the results to the customer and the contractor. In Phase 0, the independent software architecture evaluations potential system concepts. Phase A, a top level independent software architecture evaluation is performed . Phase B the independent architecture evaluation is performed. Phase C, the independent architecture evaluation is performed on changed areas since the earlier evaluation. Phases D1, D2, and D3, the independent architecture evaluation is performed on areas changed since Phase C.
|
NA
|
NA
|
ATM-2011(9010-61)-1, Evaluating Software Architectures in Space and Ground Systems, Rev 2: TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter
|
| 4.4.12-1-7 Ensure onboard software mission constants are validated |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure assessment of traceability between documents defining mission constant values and values loaded onto onboard processor(s). Assess tests after loading of constants by reviewing test procedures, results and test reports to ensure expected performance.
|
NA
|
NA
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software, Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter
|
| 4.4.12-1-8 Ensure assessment of onboard software qualification testing |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure assessment of the test procedures and corresponding test results to determine whether the designated requirements, or goals/objectives, have been satisfied and whether the onboard software performs as expected and meets the desired system performance.
|
NA
|
NA
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software, Mission Assurance Guide, TOR-2007(8546)-6018, Rev B , Software Mission Assurance Chapter
|
| 4.4.12-1-9 Ensure resources required for onboard software integration and qualification testing are validated |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure assessment of resources planned for use in software integration and qualification testing (simulators increasing in fidelity from simple software simulations at unit level; hardware-in-the-loop simulators using as much flight-like hardware or engineering models as early as possible; high fidelity simulators for use during the development and testing phases). Ensure that resources comply with contract-specified development standards and that project schedule does not overload resources.
|
NA
|
NA
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software, Mission Assurance Guide, TOR-2007(8546)-6018, Rev B , Software Mission Assurance Chapter
|