View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Decision Rights MappingArchitecture Decision RecordSAAM (Software Architecture Analysis Method)
| Criterion |  Decision Making Decision Rights Mapping |  Architecture Architecture Decision Record |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|
Purposedifferent | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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. |
Complexitydifferent | Medium | Low | High |
Timedifferent | 90-180 min | 15-45 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 4-12 | 1-3 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Decision Rights Matrix, Agreement | 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 |
Tagsno overlap | DecisionGovernanceAlignmentResponsibility | ArchitectureRationaleDocumentationGovernance | ArchitectureChangeAnalysisComparisonQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
