Trace used for model element elicitation - callout style

This is one useful way to track elicitation of model elements, but you have to get the direction right, because /tracedTo is only defined on AbstractRequirement, whereas getTracedFrom() works against any NamedElement.

Click on the image to view it full size

The elicited block RemoteControl is implied by the 'name' and 'text' of the Requirement, and can be traced in the model "back" to it; we have a very simply yet effective form of parsing analysis!

The Trace strategy can also be combined with the ElementGroup-based Webel Parsing Analysis recipe for SysML^®.

We'll see next some alternative notations.

BTW: Just ignore this known spec error (the tool gets it right):

SysML-1.6: AbstractRequirement: direction of /tracedTo wrong in Attributes description

Up next

Trace used for model element elicitation - tagged value and element property styles

Notes

[ISSUE] SysML-1.6: AbstractRequirement: direction of /tracedTo wrong in Attributes description

[ISSUE, LIMITATION, WARNING]{INFORMATIVE} The SysML1.6 derived /tracedTo is only available on AbstractRequirement (but in MagicDraw/Cameo you can use derived relationships to achieve the same thing on other kinds of NamedElement).

Snippets (quotes/extracts)

[SysML-1.6] The Trace stereotype specializes UML4SysML Trace and DirectedRelationshipPropertyPath to enable traces to identify their sources and targets by a multi-level path of accessible properties from context blocks for the sources and targets.

[SysML-1.6] AbstractRequirement::/tracedTo : NamedElement [0..*] Derived from all elements that are the client of a «trace» relationship for which this requirement is a supplier. (derived) [ERROR]