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) |  Operations Scatter Diagram |  Architecture C4 Model |
|---|---|---|---|
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 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. |
Complexitydifferent | High | Low | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30-90 min | 1-4 h |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1-4 | 1-5 |
Formatsame | Workshop + async | Workshop + async | 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 | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | Root causeQualityVisualization | ArchitectureCommunicationVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
