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)Spotify Model MappingExpectation MappingATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Team Design Spotify Model Mapping |  Facilitation Expectation 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 a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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 | 90-180 min | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 5-15 | 3-12 | 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 | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements | 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 | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam | ArchitectureQualityRiskTradeoffsStakeholders |