Overview of flowing quantities and Port types with flows

This Package Diagram shows an overview of the (most of the) types of stuff that flow in this simple air conditioner model, and the Types of Ports that have flows:

Click on the image to view it full size

Note that each of Air, Refrigerant, VariableFrequencyPower and SineWavePower have been modelled as Blocks, not just ValueTypes, so they can themselves carry value properties (some of which have units).

The block Refrigerant can have a RefrigerantState, and there are two fixed specialisations RefrigerantVapour and RefrigerantLiquid.

This Port naming convention has been used:

Webel Best Practice: Webel: For SysML Blocks and InterfaceBlocks used to type Ports with physical flows use 'F_UpperCamelCase' [may be combined with acronymn conventions]. The trailing part (after the underscore '_') may indicate the type that flows.

A S_ prefix convention indicates a flow of a signal, as opposed to a flow of a physical quantity, recalling that a Signal was chosen to model the digital TemperatureReading.

And there is also a special convention (used mostly just for this trail because it mixes flow interaction types), the prefix FF_ indicates here the type of a Port that has both in and out flows and is modelled using the SysML Extension for Physical Interaction and Signal Flow Simulation (SysPhS) approach, such as FF_FluidFlowElement and FF_HeatFlowElement, which we'll learn about next .

Up next

Overview of two SysPhS-style physical interaction Port types

Notes

[TIP, WORKAROUND]{INFORMATIVE} [HISTORICAL] HOWTO easily "hack" the SysML-1.6 ~InterfaceBlock conjugation and «~interfaceBlock» keywords in MagicDraw/Cameo. [NOW SUPPORTED 2024x Golden]

[POLICY] Since SysML-1.6 use of direct UML conjugation of Ports is NOT supported; If you are using InterfaceBlocks use instead a conjugated ~InterfaceBlock type!

[NAMING, POLICY]{STRONG} Webel: For SysML Blocks and InterfaceBlocks used to type Ports with physical flows use 'F_UpperCamelCase' [may be combined with acronymn conventions]. The trailing part (after the underscore '_') may indicate the type that flows.

[MODELLING, OPTION, TIP]{INFORMATIVE} SysML: Flows: If you use a Signal to type the itemProperty of an ItemFlow on a Connector, care must be take in how you create the Property or you might get an unwanted signal Reception on the owning context Block.

[ASSERTION, MODELLING, TIP]{STRICT} SysML+SysPhS: Flows: If you intend to use a Classifier to type the itemProperty of an ItemFlow on a Connector for a physical interaction you MUST use a Block (not a ValueType or Signal) so your can extend ConservedQuantityKind.

Snippets (quotes/extracts)

[SysML-1.6] The ~InterfaceBlock stereotype (shall be pronounced: "conjugated interface block") is a specialization of InterfaceBlock that has the same features as its original InterfaceBlock except that its DirectedFeatures and FlowProperties are reversed (conjugated

[SysML-1.6] ~InterfaceBlock::original : InterfaceBlock [1] The InterfaceBlock that this is a conjugation of.

Visit also