~R~

Realize

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.

Receive

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.

Reception

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

Recursion

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

Reference

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

Region

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

Refinement

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.

Relationship

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

Repository

A facility for storing object models, interfaces and implementations.

Represents

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

Requirement

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

Responsibility

An internal parameter that applies rules to the element - an internal requirement, scenario or constraint.

Reuse

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.

Role

1. The named detail and rules associated with one end of an association; a role 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 Use'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.