View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordSystem Dynamics SimulationArchitecture Communication CanvasStock and Flow Diagram
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Systems Thinking System Dynamics Simulation | ![]() Architecture Architecture Communication Canvas | ![]() Systems Thinking Stock and Flow Diagram |
|---|---|---|---|---|
Purposedifferent | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Low | High | Medium | High |
Timedifferent | 15-45 min | Mehrere Tage bis Wochen | 60-120 min | 2-6 h |
Participantsdifferent | 1-3 | 1-5 Modellierende, Stakeholder asynchron | 2-8 | 1-6 |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Simulation Model, Scenario Reports | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Stock and Flow Model, Dynamics Notes, Simulation Hypotheses |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Systems thinkingDynamicsSimulationAnalysis | ArchitectureCommunicationStakeholdersCanvas | DynamicsSimulationFeedbackSystems thinking |



