CAPM Elicitation, Modeling, and Requirement Quality

Requirement gathering on CAPM is about matching the method to the situation. The exam often gives you a scenario and asks which elicitation or modeling tool best supports understanding.

This means recognizing when user stories, use cases, workshops, interviews, observation, or other techniques are the better fit. It also means understanding why a traceability matrix or product backlog supports quality and control.

What stronger answers usually do

• choose the elicitation or modeling tool that matches the scenario
• understand that requirement quality depends on clarity, usefulness, and testability
• recognize the role of traceability or backlog structure in requirement management
• treat elicitation as discovery, not only as form filling

Common traps

• choosing the most familiar tool instead of the best-suited one
• assuming every requirement should be captured in the same format
• treating traceability as administrative overhead instead of control support
• gathering requirements without checking whether they can be validated later

CAPM judgment point

When the scenario is unclear, the stronger answer usually improves requirement quality first by using the technique that best reveals what users, stakeholders, or delivery teams actually need.