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 Views and Beyond |  Architecture arc42 |  Facilitation Stakeholder Salience Model |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 Tage | 1-2 Tage | 60-90 min | 15-45 min |
Participantsdifferent | 1-4 | 1-4 | 3-6 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Architecture Views, Cross-view Notes, Rationale | Architecture Document, Context View, Runtime View, Deployment View | Salience Diagram, Strategy per Class | ADR File, Decision Log, Rationale |
Tagsno overlap | DocumentationStakeholdersArchitecture | ArchitectureDocumentationCommunication | StakeholdersFacilitationAlignmentGovernance | ArchitectureRationaleDocumentationGovernance |