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

SysMLv2 Specification and GitHub examples: CONSISTENCY TRACKER: Links to examples where an action or state (usage or definition) redefines an in parameter but does not provide a value (either directly or through binding)

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
in parameter
redefinition
Relates to
24. States: State Actions.sysml
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).
[CONVENTION, MODELLING]{EDITORIAL} SysMLv2 Specification and GitHub examples: CONSISTENCY TRACKER: Links to examples where a performed action DOES NOT redefine any parameters and/or DOES NOT provide values (either directly or through binding) for any parameters in the performance context
[CONVENTION, MODELLING]{EDITORIAL} SysMLv2 Specification and GitHub examples: CONSISTENCY TRACKER: Links to examples where a performed action DOES redefine the parameters and DOES provide values (either directly or through binding) for the parameters in the performance context
[CONVENTION, MODELLING]{EDITORIAL} 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.
[MODELLING, OPTION]{OPTION} 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 always necessary (confirmed by SysMLv2 samples)
Related notes (backlinks)
Related snippets (extracts)
  [KerMLv1] 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)
  [KerMLv1] 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)