View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)Fishbone DiagramTheory of Constraints Thinking Process
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Fishbone Diagram |  Systems Thinking Theory of Constraints Thinking Process |
|---|---|---|---|
Purposedifferent | 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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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. |
Complexitydifferent | High | Low | High |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min | 0.5-3 Tage |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Fishbone Diagram, Cause Categories, Investigation Backlog | Current Reality Logic, Conflict Cloud, Future Reality Tree, Implementation Obstacles |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | Root causeQualityOperations | Theory of ConstraintsConstraintsSystems thinkingCausality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
