CAPM Practice: Determine how to gather requirements

Verification asks 'Are we building the thing right?' — checking requirements quality (correctness, completeness, consistency). Validation asks 'Are we building the right thing?' — confirming requirements represent actual stakeholder needs and business value.

**Why not A:** The distinction between verification and validation is not about who performs the activity. Both BAs and developers can participate in either verification or validation activities. The difference lies in what is being checked: specification quality versus alignment with real stakeholder needs.

**Why not C:** Verification and validation are not divided along functional versus non-functional lines. Both functional and non-functional requirements can be verified for quality and validated against stakeholder needs. The distinction is about checking correctness of specification versus confirming actual value delivery.

**Why not D:** The timing described is incorrect. Verification does not happen before elicitation, as requirements must exist before they can be checked for quality. Similarly, validation is not limited to after development; it can occur through prototypes and reviews during the requirements phase itself.