IF an ICD waiver was approved and the Draft CDD is not based upon a previously validated capability requirement document, provide the capability requirement and associated capability gap information outlined for Section (3) of an ICD in addition to the content outlined in this section. In this case, follow the format for section 3 of the ICD with focus on the Program Summary (CDD Section 4), synchronization of SoS efforts across other CDDs, CPDs, and DCRs, and identification of dependencies on any legacy or future enabling capabilities. The purpose of this section is to outline the overall approach for developing and fielding one or more capability solutions to satisfy the validated capability requirements and associated capability gaps, and to identify related interdependencies which must be satisfied to provide a successful capability solution. CDD” Per JCIDS, focus on the synchronization of “Draft SoS efforts across other CDDs, CPDs, and DCRs Provide a summary of the overall program strategy for reaching full capability and, if applicable, the relationship between increments defined in the CDD. - Carefully address the considerations (e.g., technologies to be developed, other systems in the FoS or SoS, inactivation of legacy systems) that are relevant to the incremental delivery plan. - For follow-on increments, provide an update on the acquisition status of previous increments, and discuss any updates to the program strategy to reflect lessons learned from previous increments, changes in approved Service and joint concepts, CONOPS, or the DOD IEA and the solution architecture or other pertinent information.
IF an ICD waiver was approved and the Draft CDD is not based upon a previously validated capability requirement document, provide the capability requirement and associated capability gap information outlined for Section (3) of an ICD in addition to the content outlined in this section. In this case, follow the format for section 3 of the ICD Program Summary (CDD Section 4), with focus on the synchronization of SoS efforts across other CDDs, CPDs, and DCRs, and identification of dependencies on any legacy or future enabling capabilities. The purpose of this section is to outline the overall approach for developing and fielding one or more capability solutions to satisfy the validated capability requirements and associated capability gaps, and to identify related interdependencies which must be satisfied to provide a successful capability solution. “Draft CDD” Per JCIDS, focus on the synchronization of SoS efforts across other CDDs, CPDs, and DCRs Provide a summary of the overall program strategy for reaching full capability and, if applicable, the relationship between increments defined in the CDD. - Carefully address the considerations (e.g., technologies to be developed, other systems in the FoS or SoS, inactivation of legacy systems) that are relevant to the incremental delivery plan. - For follow-on increments, provide an update on the acquisition status of previous increments, and discuss any updates to the program strategy to reflect lessons learned from previous increments, changes in approved Service and joint concepts, CONOPS, or the DOD IEA and the solution architecture or other pertinent information.