| 1.2.1.2-4-1 Ensure assessment of user's Initial Capability Document (ICD) |
Phase 0 |
|
Ensure assessment of the user's initial capabilities related to software (documented in the Initial Capabilities Document to ensure they are complete, feasible, and clearly stated. Assess analysis of software implications, or perform such analysis if one does not exist. The software-related capabilities to be assessed include the required characteristics (qualitative and quantitative) and the DoD Architecture Framework OV-1 view.
|
NA
|
Initial Capabilities Document (ICD)
|
CJCSI 3170.01 and CJCSM 3170.01; 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-4-2 Ensure assessment of user's Capability Description Document (CDD) |
Phase 0 |
Phase A |
|
Ensure assessment of the user's capabilities related to software documented in the Capability Description Document to ensure they are complete, feasible, and clearly stated. Assess analysis of software implications, or perform such analysis if one does not exist. The software-related capabilities to be assessed include functional capabilities, Key Performance Parameters and system attributes (including thresholds and objectives), Reliability/Maintainability/ Availability, fault management, integrated HW/SW diagnostics, supportability, safety, security (information assurance), human systems integration, interoperability, net-centricity, and the following DoD Architecture Framework views: AV-1, OV-1, OV-2, OV-4, OV-5, OV-6, SV-2, SV-4, SV-5, SV-6, and TV-1.
|
NA
|
Capability Development Document (CDD); Key Performance Parameters (KPP)
|
CJCSI 3170.01 and CJCSM 3170.01; 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-4-3 Ensure assessment of user's Capability Production Document (CPD) |
Phase 0 |
Phase A |
|
Ensure assessment of the user's capabilities related to software documented in the Capability Production Document (CPD) to ensure they are complete, feasible, and clearly stated. Assess analysis of software implications, or perform such analysis if one does not exist. The software-related capabilities to be assessed include functional capabilities, KPPs and system attributes (including thresholds and objectives), Reliability/Maintainability/ Availability (RMA), fault management, integrated HW/SW diagnostics, supportability, safety, security (information assurance), human systems integration (HSI), interoperability, net-centricity, and the following DoD Architecture Framework (DoDAF) views: AV-1, OV-1, OV-2, OV-4, OV-5, OV-6, SV-2, SV-4, SV-5, SV-6, and TV-1.
|
NA
|
Capability Production Document (CPD); Key Performance Parameters (KPP)
|
CJCSI 3170.01 and CJCSM 3170.01; 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-4-4 Ensure assessment of user's System Concept of Operations (CONOPS) |
Phase 0 |
Phase A |
|
Ensure assessment of the user's System Concept of Operations (CONOPS) document from a software perspective to ensure the operational concepts: (1) are complete, feasible, and clearly stated; (2) include both nominal and off-nominal operations; (3) include system inputs and outputs, their sources, destinations, frequency and usage; (4) include operational workloads and scenarios, especially for concurrently performed functions; (5) are consistent with the specified user capabilities; and (6) include operator positions and skill levels. Assess the analysis of software implications, or perform such analysis if one does not exist.
|
NA
|
System CONOPS
|
CJCSI 3170.01 and CJCSM 3170.01; 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-4-5 Ensure assessment of Technical Requirements Document (TRD) |
Phase 0 |
Phase A |
|
Ensure assessment of the Technical Requirements Document (TRD) for the system to ensure that all necessary software-related requirements are included and that the software-related requirements are correct, complete, consistent, feasible, verifiable, clear and unambiguous. Provide software-related input into the TRD as it is developed. Assess analysis of software implications, or perform such analysis if one does not exist. The software-related requirements to be assessed include functional capabilities, KPPs (including thresholds and objectives), Reliability/Maintainability/ Availability (RMA), fault management, integrated HW/SW diagnostics, supportability, safety, security (information assurance), human systems integration (HSI), interoperability, net-centricity, ability to evolve and scalability, computer resource margins and growth requirements, and requirements derived from the Concept of Operations (CONOPS). Assess plan for completing any Term base Exchange formats (TBXs) related to software for impacts on software and the impacts if the plan is not met.
|
NA
|
System Requirements Document
|
CJCSI 3170.01 and CJCSM 3170.01; 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
|
| 1.2.1.2-4-6 Ensure assessment of government reference architecture |
Phase 0 |
Phase A |
|
Ensure assessment of the government reference architecture to ensure that the architecture is complete and feasible from a software perspective, that it supports the software-related requirements in the Technical Requirements Document (TRD), and that it appropriately implements the user's System Concept of Operations (CONOPS), that it is clearly documented, and that it has a sufficient level of detail to support costing. Provide software-related input into the government reference architecture as it is developed, including supporting Concept Design Center (CDC) studies and developing the needed OV, SV and TV DoDAF views. Assess/participate in architecture decisions affecting software to ensure they are well justified and documented. Such architecture decisions include space-ground and hardware-software trade studies and make-buy-reuse studies for newly developed software versus Commercial Off-The-Shelf (COTS), Open Source Software (OSS), or legacy reuse.
|
NA
|
System/Segment Architecture Description
|
CJCSI 3170.01 and CJCSM 3170.01; 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
|
| 1.2.1.2-4-7 Ensure assessment of Systems Engineering Plan (SEP) |
Phase 0 |
Phase A |
|
Ensure software-related input is provided to the program's Systems Engineering Plan (SEP), and ensure that software is an integral part of all software-related systems engineering processes involved in mission assurance. Assess the entire SEP for correctness, completeness, and consistency with respect to software, and for consistency with the Software Acquisition Management Plan (SWAMP).
|
NA
|
Systems Engineering Management Plan (SEMP); 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
|
| 1.2.1.2-4-8 Ensure analysis of software technology readiness |
Phase 0 |
Phase A |
|
Ensure assessment of the software Technology Readiness Assessment (TRA) which should be part of the system TRA. Ensure critical software technologies are identified, and assess their readiness levels to verify readiness for use with acceptable risk for the program. Software technologies include technology directly used in the objective system (including Commercial Off-The-Shelf [COTS]), Open Source Software (OSS), technology used in tools that produce or maintain software, and process technologies that are being applied to produce or maintain software. Ensure that the software TRA is appropriately incorporated into the system TRA. Provide software input to the TRA, if it is undergoing development.
|
NA
|
Technology Readiness Assessment (TRA)
|
TOR-2006(8506)-5749, Mission Assurance Tasks for Software; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Software Mission Assurance Chapter
|