Package Diagram overview of a simple domestic air conditioner with an inverter

Gallery
Tutorial
TRAIL: SysML: Simple model of an air conditioner with a refrigerant cycle and StateMachine driven by Activities in MagicDraw/Cameo
Section
UML keywords
StateMachine
Activity
Model
Signal
Operation
BehavioredClassifier::classifierBehavior
BehavioredClassifier::ownedBehavior
operations compartment
Association
SysML keywords
Block
parts compartment
«system»
«system context»
Keywords
Slide kind
SysML Package Diagram
Please note that some of the naming used in this trail is a bit more colloquial than typical Webel Best Practice.
This Package Diagram shows the «system» block SimpleDomesticInverterAirCon and some supporting elements and sub-packages, as well as an example «system context» block:
Click on the image to view it full size

This diagram is in fact a bit of a mix between a typical Package Diagram and a Block Definition Diagram (BDD), just for the sake of this trail to give a detailed overview.

It includes use of some Association notation, which notation is not always easily understood by those new to SysML:

SysMLv1: Associative BDDs are best used as staging diagrams for you the modeller (and SysML-fluent readers). IBDs usually make better presentations diagrams for a wider audience of general engineers and other stakeholders.

The SimpleDomesticInverterAirCon «system» block has internal parts - which we'll inspect in more detail next in a dedicated "focus" Block Definition Diagram (BDD) - and some properties typed by Air, VariableFrequencyPower, and variations on Refrigerant, which are used for ItemFlow packets that flow and transform (as we'll see later in an Internal Block Diagram (IBD) for the «system context» block).

SysML-1.6/1.7: You can introduce a custom (user-defined) stereotype keyword «item» to indicate Properties that are to be used as "packets" for ItemFlows on Connectors. (SysMLv2 will have a formal way of treating such items/packets.)

It also has a StateMachine as classifier Behavior and an owned Activity. There are some packaged Signals for state Transitions and some packaged sub-Activities.

Up next
BDD: SimpleDomesticInverterAirCon
Notes
[MODELLING, STYLE, TIP]{RECOMMENDED} SysMLv1: Associative BDDs are best used as staging diagrams for you the modeller (and SysML-fluent readers). IBDs usually make better presentations diagrams for a wider audience of general engineers and other stakeholders.
[MODELLING, TIP]{SUGGESTED} SysML-1.6/1.7: You can introduce a custom (user-defined) stereotype keyword «item» to indicate Properties that are to be used as "packets" for ItemFlows on Connectors. (SysMLv2 will have a formal way of treating such items/packets.)
[MODELLING, OPTION, TIP]{INFORMATIVE} SysML: Whether you use a Block, ValueType, or Signal to represent something that flows (and can be applied to an ItemFlow) depends on what you want to achieve. If you want to indicate something structured with value properties with Units use a Block.
Snippets (quotes/extracts)
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)