Functional Decomposition
Break complex business needs into smaller, manageable functions to understand scope and structure requirements.
Definition
Functional Decomposition is a technique used to break down a complex business need, system, or process into smaller, more manageable functions and sub-functions. It helps Business Analysts understand scope, identify missing requirements, organize requirements logically, and communicate complexity clearly to stakeholders. The output is a hierarchical structure that can serve as a navigation framework for the full requirements set.
Inputs
- High-level business need, capability, or system scope statement
- Stakeholder input on major functional areas
- Existing documentation describing the current or desired system
- Business objectives to validate that decomposition is complete
Outputs
- A hierarchical decomposition diagram or outline showing functions and sub-functions
- A structured requirements framework aligned to functional areas
- Inputs to scope definition, work breakdown, estimation, and delivery planning
- Identified gaps where sub-functions are missing or undefined
When to Use
- Early analysis of large, complex initiatives where scope must be made manageable
- Defining scope boundaries before detailed requirements elicitation
- Building a requirements structure or hierarchy for a large system
- Preparing for estimation and delivery planning where work must be broken into deliverable units
When Not to Use
- Small, well-understood initiatives where the scope is already clear
- When stakeholders need concrete requirements rather than a structural framework
- When decomposition would delay progress without adding clarity
See this technique in action with a free RequirementsHub workspace.
Start Free Workspace →