View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)Software Architecture CanvasAcceptance Criteria Workshop
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture Software Architecture Canvas |  Agile Acceptance Criteria Workshop |
|---|---|---|---|
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 Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 | High | Low | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 h | 20-40 min pro Story |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-10 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
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 Canvas, Goals, Constraints, Quality Attributes | Acceptance Criteria, Story Update |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | CanvasArchitectureAlignmentWorkshop | AgileRequirementsRefinementBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
