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 Current Reality Tree | ![]() Architecture SAAM (Software Architecture Analysis Method) | ![]() Systems Thinking System Dynamics Simulation |
|---|---|---|---|
Purposedifferent | A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once. | 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. | 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. |
Complexitysame | High | High | High |
Timedifferent | 2-6 h | Preparation, scenario analysis, and findings review; effort depends on scope | Mehrere Tage bis Wochen |
Participantsdifferent | 3-8 | Architecture experts and stakeholders for scenarios and weighting | 1-5 Modellierende, Stakeholder asynchron |
Formatdifferent | Workshop | Workshop + async | Async |
Outputdifferent | Current Reality Tree, Core Problems, Intervention Ideas | 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 | Simulation Model, Scenario Reports |
Tagsno overlap | Systems thinkingRoot causeConstraintsCausality | ArchitectureChangeAnalysisComparisonQuality | Systems thinkingDynamicsSimulationAnalysis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






