Loading content
Requirements engineering is the systematic process of eliciting, analyzing and managing requirements for a system or product. It aligns stakeholder needs with technical specifications, reduces rework and supports traceable decisions. Core activities include elicitation, specification, validation and change management. It is essential for delivering fit-for-p…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Requirements engineering elicits, specifies, validates, and manages system requirements throughout their life cycle.
The discipline grew out of the software crisis of the 1960s and 1970s, when projects needed systematic ways to capture needs and control change. Standards such as ISO/IEC/IEEE 29148 consolidate established practices.
Treat requirements as verifiable agreements between need and solution: stakeholders provide goals and constraints, the team analyses conflicts, specifies requirements, and validates them with stakeholders. Traceability links needs, implementation, and tests; prioritization and change management keep the set governable.
Needs, goals, and constraints become visible through interviews, observation, document analysis, or prototypes.
Requirements are stated clearly, unambiguously, and in a testable form.
Links between needs, requirements, implementation, and tests make change impact verifiable.
Requirements engineering gives product, domain, design, and engineering a shared basis for decisions. It matters especially with many stakeholders, safety or regulatory constraints, and costly mistakes; perfectly stable requirements are rarely realistic.
Where this building block is located in the topic model.
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.