BDD: SimpleDomesticInverterAirCon

Here more detail is shown about the internal component parts of the SimpleDomesticInverterAirCon «system» block. They are shown here as Block symbols on the ends of non-navigable composition Associations, and it this case likewise with their parts listing compartments showing (just as a modelling choice here).

We again see properties typed by Air, VariableFrequencyPower, and variations on Refrigerant, which are to be 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.)

Notice how we get some reuse of the 'i' and 'o' Ports of Fan by having ExternalBlower and ChillerFan extend it.

Up next

BDD: InverterSubsystem

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.

[CONVENTION, DISPLAY, MODELLING, STYLE, TIP]{STRONG} Webel: SysMLv1: Highly recommend creating a "focus" Block Definition Diagram (BDD) for each main Block with expanded feature details and relationships to at least nearest neighbours

[DISPLAY, STYLE, TIP, TOOL]{SUGGESTED} Style: use line width 2 or 3 on the border of the "focus" element in "focus" diagrams (such as the main Block or Class of a dedicated Block Definition Diagram or Class Diagram)

[NAMING, TIP]{OPTION} Optionally suffix the "focus" BDD for a Block with '.bdd' so that it won't clash with a corresponding IBD on diagram export. This is not a SysMLv1 concern, it is purely a workflow concern. It has the slight disadvantage that BDD may "indicated" twice.

Snippets (quotes/extracts)

Visit also

Visit also (backlinks)