SysMLv1.6 Provided/required DirectedFeature contracts for ProxyPorts SHOULD be satisfiable Feature-wise (including as subsets of Features) not necessarily just at the level of entire Blocks (types)! [See also the SysMLv1.7 spec changes.]

Icon class

icon_class

far fa-sticky-note

icon_class_computed

far fa-sticky-note

Note kind

ASSERTION

WISHLIST

Specification keywords

SysML-1.6

UML keywords

SysMLv1.x keywords

This topic is now addressed under the following page updated for SysML1.7 and with a nice Diagram example:

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!

DISCLAIMER: Remarks here and references to the older SysML1.6 spec are to be considered strictly HISTORICAL only!

The SysML spec is clear on Property (StructuralFeature):

SysML-1.6: 'A Binding Connector is a connector which specifies that the properties at both ends of the connector have equal values.'

SysML-1.6: 'If the properties at the ends of a binding connector are typed by a ValueType, the connector specifies that the instances of the properties shall hold equal values, recursively through any nested properties within the connected properties.'

SysML-1.6: 'If the properties at the ends of a binding connector are typed by a Block, the connector specifies that the instances of the properties shall refer to the same block instance.'

The SysML-1.6 spec is not clear on per-BehavioralFeature matching for Operations and Receptions

This constraint is spoiling the show, Webel is lobbying to have it changed:

SysML-1.6: 'BindingConnector::1_compatible_types The two ends of a binding connector shall have either the same type or types that are compatible so that equality of their values can be defined. '

Because it is not consistent with the description of connection compatiblity for ProxyPort:

SysML-1.6: 'Proxy ports can be connected to internal parts or ports on internal parts, identifying features on those parts or ports that are available to external blocks.'

SysML-1.6: 'When a proxy port is connected to a single internal part [or port or internal part], the connector shall be a binding connector, or have the same semantics as a binding connector ... (the value of the proxy port and the connected internal part are the same; links of associations typing the connector are between all objects and themselves, and no others)'

SysML-1.6: 'When a proxy port is connected to multiple internal parts, the connectors have the same semantics as a single binding connector to an aggregate of those parts, supporting all their features, and treating flows and invocations from outside the aggregate... This aggregate is not a separate element of the system, and only groups the internal parts for purposes of binding to the proxy port.'

Relates to

Hybrid SUV example: provided/required DirectedFeatures (Internal Definition Diagram)

UML provided/required Interfaces vs SysML DirectedFeatures on Ports

Conjugation in SysML-1.7 is Type-based: InterfaceBlock, ~InterfaceBlock, and DirectedFeature

Related notes

Related notes (backlinks)

Related snippets (extracts)

[SysML-1.6] A Binding Connector is a connector which specifies that the properties at both ends of the connector have equal values.

[SysML-1.6] If the properties at the ends of a binding connector are typed by a ValueType, the connector specifies that the instances of the properties shall hold equal values, recursively through any nested properties within the connected properties.

[SysML-1.6] If the properties at the ends of a binding connector are typed by a Block, the connector specifies that the instances of the properties shall refer to the same block instance.

[SysML-1.6] BindingConnector::1_compatible_types The two ends of a binding connector shall have either the same type or types that are compatible so that equality of their values can be defined.

[SysML-1.6] Proxy ports can be connected to internal parts or ports on internal parts, identifying features on those parts or ports that are available to external blocks.

[SysML-1.6] When a proxy port is connected to a single internal part [or port or internal part], the connector shall be a binding connector, or have the same semantics as a binding connector ...

[SysML-1.6] (the value of the proxy port and the connected internal part are the same; links of associations typing the connector are between all objects and themselves, and no others)

[SysML-1.6] When a proxy port is connected to multiple internal parts, the connectors have the same semantics as a single binding connector to an aggregate of those parts, supporting all their features, and treating flows and invocations from outside the aggregate...

[SysML-1.6] This aggregate is not a separate element of the system, and only groups the internal parts for purposes of binding to the proxy port.

Visit also

Visit also (backlinks)

Flags