Business language
Domain-Driven Design
Business teams use business language, whereas the technology teams tend to use technical terms in their communication. This difference in language between the business teams and the I.T. teams can lead to linguistic challenges. Domain driven design suggests use of ubiquitous language to address these linguistic challenges.
Let’s look at an example to help you understand. What comes to mind when I say the word pasta?
If you’re thinking of some sort of noodle, you’re correct; pasta is the Italian word for noodle. However, if you say or ask for pasta in Poland, you will be served toothpaste, because pasta in Poland is synonymous with toothpaste.
As a result, the languages spoken in different parts of the world may cause misunderstanding. Similarly, utilising business jargon from one domain in another domain might cause misunderstanding and misinterpretations.
Challenges
The first problem is that I.T. teams must master business languages used by specialists in order to construct complicated systems.
The second issue is that the same phrase might be used in different commercial contexts, such as credit and credit card.
Conclusion
Domain driven design suggests setting up a common language within each business context, and this language is used by all stakeholders, including the IT teams. This language is referred to as the ubiquitous language. This is one of the strategic patterns in Domain-Driven design.
Reference
#TWBloggersClub #DDD
