Functional System Decomposition

Origin. Pyotr Anokhin's theory of functional systems (1935-1974); extended beyond physiology into organizational and technical systems.

Mechanism. A functional system is defined by its useful result, not by its components. The same result can be achieved by different component configurations, and the system dynamically reorganizes to maintain the result under perturbation. Decompose by the results produced at each stage, not by the components involved. A functional decomposition is stable under component substitution; a structural decomposition is not.

Procedure. Ask what result each part of the system exists to produce. Trace backward from the final result to intermediate results to inputs. The decomposition should be a tree of results, not a graph of components. For each result, identify the acceptance condition: how does the system recognize that the result is adequate? The acceptance condition is the comparator in the feedback loop.

Applies to. System architecture, process design, and refactoring. Particularly powerful when components are being replaced or when the system must adapt to changing requirements.

Limitations. Defining "useful result" is itself a design choice that is often contested. The method assumes a clear hierarchy of ends and means, which works for biological systems with well-defined goals (survive, reproduce) but is underdetermined for technical and organizational systems. Also: functional decomposition can obscure resource sharing and interaction between functional subsystems; components often serve multiple functions simultaneously, and a pure functional decomposition duplicates them.