On the Fernway claims system, a stakeholder proposes changing an approved requirement mid-release. Before the change is accepted, the business analyst uses the traceability matrix to assess how the change will ripple through the solution. What is this activity called?
- ARequirements elicitation, gathering fresh requirements from the stakeholder who raised the proposed change
- BRequirements validation, confirming with users that the delivered solution meets the underlying business need
- CImpact analysis, using the traceability links to identify which related requirements, designs, and tests the change would affect Correct
- DSolution verification, testing that each built component conforms to its documented specification
Why A is wrong: Elicitation draws out new or clarified requirements. It is tempting because a stakeholder is involved, but here the analyst is assessing the effect of a known change, not discovering new requirements.
Why B is wrong: Validation checks that the right product was built. It is plausible because both look across the solution, but validation confirms fitness for need rather than tracing the reach of a proposed change.
Why C is correct: Impact analysis uses the matrix links to trace a proposed change to every connected requirement, design, and test, so the change board can weigh its full effect before deciding.
Why D is wrong: Verification checks that the product was built right against its spec. It is tempting because it also uses traceability, but it confirms conformance of what exists rather than forecasting the effect of a change.