Figure D.3 - Establishing Structure of the User Model using Packages and Views

I strongly recommend that you DO NOT imitate the naming conventions of this diagram! Repeating an acronym like HSUV everywhere is unnecessary and error prone. Instead, "Trust the Namespace", and where necessary show the owner or ancestor path using display options! In this diagram, the containment operators - together with an indication of the root owner 'HSUV Model' - are more than sufficient. And the same principle applies to the name 'DeliverPower Behavior' within 'HSUV Behavior'.

Note also that the property name hsuv:HybridSUV rather than HSUV:HybridSUV is used in accordance with: SysML: Naming: Always use either anonymous or first letter lower case for Property, ObjectNode and InstanceSpecification names; no exceptions (unless using names to "quote text")! Valid: 'lowerCamelCase' OR 'tla' vs TLA acronym OR 'uCC' vs UpperCamelCase

Up next

Figure D.4 - Establishing the Context of the Hybrid SUV System using a User-Defined Context Diagram

Notes

[ISSUE] ERROR: SysML-1.6: Figure D.3 Automotive Value Types model library does not belong under the HSUV Model, showing it on this diagram without showing the owner suggests it is. Compare with Figure D.2.

[ISSUE] ERROR: SysML-1.6: The name 'Operational Viewpoint' in Figure D.3 contradicts the name ''Functional Viewpoint' in Figure D.30 (suggest amend D.30 not D.3)

[ISSUE, QUESTION] SysML-1.6: Figure D.3: Would 'HSUV Interfaces' be better higher up directly under 'HSUV Model' (instead of under 'HSUV Structure')?

[NAMING, POLICY, STYLE]{STRONG} The Webel modelling style, naming conventions, and Best Practices for SysML are more consistent than most SysML spec diagrams. When following Webel courses please DO NOT use the spec sample diagrams (which serve a different purpose) as visual references!

[NAMING, POLICY]{STRONG} "Trust the Namespace" - DO NOT repeat information in names of owned elements that can be gleaned from the owner or ancestor (and is usually easily shown using display options). It is WET, it breaks the DRY principle!

[NAMING, POLICY]{STRICT} SysML: Naming: Always use either anonymous or first letter lower case for Property, ObjectNode and InstanceSpecification names; no exceptions (unless using names to "quote text")! Valid: 'lowerCamelCase' OR 'tla' vs TLA acronym OR 'uCC' vs UpperCamelCase

Snippets (quotes/extracts)

[SysML-1.6] The package diagram (Figure D.3) shows the structure of the model used to evaluate the sample problem.