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 arc42 |  Facilitation Stakeholder Mapping |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 1-2 Tage | 60–90 min | 60-120 min |
Participantsdifferent | 2-8 | 1-4 | 2-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Architecture Document, Context View, Runtime View, Deployment View | Stakeholder Map, Engagement Plan, Risk Notes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ArchitectureDocumentationCommunication | StakeholdersAlignmentFacilitationChange | ArchitectureCommunicationStakeholdersCanvas |