Functional Decomposition
Updated 2026-08-10
INTRODUCTION
English translation pending.
CORE DEFINITION
A systems engineering method that begins with the overall function the system must perform and decomposes it into the sub-functions necessary and sufficient to deliver it, recursing until each sub-function can be realized by a concrete module. The key qualification is the order of operations: function is decided before structure, so the design is driven by what must be achieved rather than by an architecture chosen in advance. Interfaces and dependencies between sub-functions must also be specified, since the decomposition is only useful if the parts can be recombined.
SCAFFOLDING EFFECT
Reduce cognitive load
- Function first: state what the system must achieve before proposing any structure. - Recursive split: break each sub-function down until it maps to something buildable. - Interface mapping: define how the sub-functions connect so the parts can be recombined.
Anchor fast decisions
Structures chosen before functions are shaped by whatever architecture the designer already favors, so they satisfy the tool rather than the requirement. Decomposing from the function outward keeps every component traceable to a purpose, and recursion guarantees that each level is small enough to implement. Because sub-functions are defined by what they contribute, redundant and missing capabilities become visible at the point of decomposition rather than after construction.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Functional_decompositionverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS