Ubiquitous language
One shared vocabulary for a domain, used the same way by experts, developers and the code itself.
Eric Evans put it at the center of domain-driven design: the words people use in meetings are the words in class names, API fields and tests. If the business says “appointment” and the code says “slot reservation”, every conversation needs a translator and every translation is a chance for a bug.
The language is only ubiquitous inside one bounded context. “Visit” can mean a booked appointment in scheduling and a page view in analytics; that is fine as long as each context keeps its own meaning and the border between them is explicit. Event storming is a common way to discover the words. Sources: Martin Fowler, Evans, DDD Reference.
Sources
- Martin Fowler: Ubiquitous Language martinfowler.com
- Domain Language: DDD Reference domainlanguage.com
Related terms
- DDD (domain-driven design): Designing software around the business’s own language and rules, with the code split where that language changes meaning.
- Bounded context: A part of a system where each business term has one meaning and one model, with explicit translation at its edges.
- Event storming: A workshop where business and technical people map a process as a timeline of events on sticky notes to find rules, gaps and boundaries.
- Context map (DDD): A diagram of the bounded contexts in a system and the kind of relationship between each pair: who depends on whom and how models are translated.
- Domain expert: The person who knows how the business really works, such as a receptionist, an accountant or a doctor, and whose knowledge the software model has to capture.
