View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Views and BeyondArchitecture Decision RecordSoftware Architecture CanvasStakeholder Salience Model
| Criterion |  Architecture Views and Beyond |  Architecture Architecture Decision Record |  Architecture Software Architecture Canvas |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 | Medium | Low | Low | Medium |
Timedifferent | 1-3 Tage | 15-45 min | 1-2 h | 60-90 min |
Participantsdifferent | 1-4 | 1-3 | 3-10 | 3-6 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Architecture Views, Cross-view Notes, Rationale | ADR File, Decision Log, Rationale | Architecture Canvas, Goals, Constraints, Quality Attributes | Salience Diagram, Strategy per Class |
Tagsno overlap | DocumentationStakeholdersArchitecture | ArchitectureRationaleDocumentationGovernance | CanvasArchitectureAlignmentWorkshop | StakeholdersFacilitationAlignmentGovernance |