Requirements and the Trace relationship - metamodel

Gallery
Tutorial
TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo
Section
16:01: Requirements engineering in SysML
UML keywords
Trace
SysML keywords
Requirement
AbstractRequirement::/tracedTo
Trace
Slide kind
SysML Requirement Diagram
SysML extends the notoriously vague (but nevertheless useful) UML Trace relationship primarily - but not only - for use with the Requirement system:
Click on the image to view it full size
Trace can be used for many things (some might say for too many things); we look next at how it can be used effectively for elicitation of model elements from Requirements.
Up next
Trace used for model element elicitation - callout style
Notes
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]
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
Figure D.11 - Establishing HSUV Requirements Hierarchy (containment)
Figure D.12 - Establishing Derived Requirements and Rationale from Lowest Tier of Requirements Hierarchy
Figure D.13 - Acceleration Requirement Relationships
Figure 16-1: Abstract Syntax for Requirements Stereotypes
Figure 16-2: Requirements Derivation
Figure 16-3: Links between requirements and design
Related slides (backlinks, includes other tutorials)