| 2.1.6-1-1 Ensure the government's software risk management processes are developed and assessed |
Phase 0 |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure assessment of government's risk management process fully incorporates software. Provide input to the program risk management process if under development. Ensure the government's risk list includes the software risks that are correctly evaluated for probability of occurrence and impact, and appropriate risk mitigation actions have been taken for the identified software risks. Following contract award, continuous risk management with the contractor is recommended.
|
NA
|
Risk Management Plan
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter; SEI CMMI-ACQ; Air Force Systems Engineering Assessment Model (SEAM); SMC-S-012, Software Development Standard or equivalent
|
| 2.1.6-1-2 Ensure the government's software configuration management processes are developed and assessed |
Phase 0 |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure assessment of government's configuration management/change management processes fully incorporate software. Provide input to the program configuration management/change management processes if under development. Ensure the government's list of products to be configured includes software-related products.
|
NA
|
NA
|
SEI CMMI-ACQ; Air Force Systems Engineering Assessment Model (SEAM); SMC-S-012, Software Development Standard or equivalent
|
| 2.1.6-1-3 Ensure the government's measurement collection and analysis processes are assessed |
Phase 0 |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure assessment of government's measurement collection and analysis processes fully incorporate software. Provide input to the program measurement collection and analysis processes if under development. Ensure the government's metrics include software-related metrics, and adherence of software products to system requirements.
|
AFMAN 63-119 A15.3
|
NA
|
SEI CMMI-ACQ; Air Force Systems Engineering Assessment Model (SEAM); TOR-2012(8960)-9, Software Headlight Metrics Guidebook; and Software Measurement Standard for Space Systems; SMC-S-012, Software Development Standard; AFMAN 63-119 or equivalent
|
| 2.1.6-1-4 Ensure government software-related processes are assessed |
Phase 0 |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
Phase D3 |
|
Ensure the government program office has documented processes, e.g. Software Acquisition Management Plan (SWAMP), Systems Engineering Plan (SEP), integrate all the software-related processes that will be needed to manage the program. The relevant processes can be determined by tailoring the Capability Maturity Model Integration (CMMI)-ACQ or Systems Engineering Assessment Model (SEAM) models to the requirements and constraints of the program.
|
NA
|
NA
|
SEI CMMI-ACQ; Air Force Systems Engineering Assessment Model (SEAM); TOR-2012(8960)-9, Software Headlight Metrics Guidebook; and Software Measurement Standard for Space Systems; SMC-S-012, Software Development Standard or equivalent
|
| 2.1.6-1-5 Ensure assessment of the government's requirements management process |
Phase 0 |
Phase A |
Phase B |
Phase C |
Phase D1 |
Phase D2 |
|
Ensure assessment of the government's requirements management process to ensure that software-related requirements are fully incorporated into the process. 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; TR-2006(8550)-1; Reducing Software Acquisition Risk: Best Practices for the Early Acquisition Phases; SMC-S-012, Software Development Standard or equivalent
|