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 Views and Beyond |  Architecture arc42 |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | Mehrere Tage bis Wochen | 1-3 Tage | 1-2 Tage | 15-45 min |
Participantsdifferent | 1-5 Modellierende, Stakeholder asynchron | 1-4 | 1-4 | 1-3 |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | Simulation Model, Scenario Reports | Architecture Views, Cross-view Notes, Rationale | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale |
Tagsno overlap | Systems thinkingDynamicsSimulationAnalysis | DocumentationStakeholdersArchitecture | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance |