View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordATAM (Architecture Tradeoff Analysis Method)Expectation MappingViews and Beyond
| Criterion |  Architecture Architecture Decision Record |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Expectation Mapping |  Architecture Views and Beyond |
|---|---|---|---|---|
Purposedifferent | 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. | 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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. |
Complexitydifferent | Low | High | Low | Medium |
Timedifferent | 15-45 min | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min | 1-3 Tage |
Participantsdifferent | 1-3 | Evaluation team, architects, and relevant stakeholders | 3-12 | 1-4 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Expectation Map, Alignment Notes, Agreements | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureQualityRiskTradeoffsStakeholders | AlignmentStakeholdersTeam | DocumentationStakeholdersArchitecture |