Webel: SysML-1.7/SysMLv2: WISHLIST: Constraint: A BindingConnector used for pure proxying MUST NOT be typed by an AssociationBlock by definition, because the associated information can be mis-appropriated to undermine the proxy equality!

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
Policy level
Specification keywords
SysMLv1.x keywords
Keywords
Click on the image to view it full size
The attached image illustrates the potential issue. An AssociationBlock used to type BindingConnector can be used to undermine a pure proxy; in this case, some L and R stereo channels have been swapped.

According to this Webel Best Practice policy, the use of an AssociationBlock to type a Connector (any Connector) is a declaration that you are NOT simply proxying.

Pro: Excluding AssociationBlock as a possible type of a BindingConnector used for ProxyPort delegation also helps you know when it is NOT proxying .

AssocationBlocks are cool! Just please don't use them on a true proxy connector.

The diagrams also show another potential issue that can arise when using an AssociationBlock this way with nested ports; the tool will report that the direction is invalid on the inner Connectors (thanks to John Brush of 7Sigma for identifying this concern and for discussions).

To see a better way of modelling a jack or socket that avoids these issues please visit: Webel: SysML: Electronics: DO NOT represent a jack/socket as a dumb proxy. Imagine it can introduce some signal noise or other effect (such as buzz) to test it is a physical model.

Relates to
Related notes
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)