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 arc42 |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Agile Acceptance Criteria Workshop |
|---|---|---|---|
Purposedifferent | 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. | 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 a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. |
Complexitydifferent | Low | High | Low |
Timedifferent | 1-2 Tage | Several meetings plus preparation and analysis; total effort depends on scope | 20-40 min pro Story |
Participantsdifferent | 1-4 | Evaluation team, architects, and relevant stakeholders | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Acceptance Criteria, Story Update |
Tagsno overlap | ArchitectureDocumentationCommunication | ArchitectureQualityRiskTradeoffsStakeholders | AgileRequirementsRefinementBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
