SysML does NOT distinguish between 'assembly' and 'delegation' Connector kinds (because of its more complex support for nested ports). These Connector type classifications are only relevant in UML.
Block::isEncapsulated : Boolean [0..1] ... If false, or if a value is not present, then connections can be established to elements of its internal structure via deep-nested connector ends. Source OMG Systems Modeling Language (SysML) 1.6
Block::isEncapsulated : Boolean [0..1] If true, then the block is treated as a black box; a part typed by this black box can only be connected via its ports or directly to its outer boundary. Source OMG Systems Modeling Language (SysML) 1.6
Connectors may be drawn that cross the boundaries of nested properties to connect to properties within them. The connector is owned by the most immediate block that owns both ends of the connector. Source OMG Systems Modeling Language (SysML) 1.6
Boundary Ports and kinds of Connectors Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 09:02: Ports - The basics Slide kind SysML Internal Block Diagram (IBD)
SysML Blocks also extend the capabilities of UML classes and connectors with reusable forms of constraints, multi-level nesting of connector ends, participant properties for composite association classes, and connector properties. Source OMG Systems Modeling Language (SysML) 1.6
The rest of the connectors linked to a port are external. Source OMG Systems Modeling Language (SysML) 1.6
Internal connectors to ports are the ones inside the ports owner (specifically, they are the ones that do not have a UML partwithPort on the connector end linked to the port, assuming NestedConnectorEnd is not applied to that end, or if NestedConnectorEnd Source OMG Systems Modeling Language (SysML) 1.6
Figure 8-16 shows the same decomposition in an internal block diagram that includes bound references. The binding connectors have nested connector ends, because they link inside the parts of the vehicle. Source OMG Systems Modeling Language (SysML) 1.6
Figure 8-6: Abstract syntax extensions for SysML connector ends Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6 specification diagrams: 08 Blocks Slide kind UML Profile Diagram
Figure D.24 - Defining Fuel Flow Constraints (Parametric Diagram) [ANNOTATED] Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6: HSUV sample Slide kind SysML Parametric Diagram
The context for the usages of constraint blocks shall also be specified in a parametric diagram to maintain the proper namespace for the nested properties. Source OMG Systems Modeling Language (SysML) 1.6
This allows a value property (such as an engine displacement) that may be deeply nested within a containing hierarchy (such as vehicle, power system, engine) to be referenced at the outer containing level (such as vehicle-level equations). Source OMG Systems Modeling Language (SysML) 1.6
A pathname dot notation can be used to refer to nested properties within a block hierarchy. Source OMG Systems Modeling Language (SysML) 1.6
As with any connector owned by a SysML Block, the ends of a binding connector may be nested within a multi-level path of properties accessible from the owning block. The NestedConnectorEnd stereotype is used to represent such nested ends just as for ... Source OMG Systems Modeling Language (SysML) 1.6
Figure D.24 - Defining Fuel Flow Constraints (Parametric Diagram) Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6: HSUV sample Slide kind SysML Parametric Diagram
