Loading content
Requirement elicitation is a structured method for uncovering stakeholder needs, constraints and acceptance criteria to shape product scope and design. It combines interviews, workshops, observation and document analysis to build shared understanding. The method emphasizes stakeholder alignment, traceability of decisions and early validation to reduce rework…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Requirement elicitation is the systematic discovery and clarification of needs, expectations, and constraints from which verifiable requirements are formed.
Requirements elicitation is an established part of requirements engineering and has no single author. IEEE 29148:2018 places requirements and their elicitation in an international process framework.
Work as a translator between problem and solution worlds: identify stakeholders and goals, collect statements and observations, challenge assumptions and contradictions, and turn them into testable requirements. Confirm shared understanding with examples, priorities, and acceptance criteria.
People affected, users, and owners offer different views of the problem.
Interviews, observation, workshops, and artefact analysis expose different kinds of knowledge.
Examples and questions test whether a requirement is intended and testable.
Requirement elicitation prevents teams from treating unexamined wishes as solution specifications. It matters especially with multiple interests, tacit knowledge, and consequential systems; findings remain provisional until agreed and validated.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.