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 Stock and Flow Diagram |  Architecture arc42 |  Systems Thinking System Dynamics Simulation |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitydifferent | High | Low | High | Low |
Timedifferent | 2-6 h | 1-2 Tage | Mehrere Tage bis Wochen | 15-45 min |
Participantsdifferent | 1-6 | 1-4 | 1-5 Modellierende, Stakeholder asynchron | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | Stock and Flow Model, Dynamics Notes, Simulation Hypotheses | Architecture Document, Context View, Runtime View, Deployment View | Simulation Model, Scenario Reports | ADR File, Decision Log, Rationale |
Tagsno overlap | DynamicsSimulationFeedbackSystems thinking | ArchitectureDocumentationCommunication | Systems thinkingDynamicsSimulationAnalysis | ArchitectureRationaleDocumentationGovernance |