Context Map (Concept)
April 4, 2025 ยท View on GitHub
Description
The context map provides an overview for all models and their boundaries and interfaces.
Tags
pattern
Documentation
To plot strategy, we need a realistic, large-scale view of model development extending across our project and others we integrate with.
An individual bounded context leaves some problems in the absence of a global view. The context of other models may still be vague and in flux.
People on other teams won't be very aware of the context boundaries and will unknowingly make changes that blur the edges or complicate the interconnections. When connections must be made between different contexts, they tend to bleed into each other.
Even when boundaries are clear, relationships with other contexts place constraints on the nature of model or pace of change that is feasible. These constraints manifest themselves primarily through non-technical channels that are sometimes hard to relate to the design decisions they are affecting.
Therefore,
Identify each model in play on the project and define its bounded context. This includes the implicit models of non-object-oriented subsystems. Name each bounded context, and make the names part of the ubiquitous language.
Describe the points of contact between the models, outlining explicit translation for any communication, highlighting any sharing, isolation mechanisms, and levels of influence.
Map the existing terrain. Take up transformations later.
This map can be a basis for realistic design strategy.
The characterization of relationships is made more concrete in the following pages, with a set of common patterns of relationships between bounded contexts.
Other Relations
| From | Name | To | Description |
|---|---|---|---|
| Bounded Context | assess/overview relationships with | Context Map | |
| Context Map | coordinate interdependent contexts | Partnership | |
| Context Map | coordinate upstream/downstream | Customer/Supplier | |
| Context Map | free teams to go | Separate Ways | |
| Context Map | overlap contexts | Shared Kernel | |
| Context Map | overlap unilaterally as | Conformist | |
| Context Map | seggregate the conceptual messes | Big Ball of Mud | |
| Context Map | support multiple clients through | Open Host Service | |
| Context Map | translate and isolate unilaterally with | Anti-Corruption Layer |
Concept Map
Concept Map of the Domain Driven Design Context Mapping for Strategic Design Patterns
Navigation
(generated by Overarch with template docs/node.md.cmb)