Book a Demo

Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Prev Next

Common Pages

The 'Common' pages of the Diagram Toolbox provide the elements and relationships that can be used on any diagram. They are displayed at the bottom of every other set of pages in the Toolbox.


Common Elements



Note element

A Note element is a textual annotation that can be attached to a set of elements of any other type.

Constraint element

A Constraint is a form of Note, identifying a constraint on other elements.

A Text element is a textual annotation that is similar to a Note, however has no border or background color.

A Legend element provides a key to the colors and line thicknesses you have used to distinguish between element and/or connector groupings on the diagram.

On a diagram, it is possible to display a customized text box called the Diagram Properties Note, which automatically shows the diagram properties.

A Hyperlink element is a special kind of Text element that, when double-clicked, opens the configured target object such as a document, web page or diagram.

Artifact element

An Artifact is any physical piece of information used or produced by a system. This icon generates a generalized Artifact that you can define as one of a number of types. There are also Toolbox pages providing specialized types of Artifact, for specific purposes. See the Artifact Toolbox Pages Help topic.

Information Item element

An Information Item element represents an abstraction of data, which data can be conveyed between two objects.

Boundary element

A System Boundary element is a non-UML element used to define conceptual boundaries.

Image element

An Image is a System Boundary element that automatically has an Alternate Image defined.

An Image Asset is a specialized Artifact element for holding an image that can be called into a number of diagrams to show a captured document or screen, a graphic, or an object.

Common Connectors



Dependency connector

Dependency relationships are used to model a wide range of dependent relationships between model elements.

Realization connector

A source object implements or Realizes its destination object.

Trace connector

The Trace relationship is a specialization of an Abstraction, connecting model elements or sets of elements that represent the same concept across models.

Information Flow connector

An Information Flow represents the flow of Information Items (either Information Item elements or classifiers) between two elements in any diagram.

Abstraction connector

An Abstraction is a relationship between two elements that represent the same concept, either at different levels of abstraction or from different viewpoints.


A Substitution is a relationship between two Classifiers, signifying that the substituting Classifier complies with the contract specified by the contract Classifier.

Usage connector

A Usage is a Class diagram relationship in which one element requires another element for its full implementation or operation.

A Derive relationship connects two elements when the value of one is derived from the value of the other. This type of relationship is appropriate to link Requirements on different levels of abstraction; for example, a solution Requirement derived from a business or a stakeholder Requirement.

A Refine relationship connects a Requirement and another model element that adds refinement or additional information that helps clarify the Requirement so that its meaning is more apparent.

A Responsibility connector is a UML standard stereotype that defines a contract or an obligation of an element in its relationship to other elements.

Note link

A Notelink connector connects a Note to one or more other elements of any other type.

Learn more