Skip to main content Skip to complementary content

Metamodel Naming Standards

Object Names

Object names:

  • Must be unique throughout the repository
  • Become section headers and tab names in the object page for a custom model
  • Become Object Type in worksheets

For object names one should use:

  • Singular noun optionally preceded with an adjective
  • Short as possible while still unique.

Examples

  • Policy
  • Business Rule
  • Imported Object

Composition Role Names

A noun depicting the name of the child object.

The name is plural when the cardinality is Many and singular when the cardinality is 1 (“Parent” has “Child” or “Children”).

Examples

Order has Customer Address

Association Role Names

Association role names:

  • Must be unique for both the END1 and END2 objects
  • Become section headers and tab names in the object page for a custom model
  • Become Object Type in worksheets

For object names one should use:

  • Singular noun optionally preceded with an adjective
  • Short as possible while still unique.

A role name of a uni-directional relationship is a noun. It is plural when the cardinality is many.

A bi-directional relationship has one role name as noun and another one as a verb.

When there are multiple relationships to an object each role name should depict the name of the end2 object.

Examples

A Term has Synonym Terms.

A Term has Acronym

A Policy Is Enforced by Rules

A Term Defines Imported Objects

An Imported Object is Defined By Term s

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!