BDD & IBD: Evaporation

Gallery
Tutorial
TRAIL: SysPhS-1.1 Annex A examples in MagicDraw SysML (or Cameo Systems Modeler) vs Modelica
Section
Annex A.5: Humidifier (with Units)
Topic level
INTERMEDIATE
UML keywords
Property::redefinedProperty
ports compartment
Port
SysML keywords
Block
:values compartment
:parts compartment
parts compartment
SysPhS Keywords
RealSignalInElement
Keywords
Slide kind
hybrid diagram
SysML Block Definition Diagram (BDD)
SysML Internal Block Diagram (IBD)
This diagram shows the Block Evaporation and its embedded Internal Block Diagram (IBD):
Click on the image to view it full size

The Evaporation "computation block" tracks the creation of vapor in two parts, a "candidate" amount of vapor generated via eC:EvaporationCalculation and then a "filter" eC2:EvaporationCalculation2 for whether any vapor could have been generated at all (depending on the water temperature).

The output is ultimately Vapor_mL_per_h, which quantity measure is eventually passed out via the VaporGenerationPlant out of the Humidifier to the HumidifiedRoom "calculation block".

Recall that:

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.
Dr Darren says: 'A little bit OCD is not a bad thing in this business!'
On a very minor modelling point:
Webel Best Practice: Block naming: If you find you've got similar blocks named 'Thing' and 'Thing2' then 'Thing' is probably better renamed 'Thing1'
Up next
BDD & PD: EvaporationCalculation
Notes
[ASSERTION] Webel vs SysPhS-1.1: Annex A.5: Humidifier: It is assumed that "energy" is a rate (equivalent to a power).
[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} UML/SysML: Navigation: Try to 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"!
[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, STYLE, TIP]{STRONG} Consider creating a "focus" Block Definition Diagram (or Class Diagram) for each main Block (or Class) with expanded feature details and relationships to at least nearest neighbours
[NAMING, TIP]{RECOMMENDED} Suffix the "focus" BDD for a Block with .bdd so that it won't clash with a corresponding IBD on diagram export.
[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)
[CONVENTION, NAMING]{STRONG} Webel: If you must name your Ports or Pins, name them simply 'i', 'o', or 'io' to indicate direction UNLESS you have to indicate a special role like 'iRole', 'oAuxiliary'. DO NOT use Port names like 'input', 'output', etc.
[CONVENTION, MODELLING, NAMING] Block naming: If you find you've got similar blocks named 'Thing' and 'Thing2' then 'Thing' is probably better renamed 'Thing1'
Snippets (quotes/extracts)
  [SysPhS-1.1] The internal structure of VaporGenerationPlant uses blocks Heating and Evaporation, which have internal structures depicted in Figure 70 and Figure 71, respectively.
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
Figure 27: Default values and initial value in SysML
Related slides (backlinks, includes other tutorials)