Webel Parsing Analysis: SysMLv1.x: Q: "Instead of using a Snippet extension of an ElementGroup, can't I just use a Requirement and Trace to achieve the same thing?" A: No! The ElementGroup extended as the Snippet is far more powerful and fit for purpose.
The requirement diagram is a new SysML diagram type. A requirement diagram provides a modeling construct for text- based requirements, and the relationship between requirements and other model elements that satisfy or verify them. Source OMG Systems Modeling Language (SysML) 1.6
AbstractRequirement::/master : AbstractRequirement [0..*] This is a derived property that lists the master requirement for this slave requirement. The master attribute is derived from the supplier of the Copy dependency ... Source OMG Systems Modeling Language (SysML) 1.6
The Copy relationship 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
The master/slave relationship is indicated by the use of the copy relationship. Source OMG Systems Modeling Language (SysML) 1.6
A slave requirement is a requirement whose text property is a read-only copy of the text property of a master requirement. The text property of the slave requirement is constrained to be the same as the text property of the related master requirement. Source OMG Systems Modeling Language (SysML) 1.6
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
MagicDraw/Cameo: If you must use the Documentation field in the specification dialog for a Requirement element DO NOT use it to state the Requirement because that is WET not DRY. Instead just use the Requirement 'name' and/or the 'text'.
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
A standard requirement includes properties to specify its unique identifier and text requirement. Additional properties such as verification status, can be specified by the user. Source OMG Systems Modeling Language (SysML) 1.6
The requirements modeling constructs are intended to provide a bridge between traditional requirements management tools and the other SysML models. Source OMG Systems Modeling Language (SysML) 1.6
The requirements diagram described in this clause can depict the requirements in graphical, tabular, or tree structure format. A requirement can also appear on other diagrams to show its relationship to other modeling elements. Source OMG Systems Modeling Language (SysML) 1.6
SysML provides modeling constructs to represent text-based requirements and relate them to other modeling elements. Source OMG Systems Modeling Language (SysML) 1.6
The example in Figure 16-6 is taken from the automotive safety domain, and shows a Burnish requirement contained in the NHTSASafetyRequirements requirement. Note that the text of the Burnish requirement indicates a specific sequence of steps and transitio Source OMG Systems Modeling Language (SysML) 1.6
Copy::2_same_text The text property of the client requirement is constrained to be a read-only copy of the text property of the supplier requirement and this applies recursively to all subrequirements Source OMG Systems Modeling Language (SysML) 1.6
Copy::1_source_and_taget_are_requirements A Copy dependency may only be created between two NamedElements that have a subtype of the abstractRequirement stereotype applied Source OMG Systems Modeling Language (SysML) 1.6
When a Copy dependency exists between two requirements, the requirement text of the client requirement is a read-only copy of the requirement text of the requirement at the supplier end of the dependency. Source OMG Systems Modeling Language (SysML) 1.6
A Copy dependency created between two requirements maintains a master/slave relationship between the two elements for the purpose of requirements re-use in different contexts Source OMG Systems Modeling Language (SysML) 1.6
A Copy relationship is a dependency between a supplier requirement and a client requirement that specifies that the text of the client requirement is a read-only copy of the text of the supplier requirement. Source OMG Systems Modeling Language (SysML) 1.6
Figure 16-3: Links between requirements and design 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 SysML Requirement Diagram
Figure 16-2: Requirements Derivation 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 SysML Requirement Diagram
SysML-1.6: 'Figure 16-2: Requirements Derivation' indeed shows DeriveReqt but spec text refers to it only as 'an example of a compound requirement'
SysML-1.6: text on Requirement 'Test and procedure conditions' is mangled in 'Figure 16-2: Requirements Derivation' (was OK in SysML-1.5) [and also on Figure 16-6]
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
Figure D.14 - Requirements Relationships Expressed in Tabular Format (Table) 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: HSUV sample Slide kind MagicDraw/Cameo: table
Webel suggests using a verbose 'name' for leaf (child) Requirements but NO 'text' to prevent Single Source of Truth issues and for improved callout vs relationships (but this might not always work when syncing with external requirements management tools)
Figure D.11 - Establishing HSUV Requirements Hierarchy (containment) 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: HSUV sample Slide kind SysML Requirement Diagram
