methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
1-3 h1-3 h60-120 min1-2 h
Participantsdifferent
3-82-82-83-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Context Canvas, Glossary, Integration NotesContext Map, Integration Patterns, Boundary NotesCommunication Canvas, Stakeholder Messages, Architecture Communication PlanInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
Domain-Driven DesignBoundariesModeling
Domain-Driven DesignBoundariesStrategy
ArchitectureCommunicationStakeholdersCanvas
AlignmentArchitectureCanvas
Add more methods