This MetaAssociationType indicates that one object is modeled by another (Description-Procedure MetaAssociations, etc.). This means that when a diagram is extracted, the object it describes will also be extracted.

This MetaAssociationType indicates a reference in a diagram to an object which is not intrinsically part of the diagram. For example, processes in a Flowchart need to be extracted with the objects describing them (Messages), while Org-Units should be extracted without their contents (such as their Organizational Chart). The MetaAssociation connecting these org-units to the diagram is citation type.

This MetaAssociationType is an alias of a generic link and inherits its behavior.

In this case, behavior need only be defined on the generic MetaAssociation. This being so, certain MetaAssociationTypes are no longer used. This is the case for example of "Documentation" and "Annotation" MetaAssociationTypes.

The dependency between the objects concerned is also strong in this case, but the component can exist without the aggregated object, for example: org-units of a flowchart, which can exist in an organizational chart even after the flowchart no longer exists.

These links are processed as for a composition link, except for deletion (the component should not be deleted since it may be used elsewhere) and copying (the component is linked to the copy without itself being copied).

The link is indispensable in understanding the defined object, for example: synchronization to message. Adding specifications to Message has no effect on synchronization. However, deleting the Message makes Synchronization null and void.

The MetaAssociation to the minor object is processed as for a description link (see below). The major object should be deleted when the minor object is deleted.

This MetaAssociationType represents time sequencing of two independent phenomena. Modification or deletion of one of the objects has no impact on the other. Example: Next operation.

These MetaAssociations express exchange of a flow or message between two objects. Example: Message exchanged between two org-units.

These MetaAssociations enable classification of objects using tags or other criteria.

Disappearance of the classification has no effect on the objects concerned.

These MetaAssociations express a check to be carried out on an object. Example: MetaAssociation between constraint and operation.

These MetaAssociations express transformation of an object from one type to another. Example: A class produces a table in a database.

These MetaAssociations express that one of the objects is a particular case of the other. The sub-type is the major object since it inherits all modifications to the super-type.

Extraction of the sub-type also necessitates extraction of the super-type.

These MetaAssociations express a strong relationship between two objects. Neither one has any meaning without the other. Example: link between role and association. The two objects are always extracted together.

These MetaAssociations express a strong dependency of one object on another. Example: MetaAssociation between package and class or between database and table. Deletion of the major object also deletes the minor.

This MetaAssociationType enables connection of a variant to the object of which it is a variant.