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 | ![]() Systems Thinking Future Reality Tree | ![]() Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. | 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 | Medium | High | High |
Timedifferent | 60-120 min | 2-4 h | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 2-8 | 3-8 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | 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 | Theory of ConstraintsAssumptionsSystems thinking | Theory of ConstraintsSystems thinkingChange | ArchitectureChangeAnalysisComparisonQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






