Artifacts #
What this step produces.
Detailed Requirements Documentation #
A written description of what the product must do and the conditions it must meet, detailed enough to design and test from. It is the team's shared source of truth.
Elicitation Session Records #
Notes and outcomes from each requirements session: who attended, what was said, and what was agreed or left open. They give evidence for where each requirement came from.
Requirements Baseline #
The agreed and approved set of requirements at a point in time. Later changes are made only through change control, so everyone knows what was promised.
Techniques #
Techniques used in this step.
Prepare for Elicitation #
Getting ready before gathering requirements: choosing participants, goals, questions and materials. Good preparation makes each session shorter and more productive.
Conduct and Confirm Elicitation #
Running the requirements session, then sending the results back to participants to check them. Confirmation catches misunderstandings while they are still cheap to fix.
Elicitation Technique Selection #
Choosing the right way to gather requirements, such as interviews, workshops, surveys or observation, for the people and topic involved. The right method gets better information at lower cost.
Requirements Prioritization #
Ranking requirements by value, urgency, risk and effort. It lets the team decide what to deliver first and what to defer when time or money is limited.
Quality Function Deployment (QFD) #
A method that translates customer needs into technical characteristics of the product, usually in a matrix. It keeps design choices tied to what customers actually value.
Standards & Regulatory Review #
Checking which laws, standards and regulations apply to the product and turning them into requirements. It prevents late surprises from non-compliance.
Site Survey / Field Study #
Going to the place where the product will be used to observe real conditions and work. It reveals needs and constraints that people do not mention in interviews.
Open Issues Management #
Tracking unresolved questions from requirements work with an owner and a due date until each is closed. It stops gaps from silently turning into defects.
