2.2.3. Section 3: Capability Discussion. Specify capabilities developed for the individual annex.

For reference or comparison, below is what the JCIDS Manual says for the CDD 2021 itself:

2.5.3. Section 3: Capability Discussion.

2.5.3.1. The purpose of this section is to identify the validated requirements and associated capability gaps addressed by the CDD, and to outline the results of related studies or analysis performed since validation of the requirements.

2.5.3.1.1. Narrative in the capability discussion section, especially the discussion of dependencies, is to be consistent with DoDAF SV-8 generated during prior analysis, as modified for the scope and purpose of the CDD.

2.5.3.1.2. Provide updated DoDAF CVs consistent with the CDD.

2.5.3.2. Summarize all related analyses and/or studies conducted to derive the performance attributes (KPPs, KSAs, and APAs) presented later in the CDD. Ensure the summary includes any intelligence analyses considered. Include the alternatives, objective, criteria, assumptions, recommendations, and conclusion. Ensure that final reports, or other resulting products, of studies or analyses not already present in KM/DS are uploaded for Reference purposes.

2.5.3.2.1. Provide a table that depicts the contribution this CDD makes to the fulfillment of CRs (Task/Condition/Standard) and closing of capability gaps described in the applicable ICDs, as illustrated in Figure B-7.

2.5.3.2.2. Sponsors shall provide traceability between each CR and ensure that the proposed solution is addressing the performance attribute (KPP, KSA, or APA) specified in Section 5 of the CDD.

2.5.3.3. Capability Dependencies. The DoDAF SV-8 captures all external dependencies between the capability solutions articulated in the CDD and fielded and planned capability solutions, including interactions with intelligence capabilities where appropriate over time. This provides insight into the evolution of dependencies and enablers over the planned lifecycle of the capability solution.

2.5.3.3.1. Use the narrative in this section to discuss critical dependencies, and those with known risks or other issues.

2.5.3.3.2. In SoS capability solutions, the Sponsor is responsible for ensuring that related capability solutions identified in other CDDs and DCRs, remain compatible and that the development is synchronized. These related capability solutions tie to a common ICD or set of ICDs. In cases where development of SoS capability solutions involves multiple solution Sponsors, a lead Sponsor will be identified in the associated JROCM whom will coordinate efforts across organizations.

2.5.3.4. Address whether the capability solution will be subject to any undeveloped intelligence technologies or will be affected by the deactivation of fielded intelligence programs. Consider whether this will affect the effectiveness and timely delivery of the capability solution or increment. Ensure all timeframes for any enabling or program-required/dependent intelligence capabilities (fielded and future) are consistent with the capability solution’s development schedule and planned IOC and FOC.

2.5.3.5. Additionally, if the CDD is not based on a validated JCIDS document, provide the CRs and associated capability gap information outlined for Section 3 of an ICD in addition to the content outlined in this section.