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

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
[HISTORICAL] MagicDraw/Cameo 19SP3: Does NOT yet support ~InterfaceBlock [NOW SUPPORTED in 2024x Golden]
In general, the SysML DirectedFeature approach is more powerful and the notation is cleaner than UML provided/required Interfaces. Prefer SysML DirectedFeatures unless you have a really good reason to use Interfaces!
Avoid mixing flow properties on the Type of a Port with directed features (operations and values); One distinguishes between "ports with flows" and "contract ports".
Until tool support for ~InterfaceBlock comes you have to make a decision: (1) Bake your own «~InterfaceBlock» then deal with clashes when tool support comes; (2) stick with the DEPRECATED UML conjugation (not nested-port friendly) and await migration.
MagicDraw/Cameo 19SP3 still supports the DEPRECATED UML Port conjugation (but it is recommended here that you DO NOT use it, even though there might be future migration for such directly conjugated Ports).
MagicDraw/Cameo v19SP3 vs SysML&SysPhS: GOTCHA: Will NOT correctly export a SysML-1.6 «~interfaceBlock» to Modelica (but does cope with a tilde ~ prefix in the name of a plain InterfaceBlock)
Overview of flowing quantities and Port types with flows
IBD: Context for SimpleDomesticInverterAirCon - detailed
Webel: SysML1.7: Port contract matching is Feature-based, not Type-based. There's nothing particularly magical or special about use of an ~InterfaceBlock on a "conjugating" SysML Port, it's just a convenient way of managing one-to-one Feature matching!
Conjugation in SysML-1.7 is Type-based: InterfaceBlock, ~InterfaceBlock, and DirectedFeature
Source
OMG Systems Modeling Language (SysML) 1.6
Copyright information
About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes
Snippet kind
INFO
SysML keywords
InterfaceBlock
~InterfaceBlock
conjugation
~InterfaceBlock::original
DirectedFeature
FlowProperty
FlowProperty::direction
FlowDirectionKind
DirectedFeature::featureDirection
FeatureDirectionKind
Full quote
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)
Next snippet
InterfaceBlock ... for example, in flow properties are conjugated as out flow properties and provided features are conjugated as required features.
Related snippets
Related snippets (backlinks)
InterfaceBlock ... for example, in flow properties are conjugated as out flow properties and provided features are conjugated as required features.
Conjugation is specified by a constraint giving the features of ~InterfaceBlocks according to those of their original InterfaceBlocks ... It is expected that tools conforming to this specification automatically create features of ~InterfaceBlocks.
~InterfaceBlock::original : InterfaceBlock [1] The InterfaceBlock that this is a conjugation of.
[SysML1.6: PREFER SysML1.7] A DirectedFeature indicates whether the feature is supported by the owning block (provided), or is to be supported by other blocks for the owning block to use (required), or both ...
(the owning block for features on types of proxy ports is the type of the block usage the proxy port is standing in for, which might be an internal part).
A DirectedFeature indicates whether the feature is supported by the owning block (provided) for other connected blocks to use, or is to be supported by a connected block for the owning block to use (required), or both (providedRequired).
A providedRequired feature specifies a symmetric dependency between two connected blocks whereby a block’s internal use of such a feature is delegated to the connected block with the corresponding feature and conversely that block’s internal use of ...
Features that are not denoted as a DirectedFeature are implicitly provided features. As such they can be matched against a corresponding required feature.
Visit also
Visit also (backlinks)