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) |  Architecture arc42 |  Decision Making Red Teaming |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | High | Low | High | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 Tage | 1-4 h | 15-45 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1-4 | 3-8 | 1-3 |
Formatdifferent | 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 | Architecture Document, Context View, Runtime View, Deployment View | Challenge Findings, Risk Register, Mitigation Plan | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureDocumentationCommunication | RiskDecisionSensemaking | ArchitectureRationaleDocumentationGovernance |