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 Software Architecture Canvas |
|---|---|---|---|
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 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. |
Complexitydifferent | High | Low | Low |
Timedifferent | Mehrere Tage bis Wochen | 15-45 min | 1-2 h |
Participantsdifferent | 1-5 Modellierende, Stakeholder asynchron | 1-3 | 3-10 |
Formatdifferent | Async | Async | Workshop |
Outputdifferent | Simulation Model, Scenario Reports | ADR File, Decision Log, Rationale | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | Systems thinkingDynamicsSimulationAnalysis | ArchitectureRationaleDocumentationGovernance | CanvasArchitectureAlignmentWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






