View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Facilitation Stakeholder Salience Model |  Facilitation Alignment Mapping |
|---|---|---|---|
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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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 | Medium | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 60-90 min | 1-2 h |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-6 | 4-12 |
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 | Salience Diagram, Strategy per Class | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | StakeholdersFacilitationAlignmentGovernance | AlignmentStakeholdersStrategyFacilitation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
