(a) Guided by the ICD, the AoA (for ACAT I/LA programs), and
technology development activities, the CDD captures the information
necessary to develop a proposed program(s), normally using an evolutionary
acquisition strategy. The CDD outlines an affordable increment of
capability. An increment is a militarily useful and supportable operational
capability that can be effectively developed, produced or acquired, deployed
and sustained. Each increment of capability will have its own set of
attributes and associated performance values with thresholds and objectives
established by the sponsor with input from the user. The CDD supports the
Milestone B acquisition decision.
(b) The CDD provides the operational performance attributes,
including supportability, necessary for the acquisition community to design
the proposed system, including key performance parameters (KPP) that will
guide the development, demonstration and testing of the current increment.
Because the operational performance attributes provided in a CDD apply only
to a single increment of a program's development, the KPPs shall apply only
to the current increment (or to the entire program when only a single
increment is required to achieve full capability). The AoA should be
reviewed for its relevance for each program increment requiring a Milestone
B decision and, if necessary, the AoA should be updated or a new one
(c) In addition to describing the current increment, the CDD will
outline the overall strategy to develop the full or complete capability. For
evolutionary acquisition programs, the CDD will outline the increments
delivered to date (if any), the current increment and future increments (if
any) of the acquisition program to deliver the full operational capability.
In the case of FoS and SoS solutions, the CDD will reference the originating
ICD, identify other CDDs/CPDs that are required for full realization of the
capability(s) and describe the synchronization required between programs.
The CDD will also reference any additional overarching DOTMLPF changes
necessary to meld the FoS and SoS into an effective capability.
(d) The CDD must be validated and approved before each Milestone
B decision. If the performance characteristics of subsequent increments of a
CDD can be captured in an annex, then it may be appropriate to update an
existing CDD for each increment rather than rewriting the entire document.
The CDD is described in detail in reference