Domain context modeling is the practice of documenting where a business term, object model, or rule applies and how information moves between contexts. It helps product teams design workflows where different groups work with related information but need different meanings, rules, or levels of detail.
A useful concept from domain-driven design (DDD) is the bounded context, the boundary within which a model applies. Within that boundary, the people doing the work and the people building the software can agree on what their terms mean and how the modeled things behave.
A trip in sales and ticketing
Suppose a travel operations tool serves a sales team that proposes itineraries and a ticketing team that manages supplier bookings. Both teams refer to the same trip, but an accepted offer and a confirmed booking describe different events.
| Question | Sales | Ticketing |
|---|---|---|
| What does the team work with? | Trip and Offer, including proposed itineraries and quoted prices | Booking and its supplier reference, status, and fare rules |
| What decision matters? | Is this the offer the traveler wants to accept? | Is the supplier booking confirmed, and can it be changed? |
| What should the team own? | The accepted offer and the details agreed with the traveler | The supplier confirmation and booking status |
At handoff, ticketing receives the accepted itinerary and trip reference. Ticketing links each booking to that trip. When a supplier confirms a booking, sales can see its confirmation status alongside the accepted offer.
How do you model a domain context?
Look for changes in language, rules, and ownership when you draw a model boundary. The sales and ticketing teams illustrate a possible boundary in this example.
- Follow a handoff. Observe what each team calls the work, what it decides, and what it needs from the other team.
- Document the model and its scope. Record terms, objects, key relationships, and the rules that apply to them in an Object Guide. Identify where the same word carries different meanings.
- Agree on what crosses the boundary. Specify identifiers, status mappings, and which team or system updates each shared fact.
- Test an exception. Walk through a supplier rejection after a traveler accepts an offer. Check that each team can understand the situation and continue its work.
How does this relate to OOUX?
OOUX helps a team identify the objects people recognize and work with. Domain context modeling helps the team decide where a particular definition or rule holds. An object map for ticketing can then show Booking in the context of the people who manage it.