View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture arc42 | ![]() Architecture Architecture Decision Record | ![]() Systems Thinking System Dynamics Simulation |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Low | High |
Timedifferent | 1-2 Tage | 15-45 min | Mehrere Tage bis Wochen |
Participantsdifferent | 1-4 | 1-3 | 1-5 Modellierende, Stakeholder asynchron |
Formatdifferent | Workshop + async | Async | Async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale | Simulation Model, Scenario Reports |
Tagsno overlap | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance | Systems thinkingDynamicsSimulationAnalysis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






