2.5. Document Body. The body of an SW-ICD shall be no more than 10 pages long, including any content modified or augmented by a classified appendix, if used.

2.5.1. Section 1: Operational Context.

2.5.1.1. The purpose of this section is to provide operational context for the needed software capability. This information explains how the capability, being concept based and threat informed, contributes to the missions and activities of the joint force.

{NOTE: The term Range of Military Operations (ROMO) has been removed from Joint terminology and replaced with the term Competition Continuum. For more information and context, refer to the ‘Other Joint Documents’ folder under “Show Help” and “View Documents.” The term ROMO remains in the citation below to remain faithful to the authoritative document.”}

2.5.1.2. Describe the Range of Military Operations (ROMO) being addressed and the traceability to relevant parts of Unified Command Plan (UCP)-assigned missions, OPLANs/CONPLANs, Support for Strategic Analysis (SSA) Products, Service and Joint Concepts, CONOPS, and/or other relevant factors to the capability identified in the SW-ICD. Discuss the impact of a loss of the capability and if the loss would lead to critical mission failure.

2.5.1.3. Identify the timeframe under consideration for delivering capabilities based on input from supported/supporting CCMDs and the acquisition community. The timeframes presented must be consistent any phasing of capability proposed in Section 3 of the SW-ICD.

2.5.1.4. Identify what measurable operational outcomes are required; what effects must be produced to achieve those outcomes; how they complement the integrated joint/multinational warfighting force; and what enabling capabilities are required to achieve the desired operational outcomes.

2.5.1.5. Include the DoDAF OV-1 in this section, and where applicable, ensure high-level intelligence system connectivity and interoperability are accurately and adequately illustrated in the DoDAF OV-1.

2.5.1.5.1. Narrative in the operational context section must be consistent with the DoDAF OVs generated during prior analysis, as modified for the scope and purpose of the SW-ICD, including the DoDAF OV-1, OV-2, OV-4, and OV-5a.

2.5.1.5.2. Do not include other architecture data and associated artifacts/views in the document unless specifically needed for illustration purposes.