System Dynamics — Stock-Flow Modelling
System Dynamics (Stock-Flow Modelling) · Also known as: stock-flow modelling, Sistem Dinamiği (Stock-Flow Modelleme), SD modelling, feedback simulation
System dynamics is a continuous simulation method, developed by Jay W. Forrester at MIT in 1961, that represents a complex system through stocks (accumulations), flows (rates of change), and feedback loops. By expressing these relationships as coupled ordinary differential equations, it reproduces how policies, delays, and nonlinear feedbacks drive system behaviour over time — making it a cornerstone tool in policy analysis, organisational modelling, and sustainability research.
Read the full method
Sign in with a free account to read this section.
Method map
The neighbourhood of related methods — select a node to explore.
+17 more
When to use it
System dynamics is appropriate when the behaviour of interest emerges from feedback loops and accumulation over time — for example, epidemic spread, inventory oscillations, population growth, or the long-run effects of an organisational policy. It suits continuous phenomena and time-series structures; if the system consists of discrete, event-driven transactions, discrete-event simulation is the better choice. No minimum sample size is required: the method is equation-driven rather than data-driven. Validation against historical data is strongly recommended but not always possible in prospective policy work.
Strengths & limitations
- Captures nonlinear feedback dynamics and time delays that are invisible in static or regression-based models.
- Requires no minimum sample size — the method works even when historical data are sparse, relying on structural knowledge of the system.
- Supports transparent policy experimentation: changing a parameter or loop structure produces traceable, interpretable changes in behaviour.
- Applicable across disciplines — epidemiology, business, ecology, engineering, public policy — wherever stocks and flows describe the system.
- The continuous-time assumption is inappropriate for systems driven by discrete events or individual-level heterogeneity.
- Model quality depends heavily on the correctness of the causal structure; a missed feedback loop or wrong boundary cannot be recovered by calibration alone.
- Parameter estimation is often uncertain; results should always be subjected to sensitivity analysis and reported as ranges rather than point predictions.
- The method produces endogenous behaviour trajectories, not probabilistic forecasts; uncertainty quantification requires additional Monte Carlo or Latin-hypercube wrapping.
Frequently asked
How is system dynamics different from discrete-event simulation?
System dynamics treats the system as continuous flows described by differential equations and is best suited to aggregate, feedback-driven phenomena such as epidemic spread or inventory oscillations. Discrete-event simulation tracks individual entities moving through a system — queues, transactions, machine jobs — and is better when timing and sequencing of individual events matter. The two methods are complementary: system dynamics captures long-run structural behaviour; discrete-event simulation captures short-run operational detail.
Do I need a lot of data to build a system dynamics model?
No. System dynamics is equation-driven rather than data-driven, so it can be built with sparse data supplemented by structural knowledge and expert elicitation. Historical data are needed for calibration and behaviour-reproduction validation, but the method does not impose a minimum sample size the way statistical models do. When data are available, they should be used to calibrate parameters and test model validity.
What is the difference between a reinforcing (R) and a balancing (B) feedback loop?
A reinforcing loop amplifies change in one direction — positive growth or accelerating decline. A balancing loop counteracts change, pushing the system toward a goal or equilibrium. Most real systems contain both types: growth is driven by reinforcing loops and eventually checked by balancing loops (resource limits, saturation effects). Identifying these loops is the first step in causal-loop diagramming.
How is model validity established in system dynamics?
Validity rests on two complementary pillars: structural tests (extreme-condition tests, dimensional consistency, boundary adequacy) confirm that the model equations make sense on their own terms; behaviour tests (behaviour reproduction, sensitivity analysis) confirm that the model generates trajectories consistent with observed data. A model that passes behaviour tests but fails structural tests is not considered valid — it may reproduce history for the wrong reasons.
Sources
- Sterman, J.D. (2000). Business Dynamics: Systems Thinking and Modeling for a Complex World. Irwin McGraw-Hill. ISBN: 978-0072389159
- Forrester, J.W. (1961). Industrial Dynamics. MIT Press. ISBN: 978-0262060035
How to cite this page
ScholarGate. (2026, June 1). System Dynamics (Stock-Flow Modelling). ScholarGate. https://scholargate.app/en/simulation/system-dynamics
Which method?
Set this method beside its closest kin and read them side by side — the library lays the books on the table; the choice is yours.
- Discrete-Event SimulationSimulation↔ compare
- Latin Hypercube SamplingSimulation↔ compare
- MONTE-CARLO-SIMULATIONDecision-making↔ compare