View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Specification by Examplearc42ATAM (Architecture Tradeoff Analysis Method)Acceptance Criteria Workshop
| Criterion |  Agile Specification by Example |  Architecture arc42 |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | 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. | 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 | Medium | Low | High | Low |
Timedifferent | 60-90 min pro Feature | 1-2 Tage | Several meetings plus preparation and analysis; total effort depends on scope | 20-40 min pro Story |
Participantsdifferent | 3-6 | 1-4 | Evaluation team, architects, and relevant stakeholders | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | 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 | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureDocumentationCommunication | ArchitectureQualityRiskTradeoffsStakeholders | AgileRequirementsRefinementBehavior-Driven Development |