View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Theory of Constraints Thinking ProcessEvaporating CloudATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Systems Thinking Theory of Constraints Thinking Process |  Systems Thinking Evaporating Cloud |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|
Purposedifferent | The Theory of Constraints Thinking Process exposes a system's bottleneck and the logic behind it. It suits situations where many symptoms trace back to the same limiting relationship. | 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. |
Complexitydifferent | High | Medium | High |
Timedifferent | 0.5-3 Tage | 60-120 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 4-10 | 2-8 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Current Reality Logic, Conflict Cloud, Future Reality Tree, Implementation Obstacles | 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 |
Tagsno overlap | Theory of ConstraintsConstraintsSystems thinkingCausality | Theory of ConstraintsAssumptionsSystems thinking | ArchitectureQualityRiskTradeoffsStakeholders |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
