The naming of relationships in a conceptual data model

31. Each relationship is named using two sentences of the following forms:

Each VEHICLEmust bewithinone and only oneVEHICLE CLASS.

Each VEHICLE CLASSmay beclassification forone or moreVEHICLES.

where:

• in the first sentence:

  must be represents the fact that the entity type VEHICLE has mandatory participation with respect to this relationship, represented by a solid line on a conceptual data model diagram.

  within is the link phrase associated with the entity type VEHICLE.

  one and only one represents the fact that only one instance of the entity type VEHICLE CLASS can be associated with any one instance of the entity type VEHICLE through this relationship, represented by the absence of a crow’s foot on a conceptual data model diagram.

• and in the second sentence:

  may be represents the fact that the entity type VEHICLE CLASS has optional participation with respect to this relationship, represented by a dashed line on a conceptual data model diagram.

  classification for is the link phrase associated with the entity type VEHICLE CLASS.

  one or more represents the fact that many instances of the entity type VEHICLE can be associated with any one instance of the entity type VEHICLE CLASS through this relationship, represented by a crow’s foot on a conceptual data model diagram.

32. Uniqueness of relationship names within the common data architecture is to be achieved as follows:

1. Relationship names are to be unique within a conceptual data model.

2. The concatenation of the name of the conceptual data model with the relationship name provides a unique name for each relationship within the common data architecture.

33. Abbreviations are not used in relationship names.