Requirement Types
A classification of business, stakeholder, solution, and transition requirements that connects the reason for change to needs, product behavior, and adoption.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/requirement-types/
01What it means
The IIBA requirement classification distinguishes business requirements, which explain goals and outcomes; stakeholder requirements, which describe affected groups’ needs; solution requirements, which define capabilities and qualities; and transition requirements, which enable movement to the future state. Functional and non-functional requirements are subtypes of solution requirements.[1][2]
Functional and non-functional requirements are solution subtypes; transition requirements are temporary capabilities needed to move safely into the future state.
02Why it matters
Separating requirement types prevents a requested feature from being mistaken for the business objective and keeps temporary migration work from becoming permanent product behavior. The relationships also improve traceability from strategy through delivery and adoption.
03When to use it
Use the classification when a change spans business goals, multiple stakeholders, solution behavior, or migration work. Keep it lightweight for small changes, and adapt terminology when a regulated or engineering standard requires a different hierarchy.
04How it works
- State the business goals, objectives, or outcomes that justify the change.
- Identify stakeholder needs that must be met to achieve those business requirements.
- Define solution capabilities and qualities without confusing them with implementation designs.
- Identify temporary transition needs such as migration, training, continuity, or rollout support.
- Trace relationships between levels and resolve gaps or contradictions.
- Review each type as evidence and solution choices evolve.
05A practical example
For a new support portal, the business requirement is to reduce resolution time, stakeholders need case visibility and safe handoffs, solution requirements define search and access behavior, and transition requirements cover importing open cases and training agents.
06Where it breaks
Real requirements can span categories, and organizations use different taxonomies. Classification does not establish priority, correctness, or value, while excessive debate about labels can distract from understanding the need.
Common mistakes
- Writing a proposed feature as the business requirement.
- Treating stakeholder requests as already validated solution requirements.
- Forgetting temporary migration and operational-readiness needs.
- Assuming classification replaces traceability and validation.
07Sources
- Understanding Requirements and DesignsInternational Institute of Business Analysis · Professional standardUnderstanding Requirements and Designs
- ISO/IEC/IEEE 29148:2018 — Requirements EngineeringInternational Organization for Standardization · International standardISO/IEC/IEEE 29148:2018 — Requirements Engineering