liveBook · Manning

Ubiquitous language

As explained in Effective Behavior-Driven Development

A shared vocabulary used by domain experts and software practitioners to describe business concepts and system behavior consistently.

Ubiquitous language is a shared vocabulary rooted in a domain, used by business and delivery teams to describe concepts and system behavior consistently. It reduces the need to translate between competing terms and the risk of misunderstanding. section 6.1

Use domain language to make specifications clearer and more useful:

  • Name business concepts rather than implementation details: describe the number of items in a basket, not a display element called BasketItemCount. section 7.5
  • Describe intent rather than mechanics: say a customer chooses to pay on collection, rather than specifying that they click a particular control. section 7.5
  • Carry business terminology through specifications, implementation, and diagnostic output wherever possible. section 12.4.6
Listing 7.5 Fourth edit – business language
Scenario: Unauthenticated customer chooses to pay on collection
  Given the customer has "1 item" in "BasketItemCount"
  Given the customer has 1 item in their basket
  When they click "Checkout"
  And they select "Collect" from "DeliveryInstructions"
  And they have chosen to collect their order
  When they proceed to payment instructions
  Then "Pay on Collection" should be available from "PaymentOption" 
  Then they should be able to choose to pay on collection

Compare the implementation-heavy scenario with its business-language revision: the revised wording expresses the customer's intention and the pay-on-collection rule. section 7.5

How Effective Behavior-Driven Development covers it

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 it assumes
Assumes collaboration between business and delivery representatives, while grounding vocabulary in the relevant domain.
What you can do after
Apply it by rewriting scenarios in business terms that express user intent instead of implementation mechanics.
How it connects
Connects to Domain-Driven Design, Behavior-Driven Development, formulation, and scenario automation.

Also explained in

Compare how 8 books explain ubiquitous language →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Behavior-Driven Development. The section links point to the parts of the book it draws on.