Bounded Context

When modeling the processes of an organization, it is almost impossible to create only one model that represents the complete operation of the organization. The model tends to become difficult to understand and translate into code. Different groups of people can use subtly different terms for different subdomains in a large company. It leads to having confusion and misunderstanding of vocabulary. Domain Driven Design proposes to explore each subdomain separately. It will allow a team to get the best definition of vocabulary used in a particular subdomain. In doing so, the team will be able to create a more accurate model for a subdomain.

What is a bounded context?

DDD deals with the problems that the common domain models have by breaking the domain up into independent parts called Bounded Context. A bounded context is a strategic pattern that helps to maintain consistency between subdomains and their models. There must be a clear definition of limits between all bounded contexts that exist in a domain. These limits can be figured out in scoping sessions such as event storming.