Share via

2.1.9 Association End

  • Article

For a given Association, the End element defines one side of the relationship. End defines what type is participating in the relationship, multiplicity or the cardinality, and if there are any operation associations, like cascade delete.

The following is an example of an End element.

     <End Type="Model1.Customer" Role="Customer" Multiplicity="1" />

The following rules apply to the Association End element:

  • End MUST define the EntityType for this end of the relationship.

  • EntityType is either a namespace qualified name or an alias qualified name of an EntityType that is in scope.

  • End MUST specify the Multiplicity of this end.

  • End can specify the Role name.

  • End can contain any number of AnnotationAttribute attributes. The full names of the AnnotationAttribute attributes cannot collide.

  • End can contain a maximum of one Documentation element.

  • At most, one OnDelete operation can be defined on a given End.

  • End can contain any number of AnnotationElement elements.

  • Child elements of End are to appear in this sequence: Documentation, OnDelete, AnnotationElement.

Graphic representation in table format of the rules that apply to the End element of a given Association.

All child elements are to appear in the order indicated.