SysMLv1: Webel strongly recommends a looser, more "logical" modelling strategy over modelling practices with strong coupling to "physical" ownership. Many of the Webel Best Practices support this approach.

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
MODELLING
TIP
Policy level
RECOMMENDED
Specification keywords
SysML-1.2
SysML-1.3
SysML-1.4
SysML-1.5
SysML-1.6
SysML-1.7
UML-2.5.1
UML keywords
Element::owner
containment
containment operator
Keywords
Relates to
Related notes
[EXPLANATION, MODELLING, TIP] On the Webel Best Practice modelling tips for SysML (and UML). If you want to model the Webel way, use them, if you don't, ignore them. They are ONLY offered as options and graphical modelling paradigms and idioms for you to consider.
[MODELLING, TIP, TOOL, WARNING]{STRONG} SysMLv1/UML: Prefer owner path indicators over Package containment operators (which are fragile).
[DISPLAY, STYLE, TIP, TOOL]{RECOMMENDED} SysMLv1: Cameo: In Package Diagrams and Block Definition Diagrams use the owner indicator display option for Classifier symbol headers when indicating the owner (except where a containment operator suffices). The mode 'Below Element Name' is preferred.
[MODELLING, TIP]{RECOMMENDED} Webel: SysML/MBSE: Suggest don't fuss about ownership (containment) too much early on. Focus on "logical" modelling, values, flows, relationships between elements. Suggest perform regular separate modelling "housekeeping" sweeps to deal with ownership.
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)