# Requirements Analysis

The iterative examination and modeling of needs and requirements to make them coherent, feasible, valuable, and decision-ready.

- Type: practice
- Domain: Delivery & agility
- Level: Intermediate
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/requirements-analysis/>)

## What it means

Requirements analysis transforms elicited information into a structured understanding of needs, rules, relationships, boundaries, conflicts, and solution options. It clarifies and models requirements before or alongside specification; it does not assume every stakeholder statement should become product scope.

## Why it matters

Raw input is often ambiguous, duplicated, inconsistent, or solution-biased. Analysis reveals missing cases and tradeoffs, connects requirements to value, and gives designers and engineers a sounder basis for solution decisions.

## When to use it

Use it when needs cross roles, systems, rules, or teams, or when errors have meaningful cost. Scale the analysis to risk and uncertainty; straightforward reversible changes may need only a brief collaborative review.

## How it works

1. Organize elicited information by goals, actors, processes, data, rules, and constraints.
2. Clarify terms, boundaries, assumptions, and the underlying need for each candidate requirement.
3. Model relationships, states, scenarios, interfaces, and exceptions where they improve understanding.
4. Identify gaps, conflicts, dependencies, infeasible conditions, and possible design options.
5. Evaluate potential value and tradeoffs with stakeholders and delivery specialists.
6. Refine requirements and pass them through verification, validation, and prioritization.

## A practical example

A team analyzing account delegation maps roles, permission states, audit events, revocation paths, and support exceptions. It discovers that a single “delegate” role cannot satisfy both assistants and external accountants, leading to two bounded access models.

## Where it breaks

Models simplify reality and can become expensive documentation that quickly ages. Analysis cannot replace prototyping or real-world validation, and analysts may encode organizational assumptions as if they were objective needs.

## Common mistakes

- Turning every elicited statement directly into a requirement.
- Analyzing only the happy path and ignoring states and exceptions.
- Choosing a solution before clarifying the underlying need.
- Creating models too detailed to support an actual decision.

## Sources

1. [Business Analysis Knowledge Areas](<https://www.iiba.org/knowledgehub/the-business-analysis-standard/5-applying-business-analysis-tasks/5-3-business-analysis-knowledge-areas/>) — International Institute of Business Analysis · Professional standard
2. [ISO/IEC/IEEE 29148:2018 — Requirements Engineering](<https://www.iso.org/standard/72089.html>) — International Organization for Standardization · International standard

## Related topics

- [Requirements Elicitation](<https://wiki.soroush.uk/topic/requirements-elicitation/>)
- [Product Requirement](<https://wiki.soroush.uk/topic/product-requirement/>)
- [Solution Validation](<https://wiki.soroush.uk/topic/solution-validation/>)
