1. Overview.

1.1. The IS-CDD is a variant of the regular CDD, implementing the “IT Box” construct outlined in this section. IS-CDDs streamline the requirements process by delegating oversight and formats for subsequent documents as identified in the IS-CDD. This provides IS programs greater flexibility to incorporate evolving technologies and achieve faster acquisition.

1.2. Purpose.

1.2.1. The purpose of an IS-CDD is to facilitate efficient and timely software development efforts; IS-CDDs are not appropriate for hardware development efforts or capturing CRs that span a broad scope of hardware, software, and/or DOTmLPF-P efforts. All hardware associated with an IS-CDD must be COTS/GOTS. Hardware modifications are restricted to those necessary for integration, enhancements to meet requirements. The IS-CDD serves as the basis for validation by the validation authority identified in Enclosure A of this manual. Any streamlining of acquisition processes is at the discretion of the MDA IAW References [5] and [7].

1.3. Applicability.

1.3.1. IS-CDDs are appropriate when an IS solution is identified in an AoA as a follow-on to a traditional IS-ICD, as the Sponsor follows the deliberate JCIDS path.

1.3.2. Aside from paragraph 1.3.1 above, IS-CDDs are applicable under the same criteria as an IS-ICD, defined in Appendix B to Enclosure B of this manual.

1.3.3. See the CDD format section under Appendix B to Enclosure B of this manual for more information on IS-CDD formats.

1.3.4. In cases where the potential for use of the “IT Box” construct is unclear or in dispute, the Joint Staff Gatekeeper, in consultation with the validation authority as needed, will determine whether an CDD or IS-CDD will be used.

1.3.5. Joint C2 requirements that have a validated IS-CDD will be identified, documented, validated, prioritized, managed, and monitored IAW Reference [9].

1.3.6. Biennial FCB Review of IS Systems. For all IS programs with a valid IS- CDD, the Lead FCB shall review an update every second year following the validation. The Lead FCB will determine if the JROC or JCB should review the following items and will make appropriate recommendations for action.

1.3.6.1. Progress in delivering capability solutions within the required timeframe and available funding.

1.3.6.2. Compliance with applicable EA and data standards.

1.3.6.3. Other items as identified by the IS-CDD validation

1.4. Proponent. The proponent for this appendix is the J-8/JCD. For questions, contact J-8/JCD at (703) 695-2705.

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

1. Overview.

1.1. The CDD provides traceability to predecessor documents and validated CRs, provides supporting data for certifications and endorsements, identifies related DOTmLPF-P impacts of the proposed capability solution, and outlines projected lifecycle costs that are expected to result from pursuing the capability solution.

1.2. Purpose. The purpose of a CDD is to propose development of a materiel capability solution intended to wholly or partially satisfy approved CRs in order to close or mitigate associated capability gaps for which the DoD does not want to accept operational risk.

1.2.1. The CDD provides performance attributes (KPPs, KSAs, and APAs) to guide the development and production of one or more increments of a system. Each increment described by a CDD must provide a safe, operationally effective, suitable, and useful capability solution in the intended environment, commensurate with the investment.

1.2.2. The original CDD, including the performance attributes and other related sections, may remain valid through production requiring no additional staffing or coordination, unless there is a significant change that would require an update to the original validated CDD. In this case, a CDD Update will be required and validated by the same validation authority of the original document. Deliberate staffing and review will be used for CDD Updates in the same manner as CDDs with the exception that the only sections for review and validation will be the updated sections of the document. Sponsors may request expedited staffing for CDD Updates. Reference the CDD Update section under Appendix A of Enclosure A of this manual for more information on the staffing of CDD Update documents.

1.2.3 In cases where a predecessor document did not include a Mandatory Attribute because it was not defined or was not mandated in an earlier version of JCIDS, the Sponsor will either include the Mandatory KPP in the successor document or work with the appropriate certifying or endorsing organization to ensure the intent of the Mandatory Attribute is otherwise captured in the document.

1.2.4. The CDD serves as the basis for validation by the appropriate validation authority identified in Enclosure A of this manual.

1.3. Applicability. This appendix applies to the Joint Staff, Services, CCMDs, and other DoD Agencies.

1.4. Proponent. The proponent for this appendix is the J-8/JCD. For questions, contact J-8/JCD at (703) 695-2705.

{From Enclosure B, JCIDS Document Format}

2.0. Formatting Standards.

2.1. General Document Formats.

2.1.1. Software compatibility. Latest available version of Microsoft Office.

2.1.2. Paper size and margins. Use 8.5-inch by 11-inch pages with 1-inch margins on all sides.

2.1.3. Font. For document content, use Times New Roman or Bookman Old Style 12-point. For classification (header and footer) markings, use Arial 20- point bold. Table content, use Arial or Calibri 10-point.

2.1.4. Style. Underline paragraph headings. Use bold only for emphasis within text. Use sentence case throughout text and uppercase for proper nouns and titles.

2.1.5. Spacing/alignment. Single-space draft and final versions. Double- space between paragraphs, bullets, and between titles and text. Left align text. Center titles.

2.1.6. Paragraph Numbering and Indentation. Scientific notation or alpha- numeric.

2.1.6.1. For ICDs, if formatted alpha-numerically, indent paragraphs 0.5 inch from the left margin. Indent subparagraphs an additional 0.5 inch from the left margin. Paragraph spacing will be double spaced or set to 0 before and 12 after in MS Word.

2.1.6.2. For CDDs, it is recommended to format using scientific notation, align left with no indentation (set Word document paragraph spacing to 0 before and 12 after). Paragraph will be numbered (1, 1.1, 1.1.1, 2, etc.). This allows for better mapping of paragraphs to specifications in design reviews.

2.1.7. Page numbering. For ease of identifying sections and page counts, the first page of the main body of the document should start as page one. Front materials should be indexed with small Roman numerals, and appendices and/or annexes should start with A-1, B-1, C-1, and if used, D-1.

2.1.8. Line Numbering. To support review and staffing, draft documents will include line numbering starting at the Title Page and continuing throughout the document. Line numbering remains on draft document until validated.

2.2. Document Components. The basic components that make up a document are: i. Cover Page, ii. Validation Page, iii. Executive Summary, iv. Summary of Changes Page, v. TOC, 1. main body sections, appendices (A-1, B-1, C-1, D-1, E-1, F-1).

2.3. Appendices.

2.3.1. Only the following six appendices are allowed in the document. Additional reference documents or data may be submitted IAW procedures outlined in Enclosure B of this manual.

2.3.2. Appendix A. References. Ahead of other references provided in this appendix, provide an accessible URL for required architecture data and associated artifacts/views identified in Figure B-28 and, if applicable, Figure B-31. The URL location must be discoverable and accessible IAW Appendix H to Enclosure B of this manual.

2.3.3. Appendix B. Acronym List. List in alphabetical order, all of the acronyms only used in the document.

2.3.4. Appendix C. Glossary. As the Sponsor develops the document glossary, they may leverage applicable definitions from the DoDAF AV-2. These do not have to be identical as some terms will apply only to the document or the DoDAF architecture; however, terms that apply to both must be consistent. Definitions should first reflect use terminology from in the DOD Dictionary, if not then subsequently the Terminology Repository, both found at the DOD Terminology Webpage on the CAC-enabled Joint Electronic Library Plus “+” website - https://jdeis.js.mil/jdeis/index.jsp. Any deviation from existing DOD Dictionary terms should be explained in the glossary.

2.3.5. Appendix D. (Optional) Classified Appendix. A classified appendix may be used in cases where only a small subset of the document needs to be protected at a higher classification level. If the document is not useful without this appendix, the document is to be classified at the highest classification level contained within the document. A classified appendix’s content will count toward the document body page limits and will be indexed to align with the baseline document sections. Except where the existence of classified content cannot be acknowledged, each section of the baseline document augmented by the classified appendix will refer the reader to the classified appendix. If used, the appendix shall be provided to the Joint Staff Gatekeeper or J- 8/SAPCOORD IAW the classification of the appendix.

2.3.6. Appendix E. Cyber Survivability Risk Categories (CSRC). This appendix is used to determine the CSRC of the CR and describe cyber survivability attribute requirements IAW Annex C to Appendix G of this enclosure and the Cyber Survivability Endorsement Implementation Guide which can be found on KM/DS, Reference [4].

2.3.7. Appendix F. Electromagnetic Spectrum (EMS) Survivability Risk Category. This appendix is used to determine the EMS Survivability Risk Category and describe it IAW Annex C to Appendix G of this enclosure and the EMS Survivability Guidebook which can be found on KM/DS, Reference [4].

2.4. Classification and Releasability.

2.4.1. All documents containing classified information will display appropriate classification and releasability markings (overall and portion) IAW Reference [35]. See Appendix C to Enclosure A of this manual for impacts of classification on procedures for document submission to the Joint Staff Gatekeeper.

2.4.2. Exportability: Allied/Partner and Coalition Use. Sponsors will consider a foreign disclosure review when developing JCIDS documents that advocate for a future international acquisition program with allies and partner nations.

2.4.3. JCIDS documents and supporting data are joint information, the release of which is governed by Reference [36]. See Reference [1] for additional responsibilities related to release of JCIDS documents and other JROC-related information.