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 |  Facilitation Alignment Mapping |  Architecture arc42 |  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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 Tage | 1-2 h | 1-2 Tage | 60-90 min |
Participantsdifferent | 1-4 | 4-12 | 1-4 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Architecture Views, Cross-view Notes, Rationale | Alignment Map, Open Issues, Decision Questions | Architecture Document, Context View, Runtime View, Deployment View | Salience Diagram, Strategy per Class |
Tagsno overlap | DocumentationStakeholdersArchitecture | AlignmentStakeholdersStrategyFacilitation | ArchitectureDocumentationCommunication | StakeholdersFacilitationAlignmentGovernance |