1

When my team works on a project they usually come up with multiple names for the same thing. For example, if we have an Apartment entity, you might find some referring to it as an Apartment and others referring to it as a Flat. And so you see different names for the same thing in documents, database, code, and interfaces. I'm usually trying in the beginning of a project to force the idea of having a document to define unified terminologies for the team to stick with it. I'm wondering is there a known practice for something like that?

Unsuccessful Scrum Master
  • 23
  • 3
  • Let me share what a consultant at a previous company told me. "In programming tautology is not frowned upon. It is COMPULSORY". Here's another quote: "use slightly different names for ... variables" – Vorac Jul 07 '21 at 05:31

1 Answers1

1

I think you are looking for Ubiquitous Language from Domain Driven Design.

Ubiquitous Language is modeled within a Limited context, where the terms and concepts of the business domain are identified, and there should be no ambiguity.

Bogdan
  • 15,216
  • 27
  • 48