Study guides / CAPM: Certified Associate in Project Management / Analyzing & documenting requirements
Analyzing & documenting requirements
CAPM: Certified Associate in Project Management · quick review
Classifying requirements and expressing them clearly, with models that make them testable and easy to review.
The rules
- Requirement types: business (organizational goals), stakeholder (needs of a group), solution (functional and nonfunctional), transition (temporary needs such as training and data migration), plus project and quality requirements.
- Functional: what the solution does. Nonfunctional: how well (performance, security, usability, reliability).
- Good requirements are clear, concise, testable, feasible, traceable and unambiguous.
- Models: process flows, use cases, user stories, context diagrams (scope and external interfaces), data flow diagrams, entity relationship diagrams, decision tables (complex rules), state diagrams.
- Requirements are reviewed and baselined in predictive work; in adaptive work they live in the backlog and are refined continuously.
Common traps
- "Fast" or "user-friendly" isn't testable; a requirement needs a measure (for example, pages load within two seconds).
- Training users on a new system is a transition requirement, not a functional one.
How it's tested
Classifying a requirement and choosing the model that best expresses a described rule or flow.
Practise it
The full lesson, worked examples and practice questions are in Tickmark, where every answer choice is explained.
Open the full lesson