Synonyms, Homonyms, and Aliases

Not everyone speaks the same language. Not everyone is always precise in the use of names. Because names identify entities and attributes in a data model, verify that synonyms are resolved so that they do not represent redundant data. Precisely define names so that each person who reads the model can understand which facts are captured in which entity.

Select a name that clearly communicates a sense of what the entity or attribute represents. For example, there is some difference among things named PERSON, CUSTOMER, and EMPLOYEE. Although they can all represent an individual, they have distinct characteristics or qualities. The business user tells you whether PERSON and EMPLOYEE are two different things, or simply synonyms for the same thing.

Select names carefully, and be wary of calling two different things by the same name. For example, if a business area insists on calling its customers "consumers," do not insist on the customer name. Perhaps there is an alias, or there is a new "thing" that is distinct from, although similar to, another "thing." In this case, perhaps CONSUMER is a category of CUSTOMER that can participate in relationships that are not available for other categories of CUSTOMER.

You can enforce unique naming in the modeling environment. Unique naming avoids the accidental use of homonyms, ambiguous names, or duplication of entities or attributes in the model.