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

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
MODELLING
PATTERN
TIP
Policy level
RECOMMENDED
Specification keywords
SysML-1.6
SysML-1.7
UML-2.5.1
UML keywords
Property::redefinedProperty
Property::defaultValue
Stereotype
«keyword»
user defined Stereotype
custom Stereotype
Keywords
You can also use a trailing suffix like _S1 in the name of each «scenario» block within a given scenario. See for example:
A.5 Humidifier: Scenario block overview BDDs: 96 to 102
Relates to
REFERENCE: A.5 Humidifier: Webel: Block overview
BDD & IBD: HumidifierSystem
BDD & IBD: HumidifiedRoom
BDD & PD: VolumeConversion
BDD & PD: VolumeConversion
BDD & PD: SaturationVaporPressure
BDD & IBD: RelativeHumidity
BDD & PD: RelativeHumidityCalculation
BDD & PD: HumidityBalance
BDD & PD: VaporPressureCalculation
BDD & PD: PercentageConversion
BDD & IBD: Humidifier
BDD & PD: WaterTank
BDD & IBD: VaporGenerationPlant
BDD & PD: Radiation
BDD & PD: VaporGenerationPlantCalculation
BDD & IBD: Heating
BDD & PD: TemperatureIncrease
BDD & PD: HeatingCalculation
BDD & IBD: Evaporation
BDD & PD: EvaporationCalculation
BDD & PD: EvaporationCalculation2
A.5 Humidifier: Scenario block overview BDDs: 96 to 102
Related notes
[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!
Related notes (backlinks)
Related snippets (extracts)
Visit also
Annex A.5: Humidifier (with Units)
Visit also (backlinks)