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 Power Interest Grid |
|---|---|---|---|
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 many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy. |
Complexitydifferent | High | Medium | Low |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 60-90 min | 30-60 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-6 | 2-8 |
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 | Power Interest Grid, Strategy per Stakeholder |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | StakeholdersFacilitationAlignmentGovernance | StakeholdersFacilitationAlignmentPlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






