View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Scatter Diagram |  Operations ABC Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Fishbone Diagram |
|---|---|---|---|---|
Purposedifferent | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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. |
Complexitydifferent | Low | Low | High | Low |
Timedifferent | 30-90 min | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min |
Participantsdifferent | 1-4 | 1-5 | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Scatter Plot, Korrelationsnotiz, Hypothesenliste | ABC Classification, Focus Rules, Control List | 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 |
Tagsno overlap | Root causeQualityVisualization | PrioritizationOperationsPortfolio | ArchitectureQualityRiskTradeoffsStakeholders | Root causeQualityOperations |