Eric Evans’ idea of Ubiquitous Language is simple but powerful: the team needs a shared model and vocabulary for the problem domain. That model should be understandable to everyone: the builders, managers, operations, and the customers. So that the conversations, designs, and tests all line up.
Maintain a living “data dictionary” with concise terms that describe the data and the processes that change it.
Discussions for your team
- Do we currently have names for the core domain concepts that make sense to everyone?
- Where can we capture and store terms in a shared glossary?
- Do we use this language in our acceptance tests?