Under DoD Major Capability Acquisition procedures, the update should focus on identification and analysis of AoA, developing the Acquisition Strategy, measures of effectiveness, key cost and capability trades, life-cycle cost, schedule, overall risk, and translating capability gaps into system-specific requirements. Which activity corresponds to this focus?

Under DoD Major Capability Acquisition procedures, the update should focus on identification and analysis of AoA, developing the Acquisition Strategy, measures of effectiveness, key cost and capability trades, life-cycle cost, schedule, overall risk, and translating capability gaps into system-specific requirements. Which activity corresponds to this focus?

• A. Drafting the Acquisition Plan
• B. Developing the Acquisition Program Baseline
• C. Drafting the Capability Development Document (CDD)
• D. Creating the System Functional Architecture

Answer: (C)

This focus is embodied in the Capability Development Document (CDD). The CDD is the instrument that translates capability gaps into system-specific requirements and performance parameters, and it explicitly incorporates the outputs of the AoA, the chosen Acquisition Strategy, measures of effectiveness, and the major trades between cost and capability. It also anchors life-cycle cost, schedule, and overall program risk to the system’s requirements, providing the basis for developing and validating the system design and for subsequent milestones. Other documents play important roles, but they don’t consolidate this particular set of analyses and requirements into the system-specific, testable form the CDD provides. The Acquisition Plan outlines how the program will be executed; the Acquisition Program Baseline tracks cost, schedule, and performance after program start; the System Functional Architecture describes functional relationships and interfaces. The CDD is the doc that integrates capability gaps with detailed requirements and performance parameters for system development.

This focus is embodied in the Capability Development Document (CDD). The CDD is the instrument that translates capability gaps into system-specific requirements and performance parameters, and it explicitly incorporates the outputs of the AoA, the chosen Acquisition Strategy, measures of effectiveness, and the major trades between cost and capability. It also anchors life-cycle cost, schedule, and overall program risk to the system’s requirements, providing the basis for developing and validating the system design and for subsequent milestones.

Other documents play important roles, but they don’t consolidate this particular set of analyses and requirements into the system-specific, testable form the CDD provides. The Acquisition Plan outlines how the program will be executed; the Acquisition Program Baseline tracks cost, schedule, and performance after program start; the System Functional Architecture describes functional relationships and interfaces. The CDD is the doc that integrates capability gaps with detailed requirements and performance parameters for system development.