Definition: The delimited applicability of a
particular model. BOUNDING CONTEXTS gives team members a clear and
shared understanding of what has to be consistent and what can develop
independently.
Problem: Multiple models are in play on any large
project. Yet when code based on distinct models is combined, software
becomes buggy, unreliable, and difficult to understand. Communication
among team members becomes confused. It is often unclear in what
context a model should not be applied.
Solution: Explicitly define the context within which a
model applies. Explicitly set boundaries in terms of team organization,
usage within specific parts of the application, and physical
manifestations such as code bases and database schemas. Keep the model
strictly consistent within these bounds, but don?t be distracted or
confused by issues outside.