Learn about Webel's comprehensive SysMLv2 Workshop Seminar course!
Webel now has a SysMLv2 Online Self-Study course with self-test Quizzes!
Learn about the Webel Q&A     online self-testing system for SysML v2/v1

SysML2.0: Links to specification, Annex, and SysMLv2 GitHub PILOT code examples that directly use an ISQ «attribute def» as attribute type (an opposed to subsetting the ISQ «attribute» equivalent).

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
MODELLING
Policy level
EDITORIAL
Specification keywords
SysMLv2
SysMLv2 keywords
AttributeDefinition
AttributeUsage
feature typing
ISQ
There is also a full discussion of this in the Webel SysMLv2 course:
Course: Model-Based Systems Engineering with OMG Systems Modeling Language® (v2) and Cameo Systems Modeler (CATIA Magic™) for SysMLv2
The gist is that since coverage of specific kinds of quantities in «attribute» form is not complete anyway, one might as well just use an «attribute def» as type:
Webel: SysMLv2: For a quantity «attribute» prefer feature typing by an ISQ «attribute def» over subsetting of an ISQ «attribute» (the names of which don't cover all cases anyway so eventually you'll need to use the feature typing approach).
The SysMLv2 samples, Annex, and SysMLv2 PILOT GitHub examples use both forms (and not necessarily consistently):
ISSUE: SysMLv2.0 spec Annex example and multiple SysMLv2 PILOT GitHub samples: Inconsistent use of subsetted ISQ «attribute» (has multiplicity [*] in Cameo) without explicit multiplicity. According to SysML2.0 spec. rules would inherit multiplicity [*].
Relates to
25. Transitions: Change and Time Triggers.sysml
Related notes
Related notes (backlinks)
Related snippets (extracts)
Visit also
OMG Systems Modeling Language TM (SysML®) Version 2.0 formal/2025-09-03 (Sep 2025)
Visit also (backlinks)