Requirements elicitation identifies, gathers, and clarifies stakeholder needs, goals, constraints, and expectations.
Teams collect information from stakeholders, documents, existing systems, observations, and domain experts. Therefore, they should identify relevant sources before selecting suitable techniques.
Common techniques include interviews, workshops, surveys, observation, modelling, and prototyping. For example, interviews provide detailed insights. In contrast, surveys reach larger groups.
Teams should record the source, context, rationale, and assumptions behind each finding. Moreover, they should document conflicts, open questions, and supporting evidence.
Requirements elicitation often reveals incomplete, unclear, or contradictory information. Consequently, teams must analyse findings, resolve conflicts, and validate their understanding with stakeholders.
Technique selection depends on project goals, available time, stakeholder access, and domain complexity. In addition, combining several methods can improve coverage and reduce misunderstanding.
Systematic discovery creates a reliable foundation for requirements analysis, documentation, prioritization, and validation.
« Back to Glossary Index