View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)Expectation MappingSAAM (Software Architecture Analysis Method)Alignment Mapping
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Expectation Mapping |  Architecture SAAM (Software Architecture Analysis Method) |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | High | Low | High | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min | Preparation, scenario analysis, and findings review; effort depends on scope | 1-2 h |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-12 | Architecture experts and stakeholders for scenarios and weighting | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Expectation Map, Alignment Notes, Agreements | 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 | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | AlignmentStakeholdersTeam | ArchitectureChangeAnalysisComparisonQuality | AlignmentStakeholdersStrategyFacilitation |