View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Systems Thinking Rich Picture |  Operations Fishbone Diagram |  Operations Scatter Diagram |
|---|---|---|---|---|
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. | A Rich Picture brings an unclear situation onto a shared drawing. It captures actors, tensions, information flows, and blind spots before the team jumps to solutions too early. | 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. | 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. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30-90 min | 30-60 min | 30-90 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-10 | 2-8 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Rich Picture, Problem Framing Notes | Fishbone Diagram, Cause Categories, Investigation Backlog | Scatter Plot, Korrelationsnotiz, Hypothesenliste |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | Systems thinkingSoft systemsFramingVisualization | Root causeQualityOperations | Root causeQualityVisualization |