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 ExampleExample MappingATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Agile Specification by Example |  Agile Example Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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 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. | 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. |
Complexitydifferent | High | Medium | Low | High |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 60-90 min pro Feature | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-6 | 3-7 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
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 | Example Map, Acceptance Criteria, Open Questions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureQualityRiskTradeoffsStakeholders |