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 SimulationSoftware Architecture CanvasArchitecture Decision RecordStock and Flow Diagram
| Criterion |  Systems Thinking System Dynamics Simulation |  Architecture Software Architecture Canvas |  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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 | Low | Low | High |
Timedifferent | Mehrere Tage bis Wochen | 1-2 h | 15-45 min | 2-6 h |
Participantsdifferent | 1-5 Modellierende, Stakeholder asynchron | 3-10 | 1-3 | 1-6 |
Formatdifferent | Async | Workshop | Async | Workshop + async |
Outputdifferent | Simulation Model, Scenario Reports | Architecture Canvas, Goals, Constraints, Quality Attributes | ADR File, Decision Log, Rationale | Stock and Flow Model, Dynamics Notes, Simulation Hypotheses |
Tagsno overlap | Systems thinkingDynamicsSimulationAnalysis | CanvasArchitectureAlignmentWorkshop | ArchitectureRationaleDocumentationGovernance | DynamicsSimulationFeedbackSystems thinking |