View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:System Dynamics SimulationViews and BeyondArchitecture Decision RecordStock and Flow Diagram
| Criterion |  Systems Thinking System Dynamics Simulation |  Architecture Views and Beyond |  Architecture Architecture Decision Record |  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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. | 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 | Medium | Low | High |
Timedifferent | Mehrere Tage bis Wochen | 1-3 Tage | 15-45 min | 2-6 h |
Participantsdifferent | 1-5 Modellierende, Stakeholder asynchron | 1-4 | 1-3 | 1-6 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | Simulation Model, Scenario Reports | Architecture Views, Cross-view Notes, Rationale | ADR File, Decision Log, Rationale | Stock and Flow Model, Dynamics Notes, Simulation Hypotheses |
Tagsno overlap | Systems thinkingDynamicsSimulationAnalysis | DocumentationStakeholdersArchitecture | ArchitectureRationaleDocumentationGovernance | DynamicsSimulationFeedbackSystems thinking |