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 |  Domain Modeling Context Map |  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 contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 Tage | 1-3 h | 60-90 min |
Participantsdifferent | 1-4 | 2-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Architecture Views, Cross-view Notes, Rationale | Context Map, Integration Patterns, Boundary Notes | Salience Diagram, Strategy per Class |
Tagsno overlap | DocumentationStakeholdersArchitecture | Domain-Driven DesignBoundariesStrategy | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
