Ubiquitous language
A ubiquitous language is a shared, consistent vocabulary for expressing concepts within a domain.
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
A ubiquitous language is a shared, precise vocabulary used consistently by domain experts and software developers within a bounded context.
- How it is used
- Aligns domain experts and developers on business terminology during domain modeling and modernization.
- How deep it goes
- Develops workshop practices for defining terms and testing names, but does not prescribe a formal glossary or naming standard.
- Examples
- Uses airline domain naming, EventStorming event distinctions, and a bounded context canvas terminology exercise.
- What you can do after
- Practice/perform collaborative naming and terminology checks to expose misunderstandings and improve stakeholder communication.
Collaborative Software Design: How to facilitate domain modeling decisions
A ubiquitous language is an unambiguous vocabulary shared by domain stakeholders and software developers for expressing domain concepts and design decisions.
- How it is used
- Aligns stakeholders and software teams around unambiguous domain concepts and explicit design decisions.
- How deep it goes
- Defines the language, demonstrates ambiguity cleanup, and connects it to models and bounded contexts without detailing tactical code implementation.
- Examples
- Uses ticket purchases, themed days, “Seats paid,” “Ticket Sold,” and a Business Model Canvas to refine terminology.
- What you can do after
- Apply it via collaborative modeling to expose ambiguous terms, negotiate definitions, and record clearer domain models.
AI-Powered Search
A domain-specific phrase is a multiword expression whose meaning or usage is characteristic of a particular subject area.
- How it is used
- Improves query interpretation and relevance by identifying phrases whose combined meaning matters.
- How deep it goes
- Describes query tokenization and filtering, while noting that short queries limit parsing and application-specific patterns may need custom logic.
- Examples
- Uses “new york city” to illustrate separate-word matching and query sequences such as “iphone” and “pink iphone case” to illustrate related searches.
- What you can do after
- Build a semantic search layer that models phrases, extracts them from queries, and uses them in query rewriting.
Effective Behavior-Driven Development
A shared vocabulary used by domain experts and software practitioners to describe business concepts and system behavior consistently.
- How it is used
- Documents shared understanding of expected behavior in clear, domain-rooted terms for stakeholders and future readers.
- How deep it goes
- Defines the shared-language principle and demonstrates replacing UI details and mechanics with business concepts and intent.
- Examples
- Contrasts BasketItemCount with basket contents and UI clicks with choosing to pay on collection.
- What you can do after
- Apply it by rewriting scenarios in business terms that express user intent instead of implementation mechanics.
Read how Effective Behavior-Driven Development explains ubiquitous language →
Automating API Delivery
Ubiquitous language is a shared vocabulary used consistently by a development team and domain stakeholders to describe a domain and its software.
- How it is used
- Guides API design reviews by aligning resources, operations, attributes, and documentation with domain terminology.
- How deep it goes
- Defines shared domain vocabulary and applies it to API review, but does not prescribe a separate vocabulary-management process.
- Examples
- Uses resource names, attribute names, rendered API documentation, descriptions, and example values as terminology checkpoints.
- What you can do after
- Evaluate API terminology for consistency with the domain model and communicate corrections through design-review comments.
Read how Automating API Delivery explains ubiquitous language →
BDD in Action, Second Edition
A ubiquitous language is a shared vocabulary that domain experts and software professionals use consistently to describe and model a business domain.
- How it is used
- Uses shared domain vocabulary to express requirements and model system behavior in terms businesspeople can understand.
- How deep it goes
- Defines the shared vocabulary and applies it to acceptance scenarios and automation, without detailing how to develop the vocabulary.
- Examples
- Illustrates the approach with a customer funds transfer and scenarios that state expected behavior.
- What you can do after
- Apply shared vocabulary to define requirements as scenarios that can become automated acceptance criteria.
Read how BDD in Action, Second Edition explains ubiquitous language →
The Well-Grounded Data Analyst
Business terminology is the agreed meanings of domain-specific terms used by people involved in an analysis.
- How it is used
- Clarifies stakeholder questions and domain terms before analysis or data modeling.
- How deep it goes
- Defines terms through stakeholder discussion and documentation, then encodes them in data models; it stops short of prescribing a universal vocabulary.
- Examples
- Uses ambiguous dates, sales and returns, customer identity, and business metrics to expose competing meanings.
- What you can do after
- Apply agreed terminology to frame measurable questions, document assumptions, and create more consistent analytical data models.
Read how The Well-Grounded Data Analyst explains ubiquitous language →
The Art of Code
Domain-specific vocabulary is the terminology established by a problem domain for naming its entities and concepts.
- How it is used
- Guides variable naming by keeping domain vocabulary consistent across code.
- How deep it goes
- Explains naming guidance with examples but does not develop a broader domain-modeling method.
- Examples
- Contrasts user with client or visitor, and selectedUsersForExclusiveGift with generic identifiers.
- What you can do after
- Apply consistent domain terms when naming variables so their purpose is clearer.
Also covered in
- Test Driven: Practical TDD and Acceptance TDD for Java Developers
- Unit Testing Principles, Practices, and Patterns
- Spec-Driven DevelopmentIn early access (MEAP)
- Building Specialized AI SystemsIn early access (MEAP)
- Building User-Friendly DSLs
- Practices of the Python Pro
- Simple Object-Oriented Design: Create clean, maintainable applications
- Investing for Programmers
- Crack Any Codebase with AIIn early access (MEAP)
- The Design of Web APIs, Second Edition
What to know first
- domain-driven designDomain-driven design is a software design approach that centers models, structure, and terminology on the concepts, behavior, and boundaries of a problem domain.
- stakeholderA stakeholder is a person, group, or organization with an interest in, influence over, or potential to be affected by a system, project, decision, or its outcomes.
- bounded contextA bounded context is a defined boundary within which a domain model, terminology, and associated rules have consistent meaning and application.
- cognitive loadCognitive load is the mental effort required to process information, retain it in working memory, or perform a task.
Related concepts
- BRIEFpart of · A six-principle mnemonic for writing concise, business-oriented behavior scenarios: Business language, Real data, Intention revealing, Essential, Focused, and Brief.
- contextpart of · Context is the relevant information, state, or circumstances surrounding an input, decision, or activity that influence its interpretation or behavior.
- domain-driven designused by · Domain-driven design is a software design approach that centers models, structure, and terminology on the concepts, behavior, and boundaries of a problem domain.
- acceptance testingused by · Acceptance testing evaluates whether a system satisfies specified user, business, or stakeholder requirements and acceptance criteria.
- scenarioused by · A scenario is a specified or described situation, sequence of events, or set of conditions used to represent or examine behavior, processes, or possible outcomes.
- role assignmentproduced by · Role assignment is a prompting technique that directs a model to respond from a specified role, perspective, expertise, or voice.
Questions about ubiquitous language
What is ubiquitous language?
A ubiquitous language is a shared, consistent vocabulary for expressing concepts within a domain.
Which Manning books explain ubiquitous language?
Architecture Modernization: Socio-technical alignment of software, strategy, and structure, Collaborative Software Design: How to facilitate domain modeling decisions, AI-Powered Search, Effective Behavior-Driven Development, Automating API Delivery, BDD in Action, Second Edition, The Well-Grounded Data Analyst and The Art of Code.
What should I know before learning ubiquitous language?
Manning books that teach ubiquitous language usually introduce domain-driven design, stakeholder, bounded context and cognitive load first.
What is ubiquitous language part of?
Ubiquitous language is part of BRIEF. A six-principle mnemonic for writing concise, business-oriented behavior scenarios: Business language, Real data, Intention revealing, Essential, Focused, and Brief.
What is ubiquitous language also called?
Ubiquitous language is also called domain language, shared language, domain-specific vocabulary or shared vocabulary.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.







