Webel Parsing Analysis for SysML: "Snippet trumps Requirement": A SysML Requirement element is just another model element that is elicited IN PARALLEL WITH other elements that a text description mentions in any way as being involved with or related to it.
SysMLv1 (or v2): CHALLENGE EXERCISE: Simplified Parsing Analysis breakdown of 'Build an Airport' with variations
Webel: SysMLv2: WISHLIST: Manage "cascading" Satisfy claim vs Block inheritance hierarchy with redefined properties
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.
«physicalRequirement»: satisfied by a structural element. Source OMG Systems Modeling Language (SysML) 1.6
«performanceRequirement»: satisfied by a value property. Source OMG Systems Modeling Language (SysML) 1.6
«interfaceRequirement»: satisfied by a port, conector, item flow, and/or constraint property. Source OMG Systems Modeling Language (SysML) 1.6
«functionalRequirement»: satisfied by an operation or behavior Source OMG Systems Modeling Language (SysML) 1.6
The SysML non-normative extended requirements are NOT offered as the ultimate set of requirements categories or requirements fields, but they are highly usable and can be easily adapted.
The non-normative extended requirements 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
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 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
Since the concept of requirements reuse is very important in many applications, SysML introduces the concept of a slave requirement. Source OMG Systems Modeling Language (SysML) 1.6
The use of namespace containment to specify requirements hierarchies precludes reusing requirements in different contexts since a given model element can only exist in one namespace. Source OMG Systems Modeling Language (SysML) 1.6
Composite (a.k.a. "compound") Requirements 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
MagicDraw/Cameo: A Requirement may appear on many kinds of such as a Block Definition Diagram or Package Diagram, not just a Requirement Diagram
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
Examples of additional non-normative stereotypes based on AbstractRequirement are included in E.8. Source OMG Systems Modeling Language (SysML) 1.6
The only normative stereotype based on AbstractRequirement is the Requirement stereotype, ... Source OMG Systems Modeling Language (SysML) 1.6
An AbstractRequirement establishes the attributes and relationships essential to any potential kind of requirement. Any intended requirement kind should subclass AbstractRequirement. Source OMG Systems Modeling Language (SysML) 1.6
Satisfy::getSatisfies (in ref : NamedElement) : AbstractRequirement [0..*] Source OMG Systems Modeling Language (SysML) 1.6
Satisfy::1_supplier_is_requirement The supplier shall be an element stereotyped by any subtype of «AbstractRequirement». Source OMG Systems Modeling Language (SysML) 1.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
Subrequirements shall be accessed through the "nestedClassifier" property of a class. Source OMG Systems Modeling Language (SysML) 1.6
The default interpretation of a compound requirement, unless stated differently by the compound requirement itself, is that all its subrequirements shall be satisfied for the compound requirement to be satisfied. Source OMG Systems Modeling Language (SysML) 1.6
Compound requirements can be created by using the nesting capability of the class definition mechanism. Source OMG Systems Modeling Language (SysML) 1.6
A requirement is a stereotype of both Class and Abstract Requirement. Source OMG Systems Modeling Language (SysML) 1.6
