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 |
|---|---|---|---|
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. |
Complexitydifferent | High | Low | Low |
Timedifferent | Mehrere Tage bis Wochen | 15-45 min | 1-4 h |
Participantsdifferent | 1-5 Modellierende, Stakeholder asynchron | 1-3 | 1-5 |
Formatdifferent | Async | Async | Workshop + async |
Outputdifferent | Simulation Model, Scenario Reports | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | Systems thinkingDynamicsSimulationAnalysis | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






