In the Capability Development Document, which term describes the two values that bound system design for each performance parameter?

In the Capability Development Document, which term describes the two values that bound system design for each performance parameter?

• A. Cost and Schedule targets
• B. Verification and Validation
• C. Risk and Mitigation
• D. Thresholds and Objectives

Answer: (D)

The concept being tested is how performance parameters are bounded in a Capability Development Document to guide design decisions. For each performance parameter, two bound values define the allowable design space: thresholds and objectives. The threshold represents the minimum acceptable level of performance that must be met for the system to satisfy the requirement; if performance falls below this, the design is not acceptable. The objective represents the desired or target level of performance that the team aims to achieve, guiding design optimization and trade-offs within limits. Together, they frame what is minimally acceptable and what is ideally sought, shaping choices about architecture, resources, and risk. Other options don’t fit this framing: costs and schedules are program-level constraints rather than parameter-specific bounds; verification and validation are processes to confirm that the design actually meets requirements; risk and mitigation relate to managing potential issues rather than bounding performance per parameter.

The concept being tested is how performance parameters are bounded in a Capability Development Document to guide design decisions. For each performance parameter, two bound values define the allowable design space: thresholds and objectives. The threshold represents the minimum acceptable level of performance that must be met for the system to satisfy the requirement; if performance falls below this, the design is not acceptable. The objective represents the desired or target level of performance that the team aims to achieve, guiding design optimization and trade-offs within limits. Together, they frame what is minimally acceptable and what is ideally sought, shaping choices about architecture, resources, and risk.

Other options don’t fit this framing: costs and schedules are program-level constraints rather than parameter-specific bounds; verification and validation are processes to confirm that the design actually meets requirements; risk and mitigation relate to managing potential issues rather than bounding performance per parameter.