Setting Relationships of Stereotypes

A stereotype can be distinguished from its metaclass or other stereotypes not only by its stereotype properties, but also by the fact that it can limit the amount of elements which can have a predefined relationship to it to one subset.

MOF-compliant specifications distinguish a stereotype from its metaclass or other stereotypes by OCL constraints; it can limit the amount of elements which can have a predefined relationship to it to one subset.

Permissible elements are permitted or rejected in the configuration of an Innovator model. You can use the owning assignment to set e.g. which stereotype model elements should be from so that they are permissible in the model as contents for a model element of the respective stereotype; which is, therefore, Owner and which Assigned Element.

You need to be in the  Relationships view when constraining relationship roles to certain stereotypes.

An inverse role exists for certain relationship roles; it can be used to configure the same relationship from the view of the opposing metaclass. Constraints in a relationship role also automatically have an effect on inverse roles. This means that the inverse roles do not have to be separately configured.

If you assign the stereotype of a directed relationship to an initial node in the Assigned Elements role, the directed relationship is also assigned the initial node's stereotype as Owner at the same time. The same applies when setting a stereotype as the target of the directed relationship; the directed relationship's stereotype is then set as the Incoming Relationship of the target node's stereotype at the same time.

Assignment takes place using drag-and-drop between the Allowed and Not Allowed areas; you can insert the element anywhere you want, as the element is automatically inserted in the correct position. Missing subtrees are automatically created.

You can deactivate the View>Imported Entries toggle command to restrict the selection on the right-hand side to the entries defined in the current profile in this view.

Use the Edit>Ignore toggle command to mark permissible relationships as "ignored" within an imported profile. These relationships are then treated as if they were never created.

This chapter contains the topics: