09:03: Port conjugation in SysMLv1 is now Type-based

Icon class
icon_class
far fa-bookmark
icon_class_computed
far fa-bookmark
Tutorial
TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo
UML keywords
Port
Port::isConjugated
SysML keywords
ProxyPort
FullPort
InterfaceBlock
~InterfaceBlock
We are offering a 30% discount off all SysML/MBSE course bookings secured by 28th February 2025! Contact us now to apply!
This section of the trail shows you how the SysML-1.6/1.7 conjugation approach works, and how to handle it in the latest versions of the MagicDraw/Cameo tool:
UML Port conjugation is dead (since SysML-1.6); Long live conjugation of the Port's type!
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!
The mechanism for conjugated Ports has been changed in SysML 1.6, it now conjugates the Type! If you are using an InterfaceBlock to type a Port you can conjugate that 'original' on another Port by typing it with an ~InterfaceBlock.
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 ... for example, in flow properties are conjugated as out flow properties and provided features are conjugated as required features. '
SysML-1.6: '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.'
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!
Start section here
Conjugation in SysML-1.7 is Type-based: InterfaceBlock, ~InterfaceBlock, and DirectedFeature

Slides in this section

If you want to navigate the entire section including the additional explanatory text click on the title link of the first slide to view the full slide page, then use the next links to move through the slide pages. If you just want to view the slide images only in sequence, click on any slide to view it larger in a viewer, then click again to move through each slide in this tutorial trail section.
Conjugation in SysML-1.7 is Type-based: InterfaceBlock, ~InterfaceBlock, and DirectedFeature
Next trail section
09:04: Ports and contracts
SysMLv1: Summary of some important changes between SysMLv1.2 and SysMLv1.7 and some DEPRECATED modelling elements [PARTIAL LIST ONLY]
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!