SYSML17 — SysML stereotype notation creates ambiguity about to which element is the stereotype applied

The SysML notation allows a stereotype <<S>> applied to an element E1 to be shown as the notation for a different element E2 related to E1 in some way.

Example: 11.3.1.2 CallBehaviorAction and Figure 11.2:

Stereotypes applied to behaviors may appear on the notation for CallBehaviorAction when invoking those behaviors, as

shown in Figure 11.2.

What this means is that if a CallBehaviorAction shows a stereotype <<S>>, then it is unclear whether <<S>> is applied to the CallBehaviorAction itself or to the behavior that the CallBehaviorAction calls.

This ambiguity is problematic for users reading SysML diagrams as indicated by SysML issue 17549:

Table 11.1 on pg. 93 shows that the «controlOperator» stereotype can be applied

to a call behavior action (when that call behavior action calls an activity that also

has the «controlOperator» stereotype applied).

More generally, the SysML spec needs to be reviewed where this stereotype notation can result in this kind of ambiguity.

Defer

Issue deferred