Webel Radio Net: 'structure' SysML Package Diagram

Gallery
Tutorial
[TRAIL] SysMLv1: The Webel Radio Net port-based messaging example model in Cameo Systems Modeler and Cameo Simulation Toolkit
Section
Context and structural model for the RadioNet, NetSession, and RadioStation
Topic level
BASIC
SysML keywords
SysML Package Diagram
Keywords
Slide kind
SysML Package Diagram
A SysML Package Diagram for 'structure'. Note that in the Webel Radio Net model there is no formal systems engineering methodology treatment of the "problem" vs "solution" space, and no formal functional analysis breakdown via logical components mapped to separate components of the solution space.
Click on the image to view it full size
SysMLv1: Webel often uses Model packages for most modelling and reserves Package for code-like elements, OpaqueBehavior sub-libraries, instances, and elements reverse-engineered from code. But there are no hard and fast rules about Package vs Model.
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.

In addition to the RadioNetContext SystemContext block we see that there are the following Packages:

structure.channel: Blocks for generic communication channels and radio channels.

structure.net: The RadioNet system and supporting elements, including sub-packages for simulation and instances.

structure.station: The RadioStation block and supporting elements, including a sub-packages for simulation with some OpaqueBehaviors and utility Activities.

structure.hub: The generic signal routing AbstractHub block and support for using the Action Language Helper (ALH) API with Ports, and sub-packages for each of the specific scheduling message SHub and radio message RHub routing hubs.

Up next
Webel Radio Net: 'channel' SysML Package Diagram
Notes
[MODELLING, OPTION]{INFORMATIVE} SysMLv1: Webel often uses Model packages for most modelling and reserves Package for code-like elements, OpaqueBehavior sub-libraries, instances, and elements reverse-engineered from code. But there are no hard and fast rules about Package vs Model.
[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.
Snippets (quotes/extracts)
Visit also
Course: Model-Based Systems Engineering with the OMG's Systems Modeling Language® (v1) and the MagicDraw/Cameo (CATIA Magic™) tools for SysML
Visit also (backlinks)
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)