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 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 and highlighting any sharing. Map the existing terrain.
Read more about this topic: Domain-driven Design, Strategic Domain-driven Design
Famous quotes containing the words context and/or map:
“Among the most valuable but least appreciated experiences parenthood can provide are the opportunities it offers for exploring, reliving, and resolving one’s own childhood problems in the context of one’s relation to one’s child.”
—Bruno Bettelheim (20th century)
“In thy face I see
The map of honor, truth, and loyalty.”
—William Shakespeare (1564–1616)