Tags and keywords
The slide shows a trail version of Internal Block Diagram (IBD) Figure 59: Internal structure of hydraulics system:
SysPhS-1.1: 'Figure 59 shows the internal structure of a ConnectedTanks block. Part properties, typed by blocks ... represent components in this system. They are connected to each other through ports, which represent openings in the tanks and pipe ... Item flows on connectors indicate fluid passes through the ports and between the parts. The diagram connects a tank to each end of a pipe.'
This trail version of the diagram employs this display option:
The context-specific values for fluidLevel
and tankSurfaceArea
are shown in the initialValues compartment on fluidReservoir1:Tank
and fluidReservoir2:Tank
.
Notice how the "shared"
Property::defaultValue
for each of gravity
and fluidDensity
(introduced earlier to keep things nice and DRY) are also visible in the initialValues compartment!
Unless an over-riding context-specific values is defined for a value property, any Property::defaultValue
defined on it "shines through" (sometimes known as the Translucency Pattern for those of you old enough to remember Perl).
BTW: There is, in any case, more than one way to encapsulate variation between initial conditions for usages, as noted in the spec: