Boundary Ports and kinds of Connectors

We start our introduction to Ports with an Internal Block Diagram (IBD) with a single Port symbol on the boundary of the diagram frame, which frame represents the boundary of a Block between itself and its environment:
Click on the image to view it full size

At this stage, we are only looking at types of connections made directly to from a boundary Port to part properties of the owning Block (we'll see later that owned properties of a Block may also have Ports if they are typed by a Block that has Ports).

A Connector from a boundary Port to an inner Property - such as from p:DelegatingPort to b1:InnerBlock1 - is of kind delegation,

From the software-centric UML world: In SysML, the sense of delegation is far broader, and can involve data, information, material, energy (or anything else that can flow) or anything that can be provided or required.

A Connector from an inner Property to another inner Property - such as from b1:InnerBlock1 to b2:InnerBlock2 - is of kind assembly.

One of the nicest extensions of SysML over UML is the ability to connect across boundaries to inner Properties of Properties, such as from b1:InnerBlock1 to nb:NestedBlock across the boundary of b3:InnerBlock3:

SysML has special a requirement for being allowed to connect across the boundary of a Property typed by a Block, the Block must not have 'isEncapsulated' true: Finally, note that the boundary Port has isBehavior false, which just means it does not delegate to the owning block itself:
SysML has additional special kind of connector called the BindingConnector we'll see later
Up next
Snippets (quotes/extracts)
Visit also
Visit also (backlinks)
Related slides (other tutorials)
Related slides (other tutorials, backlinks)