View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Quality Attribute WorkshopATAM (Architecture Tradeoff Analysis Method)Specification by ExampleRisk Storming
| Criterion |  Architecture Quality Attribute Workshop |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Agile Specification by Example |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | 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. | 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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 | Medium | High | Medium | Low |
Timedifferent | 2-4 h | Several meetings plus preparation and analysis; total effort depends on scope | 60-90 min pro Feature | 60-90 min |
Participantsdifferent | 5-15 | Evaluation team, architects, and relevant stakeholders | 3-6 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Example Table, Acceptance Tests | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | RequirementsArchitectureWorkshop | ArchitectureQualityRiskTradeoffsStakeholders | AgileRequirementsExamplesBehavior-Driven Development | RiskArchitectureWorkshopValidation |