BDD & PD: VolumeConversion | Webel IT Australia

It may look like a lot of work for simply multiplying one number by a gain, but it goes quickly once you've got the hang of it. We'll be roughly following this diagramming pattern also for the more complicated cases to come.

The block VolumeConversion seems to be specifically intended for conversion from VaporRate_mL_per_h to VaporRate_mL_per_s, using a factor 1/3600, which is carried by the redefining gain value property of the «scenario» block VolumeConversion_S1.

Note in this trail version the use of an explicit unitless ConversionFactor type for gain to help keep track of the unit dimensions systematically.

In this trail version the usage (part property) of the VolumeConversion block is named vC. In the spec it is named mLpH2mLpS, which is not an ideal name for a part property. However, if the block VolumeConversion had been more generally named Conversion_per_h_to_per_s, then mLpH2mLpS might make some sense as a more specific application of it.

Up next

BDD & PD: SaturationVaporPressure

Notes

[ASSERTION]{STRONG} Webel vs SysPhS-1.1: Annex A.5: Humidifier: It is assumed that "vapor" is a volume rate corresponding to the rate of consumption OF HEATED LIQUID WATER (from a tank) used to create the vapor.

[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]

[MODELLING, PATTERN, TIP]{RECOMMENDED} SysML: When using Property::defaultValue and Property::redefinedValue to carry a "shadow hierarchy" of redefinitions across an entire system hierarchy, considering using a user-defined keyword such as «configuration» or «scenario» on each redefining Block

[CAPABILITY, FEATURE, TOOL] MagicDraw/Cameo: Supports embedding of one or more Diagrams in another via the Diagram Overview feature. Awesome!

[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

[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.

[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)