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)Quality Attribute WorkshopExample MappingRisk Storming
| Criterion | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Architecture Quality Attribute Workshop | ![]() Agile Example Mapping | ![]() Architecture Risk Storming |
|---|---|---|---|---|
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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 2-4 h | 30-60 min | 60-90 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 5-15 | 3-7 | 4-12 |
Formatdifferent | Workshop + async | Workshop | 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 | Quality Scenarios, Priority List, Architecture Concerns | Example Map, Acceptance Criteria, Open Questions | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | RequirementsArchitectureWorkshop | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RiskArchitectureWorkshopValidation |



