Domain-driven design is all about encapsulating domain knowledge and the guiding force to contain and distribute knowledge is language. We have talked before about the fact that one of the goals of domain-driven design is to create a ubiquitous language in the project that is shared between the developers and the project owners or stakeholders to guide the implementation. And it has been hinted before that this is, of course, not a one way street.

As domain concepts are uncovered, it is often useful to establish and name the new concepts as a team to make them the established way of communication. Sometimes, these new names and meanings can make it back into the business, they will start to get used to describe the now named pattern and over a long time can make it back in the common language used in the domain cross businesses if they are considered useful.

In the original book on domain-driven design, by Eric Evans, he discusses the development of a financial...