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) |  Growth Hooked Model |  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. | The Hooked Model helps clarify engagement loops, user behavior, and experiments. It makes repeat behavior measurable and captures the result as a hooked loop, trigger map, and reward design. | 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 | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | Multiple workshops over several weeks | 1-4 h |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-8 | 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 | Hooked loop, Trigger map, Reward design, Ethics check | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | GrowthBehaviorRetention | ArchitectureCommunicationVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
