Notes:
- "columns" of related packages arranged to better reflect systems engineering process:
- left to right from Requirements through Structure to Behavior and Test
- extra packages Test and Configuration
- ValueTypes and FlowTypes model libraries isolated in ModellingDomain package independent of Hybrid SUV
Visit also detailed annotated version of Figure B.3 with explanations and amendments to SysML1.0 spec.
TIP: I recommend against naming packages verbosely to include a reusable name as prefix:
HSUVStructure, HSUVBehavior, HSUVAnalysis, HSUVViews...
Instead, simply "trust the owner name" and display it with the packages:
Structure (HSUV), Behavior (HSUV), Analysis (HSUV), Views (HSUV)
The top-level "system package" then reads more like a Class with "one of each thing" in it, and if you rename the top-level "system package" all diagrams catch it, and you won't have to rename all the subpackages.
Image:
