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

Glossary Page



A source object realizes the destination object. Realize is used to express traceability and completeness in the model a business process or requirement is realized by one or more Use Cases which are in turn realized by some Classes which in turn are realized by a Component, and so on.

receive [a message]

The handling of a stimulus passed from a sender instance.

See also: sender, receiver


An element used to define the acceptance or receipt of a request. Movement on to the next action occurs until it has received what is defined.

receiver [object]

The object handling a stimulus passed from a sender object.

Contrast: sender


A declaration that a classifier is prepared to react to the receipt of a signal.


A type of message used in Sequence diagrams to indicate a recursive function.


  1. A denotation of a model element.
  2. A named slot within a classifier that facilitates navigation to other classifiers.

Synonym: pointer


UML 2.x supports both Expansion Regions and Interruptible Activity Regions. An Expansion Region defines the bounds of a region consisting of one or more sets of input collections, where an input collection is a set of elements of the same type. An Interruptible Activity Region contains Activity nodes - when a token leaves an interruptible region, this terminates all of the region's tokens and behaviors.


A relationship that represents a fuller specification of something that has already been specified at a certain level of detail. For example, a design Class is a refinement of an analysis Class.


A semantic connection among model elements. Examples of relationships include Associations and Generalizations.


A facility for storing object models, interfaces and implementations.


A connector that indicates a Collaboration is used in a classifier. The connector is drawn from the Collaboration to its owning classifier.


A required feature, property or behavior of a system (external requirement).


A contract or obligation of a classifier (internal requirement).


The use of a pre-existing artifact.

reverse engineering

The process of importing source code into the model as standard UML model objects (such as Classes, attributes and operations).

rich text format

A standard mark-up language for creating word processor documents, frequently associated with Microsoft Word.

robustness diagram

Enterprise Architect supports business process modeling extensions from the UML business process model profile. Robustness diagrams are used in ICONIX - you can read more about this at ICONIX Jump Start Training.


  1. The named detail and rules associated with one end of an association. Can indicate name, constraints, multiplicity and collection details.
  2. The named specific behavior of an entity participating in a particular context. A role can be static (such as an Association end) or dynamic (such as a Collaboration role).

role binding

The mapping between a Collaboration Occurrence's internal roles and the respective parts required to implement a specific situation. The associated parts can have properties defined to enable the binding to occur, and the collaboration to take place.

run time

The period of time during which a computer program executes.

See also: analysis time, compile time, design time

Contrast: modeling time