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 Risk Storming |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|
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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. |
Complexitydifferent | High | Low | High |
Timedifferent | Mehrere Tage bis Wochen | 60-90 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 1-5 Modellierende, Stakeholder asynchron | 4-12 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | Simulation Model, Scenario Reports | Annotated Diagram, Prioritized Risk List, Action Backlog | 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 |
Tagsno overlap | Systems thinkingDynamicsSimulationAnalysis | RiskArchitectureWorkshopValidation | ArchitectureChangeAnalysisComparisonQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
