Learn about Webel's comprehensive SysMLv2 Workshop Seminar course!
VIDEO: The Webel SysMLv2/MBSE course has landed! Take a quick tour!
Webel now has a SysMLv2 Online Self-Study course with self-test Quizzes!

SysMLv2 Specification and GitHub examples: CONSISTENCY TRACKER: Links to examples where action (usage or definition) in parameters are redefined but the out parameter is not.

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
CONVENTION
MODELLING
Policy level
EDITORIAL
Specification keywords
SysMLv2
SysMLv2 keywords
SysMLv2GitHub
in
out
in parameter
out parameter
redefinition
To understand the purpose of this tracker with links to relevant slides with examples and "counter examples" please read carefully the discussion under:
SysML2.0: Webel: Suggest the entire description in the specification of whether and when usages MUST redefine inherited parameters needs an overhaul (and the SysML2.0 spec examples, Annex problem, and SysMLv2 GitHub examples are inconsistent anyway).
Note also that although a calculation is a special kind of action, they are excluded from this tracker because the result parameter is never "redundantly" redefined in any known examples. And since cases (such as analysis cases, verification cases, and use cases) are special kinds of calculations they are likewise excluded from this tracker.
Relates to
Related notes
[ASSERTION, ISSUE, PROPOSAL]{PROPOSED} SysML2.0: Webel: Suggest the entire description in the specification of whether and when usages MUST redefine inherited parameters needs an overhaul (and the SysML2.0 spec examples, Annex problem, and SysMLv2 GitHub examples are inconsistent anyway).
[ISSUE, PROPOSAL]{PROPOSED} SysMLv2: Webel: Redefining a parameter or port (or a directed feature of such) in a binding connector's context provides a "clean" binding target (as opposed to binding to an inherited feature). BUT It's not 100% clear whether it's necessary [TBD]
Related notes (backlinks)
Related snippets (extracts)
  [SysMLv2] the KerML checkFeatureParameterRedefinition constraint requires that any owned parameters ... of a ActionUsage redefine corresponding parameters of any Behaviors or Steps it specializes (including ActionDefinitions and ActionUsages)
  [SysMLv2] checkFeatureResultRedefinition: If a Feature is a result parameter of an owningType that is a Function or Expression, then, for each direct supertype of its owningType that is also a Function or Expression, it must redefine the result parameter
  [SysMLv2] If an action definition has a single superclassification, then the specialized action definition may declare fewer owned parameters than the general action definition, inheriting any additional parameters from the general definition ...
  [SysMLv2] If an action usage has any type of specialization relationship ... with an action definition or usage ... the rules for the redefinition of the parameters ... are the same as given for the redefinition of parameters of an action definition ...
Visit also
Visit also (backlinks)