Loading content
Requirements analysis identifies, prioritizes, and documents functional and non-functional requirements for systems or products. It aligns stakeholder needs with technical constraints, establishes traceability, and forms the basis for design, validation, and early project decisions. The aim is a clear, verified, and accepted specification.
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 analysis elicits, clarifies, structures, and prioritizes stakeholder needs, constraints, and expected system behavior.
The discipline grew from the software crisis of the 1960s and the cost of resolving misunderstandings late. Systems engineering, use cases, and agile discovery extended its practices.
Analysts gather statements from stakeholders, resolve conflicts, and turn them into verifiable requirements. Each needs context, priority, and an acceptance criterion. Analysis focuses on what is needed; requirements engineering additionally covers elicitation, documentation, validation, and ongoing management.
Needs and constraints are gathered from suitable sources.
Requirements are checked for clarity, consistency, and testability.
Links to source, decision, implementation, and test remain visible.
Requirements analysis reduces building the wrong thing and gives design and testing a verifiable basis. Ambiguous terms, missing stakeholders, and premature solution choices remain key risks.
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.