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 Causal Loop Diagram |  Systems Thinking System Dynamics Simulation |  Architecture arc42 |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | A Causal Loop Diagram makes feedback, reinforcement, and balance in a system legible. It uncovers side effects and self-reinforcement that stay hidden in linear explanations. | 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. | 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 | Medium | High | Low | Low |
Timedifferent | 1-3 h | Mehrere Tage bis Wochen | 1-2 Tage | 15-45 min |
Participantsdifferent | 2-8 | 1-5 Modellierende, Stakeholder asynchron | 1-4 | 1-3 |
Formatdifferent | Workshop | Async | Workshop + async | Async |
Outputdifferent | Causal Loop Diagram, Feedback Notes, Leverage Points | Simulation Model, Scenario Reports | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale |
Tagsno overlap | FeedbackSystems thinkingCausalityDynamics | Systems thinkingDynamicsSimulationAnalysis | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance |