| 2.3.11-3-1 Ensure contractor's Systems Engineering Management Plan (SEMP) includes software that is an integral part of all software-related systems engineering processes and product |
Phase A |
Phase B |
Phase C |
|
Assess the entire SEMP for correctness, completeness, and consistency with respect to software, and for consistency with the Software Development Plan (SDP).
|
NA
|
Systems Engineering Management Plan (SEMP); Software Development Plan
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter
|
| 2.3.11-3-2 Ensure contractor's specialty engineering plans related to software mission assurance are complete |
Phase A |
Phase B |
Phase C |
|
This includes safety, Human Systems Integration (HIS), and information assurance plans. Ensure that software is an integral part of all software-related specialty engineering processes and products. Ensure the specialty engineering plans are consistent with the Systems Engineering Management Plan (SEMP) and Software Development Plan (SDP).
|
NA
|
Systems Engineering Management Plan (SEMP); Software Development Plan
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter
|
| 2.3.11-3-3 Ensure contractor's master test plan correctly incorporates software testing is into the overall test program |
Phase A |
Phase B |
Phase C |
|
Ensure that a robust software testing program is planned, and that the higher level testing appropriately includes software. Ensure that planned test beds and test facilities are sufficient to support a robust software test program, and that "Test Like You Fly" principles are addressed from a software perspective.
|
NA
|
Test and Evaluation Master Plan (TEMP)
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter
|
| 2.3.11-3-4 Ensure contractor plans for new software related technology insertion are evaluated |
Phase 0 |
Phase A |
Phase B |
Phase C |
Phase D1 |
|
Such technologies include computer hardware technologies as well as software product and process technologies. Assess the appropriateness of the technologies for use on this program, the contractor's capabilities in using the new technologies, and the feasibility of the contractor's plans for inserting the technologies into 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
|
| 2.3.11-3-5 Ensure software is appropriately included in all relevant systems engineering processes |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
|
Ensure software is appropriately included in all relevant systems engineering processes in a disciplined manner that reflects best practices and is demonstrated by appropriately documented artifacts.
|
NA
|
NA
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter
|
| 2.3.11-3-6 Ensure software-related requirements are fully incorporated into the requirements management process |
Phase 0 |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
|
Ensure that changes to software-related requirements are managed, and that impacts to software from such changes are assessed. Assure that requirements traceability is established and maintained within the requirements management process.
|
NA
|
NA
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter; CMMI-DEV
|
| 2.3.11-3-7 Ensure test processes for planning and performing higher level testing are applicable to integrated hardware-software system |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
|
Ensure test processes for planning and performing higher level testing are applicable to integrated hardware-software system (subsystem, element, segment, system). Ensure that the processes reflect best practices for integration testing and requirements verification testing and that that processes are disciplined and documented. Ensure that the processes include requirements traceability to the test procedure steps where requirements are verified. Ensure that the method for verifying each requirement is appropriate. Ensure that processes are not oriented solely to hardware, but are applicable to integrated hardware-software systems.
|
NA
|
NA
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter; CMMI-DEV
|
| 2.3.11-3-8 Ensure contractor's systems engineering and higher level test process performance associated with integrated software is evaluated |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
|
Observe performance of contractor systems engineering processes, including requirements management, and higher level test processes. Verify contractor staff performs in accordance with previously assessed contractor processes, and identify weaknesses 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; CMMI-DEV
|