| 1.2.1.2-1-1 Ensure the software portions of the government's Cost Analysis Requirements Document (or equivalent) are developed and assessed |
Phase A |
|
Ensure sufficient detail exists in the government's Cost Analysis Requirements Document (CARD) or equivalent for software. Ensure software sizing was obtained using accurate data and models and independently of the contractor(s). Ensure software cost model outputs were obtained using accurate data and models and independently of the contractor(s). Verify that sufficient detail exists in the CARD (or equivalent) to ensure that the software size, cost, and schedule are accurately estimated.
|
NA
|
Software Acquisition Management Plan (SWAMP); Cost Analysis Requirements Description (CARD)
|
DoD 5000.02; TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter
|
| 1.2.1.2-1-2 Ensure the software portions of the government's cost and schedule baseline are developed and assessed |
Phase A |
|
Ensure sufficient detail exists in the government's cost and schedule baseline for software. Provide input to the cost and schedule baseline if under development. Ensure that the software sizing was obtained using accurate data and models and independently of the contractor(s). Ensure that the software cost model outputs were obtained using accurate data and models and independently of the contractor(s). Verify that sufficient detail exists in the cost and schedule baseline to ensure that the software size, cost, and schedule are being accurately estimated.
|
NA
|
Software Acquisition Management Plan (SWAMP); Cost Analysis Requirements Description (CARD)
|
DoD 5000.02; TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter
|
| 1.2.1.2-1-3 Ensure the government's acquisition strategy is assessed for software implications |
Phase 0 |
Phase A |
|
Ensure government's acquisition strategy adequately discusses software in the program description, program office description and activities, risk areas and design considerations, acquisition approach and program structure, business and contracting strategy, and identification of potential sources. Assess the government's acquisition strategy, plans, and cost and schedule estimates to verify adequate preparation, funding, and risk identification for the software components of the program. Verify that the acquisition strategy addresses the use of legacy, and non-developmental software items (re-use, Commercial Off-The-Shelf (COTS), Open Source Software (OSS), and Government Off-The-Shelf (GOTS)). Verify that the government has identified a software maintenance strategy as part of the Integrated Logistics Planning. Provide input to define this strategy if under development.
|
NA
|
Software Acquisition Management Plan (SWAMP)
|
DoD 5000.02; TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter
|
| 1.2.1.2-1-4 Ensure the government's Software Acquisition Management Plan is developed and assessed |
Phase 0 |
Phase A |
|
Ensure government's Software Acquisition Management Plan (SWAMP) clearly and completely addresses the tasks that the government will perform in acquiring the software portions of the program. Provide input to the SWAMP if under development. Verify that the SWAMP addresses the required staffing and other resources needed to ensure the executability of the software acquisition. Ensure that the SWAMP includes timelines, responsible organizations, and required resources for identified tasks. Ensure that the SWAMP includes measurements and analysis for all government activities. Ensure that the SWAMP addresses corrective action for software-related issues. Ensure that the government documents and provides rationale for any tasks that are tailored out of the process.
|
NA
|
Software Acquisition Management Plan (SWAMP)
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter
|