View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:SAAM (Software Architecture Analysis Method)Specification by ExampleAcceptance Criteria Workshop
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Agile Specification by Example |  Agile Acceptance Criteria Workshop |
|---|---|---|---|
Purposedifferent | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | 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. | 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 | Medium | Low |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 60-90 min pro Feature | 20-40 min pro Story |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-6 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Example Table, Acceptance Tests | Acceptance Criteria, Story Update |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | AgileRequirementsExamplesBehavior-Driven Development | AgileRequirementsRefinementBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
