View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Domain Modeling Context Map | ![]() Architecture Views and Beyond | ![]() Architecture Architecture Communication Canvas | ![]() Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-3 Tage | 60-120 min | 1-2 h |
Participantsdifferent | 2-8 | 1-4 | 2-8 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Architecture Views, Cross-view Notes, Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | DocumentationStakeholdersArchitecture | ArchitectureCommunicationStakeholdersCanvas | AlignmentStakeholdersStrategyFacilitation |



