Internal Block Diag.

1. Creation of an Internal Block diagram

1.1. From the wizard

You can use the creation wizard to create a new Internal Block diagram. Select the corresponding Template to initialize the model. By default, the Requirement diagram is selected.

The root element of the SysML model is a Model and it contains a Package which contains a Block. The diagram is then linked with the Block.

1.2. From an existing diagram

The Internal Block diagram is necessarily associated with a Block model object.

create Internal Block diagram from the Outline

To create an Internal Block diagram from the Outline, select the 'Block' node, right click and select 'Add Diagram' then 'Internal Block diagram'

2. Edit an Internal Block Diagram

2.1. Description of the different elements contained in an Internal Block Diagram

2.1.1. Property

TBD

2.1.2. Block Property

TBD

2.1.3. Port

A port specifies the services the owning Block provides (offers) to its environment as well as the services that the owning Block expects (requires) of its environment.

Even if ports are shown in Internal Block Definition, it is required to specify in the Block Definition Diagram the services required and offered by the block that typed the block.

2.1.4. Flow Port

A Flow Port specifies the input and output items that may flow between a Block and its environment. Flow Ports are interaction points through which data, material or energy "can" enter or leave the owning block.

Distinction is made between atomic flow port and non-atomic flow port : atomic flow ports relay a single usage of a block, Value-Type, Data-Type or Signal. A non atomic flow port relays items of several types as specified by a FlowSpecification. The distinction is made according to the flow port's type.

A non atomic flow port can be conjugated. If it is then all directions of the flow properties specified by the flow specification that types the flow port are relayed in the opposite direction (i.e., in flow property is treated as an out flow property by the flow port and vice-versa).

Block, Value-Type, Data-Type and Flow-Specification must be defined in a block definition diagram.

2.1.5. Relationship between elements from an Internal Block Diagram

2.1.5.1. Dependency

A dependency is a relationship that signifies that a single or a set of model elements requires other model elements for their specification or implementation.

2.1.5.2.Connector

TBD

2.1.5.3.Item Flow

An Item Flow describes the flow of items across a connector. It may constrain the item exchange between FlowPorts. For example, a Pump connected to a Tank : the Pump has an out FlowProperty of type Liquid and the Tank has an in FlowProperty of type Liquid. To signify that only Water flow between the Pump and the Tank, we can specify an ItemFlow of type Water on the connector.

The ItemFlow element cannot be created from the Palette, nor from the outline. The element defines in the current editor does not have any signification in the model. It is just a graphical representation.

An ItemFlow is associated with a connector and is defined between two flowports. So, to show the item flow on your connector, open the graphics tab of the connector properties and show the ConnectorItemFlowIconEdgeObject to see the arrow and ConnectorItemFlowNameEdgeObject to see the label associated.

The ItemFlow direction will be automatically computed according to the FlowPorts direction and the connector position. If a red cross appears, it means that nothing can currently flow on your connection, check your flowports configuration.

Item Flow representation

To define the name and the type of the ItemFlow, double-click on the connector. Note that any change made in one of the two flowports will re-initialized those informations.

3. Diagram Example

InternalBlockDiagram