Great quotes for the concept of Ubiquitous Language
The mission of this overview is to compile impactful quotes that embody the essence of Published Language, facilitating a deeper comprehension of this fundamental DDD concept. Bounded context and the ubiquitous language are the foundation of DDD.
A language structured around the domain model and used by all team members to connect all the activities of the team with the software. Evans 2003
updated: 05.01.2024
Patterns, Principles and Practices of Domain-Driven Design by Scott Millet and Nick Tune 2015
- p48: The language of the Business. Developers should think in domain terms and concepts, not technical terms, to avoid the need to translate from business jargon into technical jargon.
- P49: Not only must the development team learn the explicit terms and concepts from the business, but they must collaborate with the domain experts to define the assumed or implicit concepts that may not have terminology. These concepts must be named by the entire team and included in the shared UL.
- p130: Bounded context and the ubiquitous language are the foundation of DDD.
Domain-Driven-Design Tackling Complexity in the Heart of Software by Eric Evans 2003
- p: Within each BOUNDED CONTEXT, you will have a coherent dialect of the UBIQUITOUS LANGUAGE. The names of the BOUNDED CONTEXTS will themselves enter that LANGUAGE so that you can speak unambiguously about the model of any part of the design by making your CONTEXT clear.
Implementing Domain-Driven Design by Vaughn Vernon 2013
- p22: If there is a single “invention” Evans delivers to the software development community, it is the Ubiquitous Language. At a minimum he brought the Ubiquitous Language out of the dusty archives of design wisdom.
Learning Domain-Driven Design by Vlad Khononov 2021
- p24: Domain-driven design proposes a better way to get the knowledge from domain experts to software engineers: by using a ubiquitous language.
- p25: It’s crucial to emphasize that the ubiquitous language is the language of the business. … No technical jargon!
- p211: The use of a ubiquitous language is the cornerstone practice of domain-driven design. It is essential for domain knowledge discovery, communication and effective solution modeling.
Best Practice – An Introduction To Domain-Driven Design by Microsoft 2009
- p: These domain experts use company- or industry-standard terminology. In DDD, this vocabulary is called the Ubiquitous Language. As developers, you want to understand this vocabulary and not only use it when speaking with domain experts but also see the same terminology reflected in your code.
YouTube – Domain Modeling Made Functional – Scott Wlaschin – KanDDDinsky 2019
- Domain Model == code == documentation
Case Study: Large-Scale Marketing System – Vladik Khononov – DDD Europe 2020
- Ubiquitous language is the most important part of Domain Driven design. The core domain of DDD.
Domain Storytelling: A Collaborative, Visual, and Agile Way to Build Domain-Driven Software – Hofer, Schwenter – 2023
- Ubiquitous language: This language is derived from the domain language and is consistent within a bounded context. This language should be used everywhere (ubiquitously) — from the spoken words of the domain expert to the whiteboard to the code. Keep in mind that there are usually several ubiquitous languages in a company (one per bounded context). It is not a uniform, company-wide language.