View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordSAAM (Software Architecture Analysis Method)Alignment MappingStakeholder Salience Model
| Criterion |  Architecture Architecture Decision Record |  Architecture SAAM (Software Architecture Analysis Method) |  Facilitation Alignment Mapping |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | 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. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 15-45 min | Preparation, scenario analysis, and findings review; effort depends on scope | 1-2 h | 60-90 min |
Participantsdifferent | 1-3 | Architecture experts and stakeholders for scenarios and weighting | 4-12 | 3-6 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | 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 | Salience Diagram, Strategy per Class |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureChangeAnalysisComparisonQuality | AlignmentStakeholdersStrategyFacilitation | StakeholdersFacilitationAlignmentGovernance |