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

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
Trace::getTracedFrom(in ref)
Slide kind
SysML Requirement Diagram
This variation on the previous slide compares tagged value style and element property style in the MagicDraw SysML Plugin and Magic Cyber-Systems Engineer ® (Cameo Systems Modeler®) tools:
Click on the image to view it full size
We explore next briefly how the simple yet usable requirements verification and test engineering system of SysML works.
Up next
TestCase and Verify metamodel
Notes
[ISSUE] SysML-1.6: AbstractRequirement: direction of /tracedTo wrong in Attributes description
[CAVEAT, DISPLAY, STYLE, TOOL] MagicDraw/Cameo: the coloured stereotype icons for some kinds of elements can't be removed from all diagrams, tables, or matrix views
[DISPLAY, QUESTION, STYLE, TOOL] MagicDraw/Cameo: How disable icons in requirement relationship compartments and tagged values compartment on Requirement symbol?
[CAVEAT, DISPLAY, STYLE, TOOL] MagicDraw/Cameo: the coloured stereotype icons for some kinds of elements can't be removed from all diagrams, tables, or matrix views
[ISSUE] MagicDraw/Cameo 19SP3: uses PascalCase instead of lowerCamelCase on some SysML compartment names
[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]
  [SysML-1.6] Trace::getTracedFrom (in ref : NamedElement) : AbstractRequirement [0..*] The query getTracedFrom() gives all the requirements that are clients ("from" end of the concrete syntax) of a «Trace» relationship whose supplier is the element in parameter ...
Visit also
Visit also (backlinks)
There are six types of quarks (and six antiquarks)
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)
Protons are spin-1/2 fermions and are composed of three valence quarks, making them baryons
The neutron is classified as a hadron, because it is a composite particle made of quarks.
Radio frequencies (just a quick look)
Using Trace to quickly elicit model elements from an identified figure, drawing, diagram, plot, graphic, or table from a domain source document
Using a generic MagicDraw/Cameo query table to track /tracedTo for any NamedElement type using a derived relationship