Parametric diagrams with BindingConnectors for concrete implementation blocks A1 and A2

The following Webel Best Practice tip can really help organise the wiring up of SysML Parametric diagrams, and can give indication in BDDs and elsewhere about how the value properties are intended to be used:

Webel Best Practice: SysML Parametrics: You can use custom stereotypes keywords «i» and «o» to indicate value properties that are intended to be used as (i)nputs and (o)utputs when bound to constraint parameters for SysML Parametrics

If you have done any SysML Parametrics, the diagrams here should all be self-explanatory, however there is one subtlety:

One has to be very careful not to inherit unwanted Connectors without redefining them! It can cause the simulation engine to fail in hard to discover ways!

So the "contract Connector" o-o has been redefined by o-o1 and o-o2 in A1 and A2 respectively.

Up next

Executable instance tables for A1 and A2 (concrete implementations of I_A)

Notes

[MODELLING, NAMING, TIP]{RECOMMENDED} SysML Parametrics: You can use custom stereotypes keywords «i» and «o» to indicate value properties that are intended to be used as (i)nputs and (o)utputs when bound to constraint parameters for SysML Parametrics

[CAPABILITY, FEATURE, STYLE, TIP]{RECOMMENDED} TIP: UML/SysML: MagicDraw/Cameo: Consider showing the constraint parameter name and type label inside the small rectangular parameter symbol on SysML Parametric Diagrams. Dr Darren swears by it!

[ASSERTION] The SysML InterfaceBlock can be used for general contracts (it is NOT just for use as the Type of a ProxyPort)!

Snippets (quotes/extracts)

[SysML-1.6] InterfaceBlock::2_no_part Interface blocks composite properties are either ports, value properties or flow properties.