A.5 Humidifier: Scenario block overview BDDs: 96 to 102

Gallery
Tutorial
TRAIL: SysPhS-1.1 Annex A examples in MagicDraw/Cameo SysML vs Modelica (Wolfram SystemsModeler)
Section
Annex A.5: Humidifier (with Units)
Topic level
INTERMEDIATE
UML keywords
Property
Property::defaultValue
Property::redefinedProperty
SysML keywords
Block
SysPhS Keywords
RealSignalInElement
IntegerSignalInElement
PhSConstant
PhSVariable
Keywords
Slide kind
SysML Package Diagram
The diagram shows all Blocks used for carrying the startup "initial values" in this Webel IT trail version of the example problem. This large overview diagram serves here only as a reference, as each specialising «scenario» Block has already also been shown in this trail on the "focus" BDD of the Block it extends.
Click on the image to view it full size
If you think this approach looks like a lot of hard work you are not alone:
SysML: Using redefined Property and Property::defaultValue to create deep hierarchical value configurations of "initial values" configurations for SysPhS simulation is notoriously fiddly and requires experience and patience. Better tool support is needed!
The naming pattern here is more consistent than in the spec. Recall this tip:
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
Please also be mindful of this:
SysPhS-1.1: GOTCHA: The term "initial values" is sometimes just used to refer to the start values for a simulation run in Modelica or Simulink. It does NOT always mean the additional context-specific values mechanism of SysML beyond Property::defaultValue
Up next
A.5 Humidifier: Value property defaults table
Notes
[COMPLICATION, TOOL, WARNING] SysPhS-1.1: GOTCHA: The term "initial values" is sometimes just used to refer to the start values for a simulation run in Modelica or Simulink. It does NOT always mean the additional context-specific values mechanism of SysML beyond Property::defaultValue
[GOTCHA, ISSUE, TOOL, WARNING]{INFORMATIVE} MagicDraw/Cameo vs SysML&SysPhS: GOTCHA: Will NOT export a non-normative System «system» block to Modelica, it only recognises a plain Block «block»!
[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
[DISPLAY, STYLE, TIP] As an alternative to composition Association "trees" consider instead using symbol resize to visually "bracket" composed items (can however be a bit fiddly).
[COMPLICATION, TOOL, WARNING] SysPhS-1.1: GOTCHA: The term "initial values" is sometimes just used to refer to the start values for a simulation run in Modelica or Simulink. It does NOT always mean the additional context-specific values mechanism of SysML beyond Property::defaultValue
[CAPABILITY, FEATURE, TOOL] MagicDraw/Cameo: Supports embedding of one or more Diagrams in another via the Diagram Overview feature. Awesome!
[COMPLICATION, TOOL, WARNING] SysML: Using redefined Property and Property::defaultValue to create deep hierarchical value configurations of "initial values" configurations for SysPhS simulation is notoriously fiddly and requires experience and patience. Better tool support is needed!
Snippets (quotes/extracts)
Visit also
08:02: The SysML ValueType, Unit, and using values
TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]
Visit also (backlinks)
Related slides (includes other tutorials)
Figure 27: Default values and initial value in SysML
Related slides (backlinks, includes other tutorials)
REFERENCE: A.5 Humidifier: Webel: Block overview