A core part of Domain Driven Design is the consistent use of a ubiquitous language across the system - in conversations, code, database schema, UI, tests, etc.I'm involved in a project in which there is a well-established domain language already, defined by an international standards organisation.However, the work we're doing is for a public web site, and the 'correct' terms for the domain aren't necessarily how the public typically use and understand them.The compromise we're using at the moment is to use the 'official' terms everywhere, except for in our acceptance criteria which refer to UI components, where we use the informal names.Does this seem like a reasonable approach?
Ubiquitous Language - conflict between correctness and usability
documentation;domain specific languages