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 MappingStakeholder MappingATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Team Design Spotify Model Mapping |  Facilitation Stakeholder 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 | 60–90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 5-15 | 2-8 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop | Workshop + async | 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 | Stakeholder Map, Engagement Plan, Risk Notes | 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 | StakeholdersAlignmentFacilitationChange | ArchitectureQualityRiskTradeoffsStakeholders |