Webel Radio Net: SysML Package Diagram as index

Gallery
Tutorial
[TRAIL] SysMLv1: The Webel Radio Net port-based messaging example model in Cameo Systems Modeler and Cameo Simulation Toolkit
Section
Webel Radio Net: Model overview, exchange items, and Ports
Topic level
BASIC
Keywords
Slide kind
SysML Package Diagram
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.
The index Package Diagram for the Webel Radio net serves primarily as a quick navigation dashboard. It is referenced throughout the project, especially from Packages or Model packages one level down:
Webel: UML/SysML: Navigation: ALWAYS offer a way out of a diagram (usually up a hierarchy, but possibly across) using a navigable symbol (linked to a diagram) and/or a diagram symbol. Avoid "cul-de-sacs"! [But beware of shared package cross-dependencies]

Of primary interest are the RadioNetContext, RadioNet system, and RadioStation block, and the simulation block Sim_RadioNet, from which a simulation in Magic Model Analyst® (Cameo Simulation Toolkit®) can be launched.

The specifics of the Element ownership organisation is not critical. The Package organisation shown is not intended as a formal "template" for your own projects, but some basic principles can be employed:

  • Identify ValueTypes early on. They may or may not live in a top-level 'value' Package, they can be local to another Package or even owned by a Block.
  • Identify exchange items (such as Signals) early on!
Webel: SysML: Heard of "follow the money"? In MBSE we "follow the flows"! Identify requests, data packets, messages, signals early on and use ItemFlow as often as you can wherever you can! Adopt a signal processing mindset throughout (systems thinking).
Note that this Radio Net sample does not (yet) include formal Systems Engineering (SE) functional breakdown or logical vs design/implementation components treatment. It also does not (yet) include Requirement Analysis, and only has an absolutely minimal representation of the context including a single SysML-style block-based custom «actor» NetManager (and a custom «person» NetOperator associated with a RadioStation).

Up next
Webel Radio Net: Content Diagram as index of table and matrix diagrams
Notes
[MODELLING, NAVIGATION, PATTERN, TIP, TOOL]{STRONG} Webel: UML/SysML: Navigation: ALWAYS offer a way out of a diagram (usually up a hierarchy, but possibly across) using a navigable symbol (linked to a diagram) and/or a diagram symbol. Avoid "cul-de-sacs"! [But beware of shared package cross-dependencies]
[CONVENTION, MODELLING, TIP]{RECOMMENDED} Webel: MBSE: SysMLv1: Prefer a custom «actor» extension of a Block (such as the non-normative External) over UML-style Actor for use as parts in IBDs and on allocation swimlanes. You can also have a Trace from a block-based «actor» to a UML-style Actor.
[ASSERTION, MODELLING, PATTERN]{STRONG} Webel: SysML: Heard of "follow the money"? In MBSE we "follow the flows"! Identify requests, data packets, messages, signals early on and use ItemFlow as often as you can wherever you can! Adopt a signal processing mindset throughout (systems thinking).
[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.
Snippets (quotes/extracts)
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)