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 Evaporating Cloud |  Architecture SAAM (Software Architecture Analysis Method) |  Systems Thinking Causal Loop Diagram |
|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | 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. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 60-120 min | Preparation, scenario analysis, and findings review; effort depends on scope | 1-3 h |
Participantsdifferent | 2-8 | Architecture experts and stakeholders for scenarios and weighting | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | 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 | Causal Loop Diagram, Feedback Notes, Leverage Points |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ArchitectureChangeAnalysisComparisonQuality | FeedbackSystems thinkingCausalityDynamics |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
