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 Giventhe customer has "1 item" in "BasketItemCount"Given the customer has 1 item in their basket Whenthey click "Checkout"Andthey 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







