View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Causal Loop DiagramSystem Dynamics SimulationSAAM (Software Architecture Analysis Method)ARID (Active Reviews for Intermediate Designs)
| Criterion |  Systems Thinking Causal Loop Diagram |  Systems Thinking System Dynamics Simulation |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
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. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. |
Complexitydifferent | Medium | High | High | Medium |
Timedifferent | 1-3 h | Mehrere Tage bis Wochen | Preparation, scenario analysis, and findings review; effort depends on scope | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 2-8 | 1-5 Modellierende, Stakeholder asynchron | Architecture experts and stakeholders for scenarios and weighting | Designers, developers as users, and facilitation |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Causal Loop Diagram, Feedback Notes, Leverage Points | Simulation Model, Scenario Reports | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | FeedbackSystems thinkingCausalityDynamics | Systems thinkingDynamicsSimulationAnalysis | ArchitectureChangeAnalysisComparisonQuality | ArchitectureEngineeringFeedbackValidationTasks |