View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking System Dynamics Simulation |  Architecture Architecture Decision Record |  Architecture C4 Model |  Systems Thinking Stock and Flow Diagram |
|---|---|---|---|---|
Purposedifferent | System Dynamics Simulation makes assumptions about time, delay, and feedback testable through experiments. It draws relationships, patterns, and feedback loops. The result is captured as a simulation model and scenario reports. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | A Stock and Flow Diagram shows how stocks, inflows, and outflows shape a system over time. It is especially suited when growth, delays, or capacity limits determine the dynamics. |
Complexitydifferent | High | Low | Low | High |
Timedifferent | Mehrere Tage bis Wochen | 15-45 min | 1-4 h | 2-6 h |
Participantsdifferent | 1-5 Modellierende, Stakeholder asynchron | 1-3 | 1-5 | 1-6 |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | Simulation Model, Scenario Reports | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram | Stock and Flow Model, Dynamics Notes, Simulation Hypotheses |
Tagsno overlap | Systems thinkingDynamicsSimulationAnalysis | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization | DynamicsSimulationFeedbackSystems thinking |