To ensure that "all requirements and designs align to business requirements" is the purpose of which task?

Question

Options

• AConduct elicitation
• BVerify requirements
• CValidate requirements
• DAssess risks

• A
  7% (4)
• B
  2% (1)
• C
  86% (49)
• D
  5% (3)

Explanation

Validating requirements (C) ensures that requirements and designs align to business requirements - meaning they solve the right problem and deliver actual business value. Validation asks "Are we building the right thing?"

• A (Conduct elicitation) is wrong because elicitation is about gathering requirements from stakeholders, not checking alignment.
• B (Verify requirements) is close but focuses on internal quality - ensuring requirements are complete, consistent, and correctly written (are we building it right?), not on business alignment.
• D (Assess risks) is wrong because risk assessment identifies threats and uncertainties, not requirement alignment.

Memory tip: Think Validate = Value to the business. Verification checks the spec; Validation checks the vision.

No community discussion yet for this question.