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 ATAM (Architecture Tradeoff Analysis Method) |  Architecture Views and Beyond |
|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 60-120 min | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 Tage |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ArchitectureQualityRiskTradeoffsStakeholders | DocumentationStakeholdersArchitecture |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
