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!

Webel Best Practice: SysMLv2: "Trust the Type": If redefining a port or parameter to provide a "clean" connection end target always also include the :Type in the redefinition declaration - and even if it's a bit tedious and a bit WET.

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
CONVENTION
MODELLING
PATTERN
STYLE
TIP
Policy level
STRONG
Specification keywords
SysMLv2
SysMLv2 keywords
redefinition
Parameter
port
port usage
Keywords

This policy support's Webel "Trust the Type" display modes in Cameo.

Note that the policy concerns cases where the redefinition is made solely to create "clean" end targets (as opposed to inherited end targets). The case of redefinition of parameters for provision of feature values (typically using feature value = binding shorthand) is covered under:

Visit also: Webel Best Practice: SysMLv2: "Trust the Type": If using parameter = shorthand to provide a feature always also include the :Type in the declaration (which is an implied redefinition) - and even if it's a bit tedious and a bit WET.
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).
[ASSERTION, MODELLING]{INFORMATIVE} SysMLv2: It is permissible to use a flow between compatible directed features of port usages without redefining inherited port usages (to create "clean" end targets) in the connection context
[ASSERTION, MODELLING]{INFORMATIVE} SysMLv2: It is permissible to use a flow between parameters of action usages without redefining inherited parameters in the connection context.
[DISPLAY, MODELLING, PATTERN, STYLE, TIP, TOOL]{STRONG} Webel Best Practice: SysMLv2: "Trust the Type" feature name hiding. In many Views, there is no benefit, at all, in showing feature names (especially if they are needlessly verbose and just repeat the Type name but lowerCase)
[MODELLING, PATTERN, STYLE, TIP]{STRICT} Webel Best Practice: SysMLv2: "Trust the Type" functional analysis: When referencing a performed action or exhibited state ALWAYS also include the :Type in the declaration (even if it's a bit tedious and a bit WET). Helps avoid also verbose usage names!
[CONVENTION, MODELLING, PATTERN, STYLE, TIP]{STRICT} Webel Best Practice: SysMLv2: "Trust the Type": When redefining a subject (within any element kind) ALWAYS also include the :Type in the redefinition declaration (even if it's a bit tedious and a bit WET).
[DISPLAY, MODELLING, PATTERN, STYLE, TIP, TOOL]{STRONG} Webel Best Practice: SysMLv2: VERY STRONG RECOMMENDATION: Prefer Webel "Trust the Type" i/o parameter naming and Webel display conventions over verbose parameter names. To find out how attend the Webel SysMLv2 course!
[DISPLAY, MODELLING, PATTERN, STYLE, TIP, TOOL]{STRONG} Webel Best Practice: SysMLv2: VERY STRONG RECOMMENDATION: Prefer Webel "Trust the Type" i/o port naming and Webel display conventions over verbose port usage names and verbose directed feature names. To find out how attend the Webel SysMLv2 course!
[ASSERTION, DISPLAY, NAMING, STYLE]{STRONG} Webel: SysMLv2: IMPORTANT! Specification documents and the namings used in their supporting examples have a specific purpose and the examples play specific roles. They are NOT tutorials on how to model practically in a specific tool on real projects!!!
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)