Context Map

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 bounds 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. 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 context, and make the names part of the ubiquitous language.

Describe the points of contact between the models, outlining explicit translation for any communication and highlighting any sharing.