Using a generic MagicDraw/Cameo query table to track /tracedTo for any NamedElement type using a derived relationship Gallery Tutorial TRAIL: Theory and best practices for the Webel Parsing Analysis recipe for SysMLv1.6+ Section Slide kind MagicDraw/Cameo: table table
Webel Parsing Analysis: Pseudo Semantic Triple: When «pa:triple» is applied to a named uni-directional Association the name and a consistent direction arrow should be displayed on the Association symbol in diagrams.
Webel Parsing Analysis: Pseudo Semantic Triple: For «pa:triple» applied to a named one-to-one Dependency, the source is the subject, the name of the Dependency is the predicate, the target is the object.
Webel Parsing Analysis: Pseudo Semantic Triple: For «pa:triple» applied to a named one-to-one or one-to-many uni-directional Association, the non-navigable end Property is the subject, the name is the predicate, the navigable end Property is the object.
Webel Parsing Analysis: The name of a Parsing Analysis Diagram (PAD) may be drawn from a focus Snippet OR may simply indicate a topic of interest to the analysis
Webel: SysML: DO NOT sacrifice modelling naming conventions for the mere sake of carrying organisation-specific names! Instead use tagged values of custom stereotypes as metadata to carry alternative names in parallel with systematic model element names.
SysML/SysPhS-1.1: Anonymous Property or Action names may not be an option if: You are exporting to Modelica or Simulink; You absolutely need names for generated query reports (such as generated Interface Control Documents).
A Usage is a Dependency in which the client Element requires the supplier Element (or set of Elements) for its full implementation or operation. Source Unified Modeling Language 2.5.1
This means that the complete semantics of the client Element(s) are either semantically or structurally dependent on the definition of the supplier Element(s). Source Unified Modeling Language 2.5.1
A Dependency is a Relationship that signifies that a single model Element or a set of model Elements requires other model Elements for their specification or implementation. Source Unified Modeling Language 2.5.1
Property is indirectly a kind of RedefinableElement, so Properties may be redefined. The name and visibility of a Property are not required to match those of any Property it redefines. Source Unified Modeling Language 2.5.1
The name of a «testCase» Behavior may be verbose and may use natural language, but should always start with a Capital letter.
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 ... Source OMG Systems Modeling Language (SysML) 1.6
In SysML more than one NamedElement can help Satisfy a single Requirement (which presents challenges for verifying satisfaction of Requirements). This is a conceptual challenge for requirements engineering in general, not just SysML!
A basic Requirement is an AbstractRequirement Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 16:01: Requirements engineering in SysML Slide kind UML Profile Diagram
A most basic Requirement with a 'name', an 'id', and 'text' Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 16:01: Requirements engineering in SysML Slide kind SysML Requirement Diagram
Figure 16-1: Abstract Syntax for Requirements Stereotypes Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6 specification diagrams: 16 Requirements Slide kind UML Profile Diagram
Allocate is directional in that one NamedElement is the "from" end (no arrow), and one NamedElement is the "to" end (the end with the arrow). Source OMG Systems Modeling Language (SysML) 1.6
Allocate is a stereotype of a UML4SysML::Abstraction that is permissible between any two NamedElements. It is depicted as a dependency with the "allocate" keyword attached to it. Source OMG Systems Modeling Language (SysML) 1.6
Message::signature : NamedElement [0..1] ... The signature of the Message is the specification of its content. It refers either an Operation or a Signal. Source Unified Modeling Language 2.5.1
