Depending on their NodeClass Nodes are represented by different graphical forms as defined in Table C.1.

Table C.1 – Notation of Nodes depending on the NodeClass

NodeClass

Graphical Representation

Comment

Object

image057.png

Rectangle including text representing the string-part of the DisplayName of the Object. The font shall not be set to italic.

ObjectType

image058.png

Shadowed rectangle including text representing the string-part of the DisplayName of the ObjectType. The font shall be set in italic.

Variable

image059.png

Rectangle with rounded corners including text representing the string-part of the DisplayName of the Variable. The font shall not be set in italic.

VariableType

image060.png

Shadowed rectangle with rounded corners including text representing the string-part of the DisplayName of the VariableType. The font shall be set in italic.

DataType

image061.png

Shadowed hexagon including text representing the string-part of the DisplayName of the DataType. The font shall be set in italic.

ReferenceType

image062.png

Shadowed six-sided polygon including text representing the string-part of the DisplayName of the ReferenceType. The font shall be set in italic.

Method

image063.png

Oval including text representing the string-part of the DisplayName of the Method. The font shall not be set to italic.

View

image064.png

Trapezium including text representing the string-part of the DisplayName of the View. The font shall not be set to italic.

References are represented as lines between Nodes as exemplified in Figure C.1. Those lines can vary in their form. They do not have to connect the Nodes with a straight line; they can have angles, arches, etc.

image065.png

Figure C.1 – Example of a Reference connecting two Nodes

Table C.2 defines how symmetric and asymmetric References are represented in general, and also defines shortcuts for some ReferenceTypes. Although it is recommended to use those shortcuts, it is not required. Thus, instead of using the shortcut, the generic solution can also be used.

Table C.2 – Simple Notation of Nodes depending on the NodeClass

ReferenceType

Graphical Representation

Comment

Any symmetric ReferenceType

image066.png

Symmetric ReferenceTypes are represented as lines between Nodes with closed and filled arrows on both sides pointing to the connected Nodes. Near the line has to be a text containing the string-part of the BrowseName of the ReferenceType.

Any asymmetric ReferenceType

image067.png

Asymmetric ReferenceTypes are represented as lines between Nodes with a closed and filled arrow on the side pointing to the TargetNode. Near the line has to be a text containing the string-part of the BrowseName of the ReferenceType.

Any hierarchical ReferenceType

image068.png

Asymmetric ReferenceTypes that are subtypes of HierarchicalReferences should be exposed the same way as asymmetric ReferenceTypes except that an open arrow is used.

HasComponent

image069.png

The notation provides a shortcut for HasComponent References shown on the left. The single hashed line has to be near the TargetNode.

HasProperty

image070.png

The notation provides a shortcut for HasProperty References shown on the left. The double hashed lines have to be near the TargetNode.

HasTypeDefinition

image071.png

The notation provides a shortcut for HasTypeDefinition References shown on the left. The double closed and filled arrows have to point to the TargetNode.

HasSubtype

image072.png

The notation provides a shortcut for HasSubtype References shown on the left. The double closed arrows have to point to the SourceNode.

HasEventSource

image073.png

The notation provides a shortcut for HasEventSource References shown on the left. The closed arrow has to point to the TargetNode.

HasInterface

image074.png

The notation provides a shortcut for the HasInterface References shown on the left. The closed arrow shall point to the TargetNode.