Artifacts #
What this step produces.
Requirements Documentation #
A document describing what stakeholders need and what the solution must do, each requirement being clear and testable. It is the basis for scope and design.
Requirements Management Plan #
A plan describing how requirements will be gathered, analysed, changed and tracked during the project. It sets the rules before the work grows.
Requirements Traceability Matrix #
A table linking each requirement to its source, deliverable and test. It shows what is covered and helps assess the impact of changes.
Techniques #
Techniques used in this step.
Requirements Elicitation #
Techniques such as interviews, workshops and observation for drawing out what stakeholders really need. It is used to collect requirements they cannot always state themselves.
Affinity Diagram #
Grouping many collected requirements or ideas into clusters by similarity. It brings order to a large, unsorted set.
Mind Mapping #
Drawing a central topic with branching related ideas to explore it freely. It helps reveal requirements that a plain list would miss.
Requirements Traceability Matrix Construction #
The practice of building the matrix: listing requirements, giving each a unique identifier and linking it to its source and result. It sets up tracking from the start.
