A raise exception action is an action that causes a particular exception to occur.
reactive object
A reactive object is an object whose behavior is best characterized by its responses to events dispatched outside its context.read attribute action
A read attribute action is an action that reads the values of one or more attributes and puts them on an output pin.
read extent action
A read extent action is an action that reads the set of all instances of a given classifier that exist at a particular point during system execution.
read is classified object action
A read is classified object action is an action that determines whether a given object is connected with a particular classifier.
read link action
A read link action is a link action that navigates across a link to retrieve the objects on one end.
read link object action
A read link object action is an action that reads the object at a given end of a particular link object.
read link qualifier object action
A read link qualifier object action is an action that retrieves a given qualifier value from a particular link object.
read self action
A read self action is an action that retrieves the object to which the enclosing activity belongs.
read structural feature action
A read structural feature action is a structural feature action that retrieves the values of a given structural feature.
read variable action
A read variable action is a variable action that reads the values of a given variable.
real constant expression
A real constant expression is a numeric constant expression that refers to a real number. A realization is an abstraction that signifies that the supplier serves as the implementation of the client. (Note that in this context, "implementation" implies a more refined or elaborate form of the client, not necessarily a physical implementation as, say, program code.) The term realize is a stereotype that indicates a realization dependency.
realization
realize
receive
An object receives a message from another object.
receiver
A receiver is an object that receives a message from another object.
reception
A reception is a declaration that a classifier is prepared to react to the receipt of a particular signal with a given behavior.
reclassify object action
A reclassify object action is an action that changes the classifier to which a given object belongs.
redefinable element
A redefinable element is a named element that, when defined in the context of a classifier, can be redefined more specifically or differently in the context of another classifier that directly or indirectly specializes the first classifier. The UML defines eight kinds of redefinable elements:
![]() | activity edge |
![]() | activity node |
![]() | |
![]() | feature |
![]() | redefinable template signature |
![]() | region |
![]() | state |
![]() | transition |
redefinable template signature
A redefinable template signature is a template signature that allows the addition of new formal template parameters in the context of a specializing template classifier.
refine
The term refine is a stereotype that signifies a refinement.Refine the Architecture
Within the RUP, Refine the Architecture is an activity within the Analysis and Design discipline.
This activity involves the following tasks:
![]() | Providing a natural transition from analysis activities to design activities |
![]() | Maintaining the consistency and integrity of the architecture |
![]() | Describing the organization of the system's runtime and deployment architecture |
![]() | Organizing the implementation model |
Refine Business Process Definitions
Within the RUP, Refine Business Process Definitions is an activity within the Business Modeling discipline.
The purpose of this activity is to refine and expand the definitions of the business processes that the new system needs to execute.
refinement
A refinement is a dependency within which the supplier is at a lower level of abstraction than the client.One models a refinement with the use of the refine stereotype. Within the RUP, Refine Roles and Responsibilities is an activity within the Business Modeling discipline. The purpose of this activity is to refine and expand the definitions of the roles and responsibilities of business workers based on the business process realizations. Within the RUP, Refine the System Definition is an activity within the Requirements discipline. This activity involves using a use case model to detail the software requirements of the system being modeled, use this model to reach agreement with the customer about the functionality of the new system, and capture nonfunctional requirements.
Refine Roles and Responsibilities
Refine the System Definition
region
A region is an area within a composite state that contains a set of concurrent substates and a set of transitions.
reification
The term reification refers to the act of reifying something.reify
To reify a model element is to treat it as an object when it normally would not be treated that way.reject
The term reject refers to an OCL operation that creates a Collection which contains all of the elements in a given Collection for which a specified Boolean expression is False.relationship
A relationship is a structural connection between or among model elements.The UML defines two basic kinds of relationships: associations and directed relationships.
release
Within the Unified Process, a release is a complete and consistent set of artifacts delivered to an internal or external customer.
A remove structural feature action is an action that deletes a value from a particular structural feature.
remove variable action
A remove variable action is a variable action that deletes a value from a particular variable.
reply action
A reply action is an action that returns a set of return values and a token, containing return information produced by a previous accept call action, to the trigger of the call.
The term represents is a stereotype that signifies a dependency between a collaboration occurrence and a classifier.
request
A request is a stimulus that is sent to one or more instances.Within the UML, a request takes the form of a call or a signal.
A required interface is an interface that a classifier requires from another classifier.
requirement
A requirement is a stereotype on a comment that signifies that the comment states a responsibility or obligation.Requirements artifact set
Within the RUP, the Requirements artifact set is the set of artifacts related to the definition of what the software system to be developed must accomplish from the customer's point of view.The Requirements artifact set contains the following artifacts:
![]() |
glossary |
![]() | requirements attributes |
![]() | requirements management plan |
![]() | software requirements |
![]() |
stakeholder requests |
![]() | storyboard |
![]() |
supplementary specification |
![]() |
use case model |
![]() |
vision |
Requirements discipline
Within the RUP, the goals of the Requirements discipline include capturing and maintaining the detailed requirements of the system being modeled and designing a user interface focused on the needs and goals of its users and other important stakeholders.
The following activities comprise the Requirements discipline:
![]() | Analyze the Problem |
![]() |
Define the System |
![]() |
Manage Changing Requirements |
![]() |
Manage the Scope of the System |
![]() | Refine the System Definition |
![]() |
Understand Stakeholder Needs |
Within the RUP, a requirements reviewer is a person playing the role of planning and conducting a formal review of the use case model.
requirements specifier
Within the RUP, a requirements specifier is a person playing the role who describes one or more aspects of the system requirements.
Requirements workflow
Within the Unified Process, the purpose of the Requirements workflow is to define a vision of the system to be built and translate that vision into a use case model that defines the detailed requirements of that system.The following activities comprise the Requirements workflow:
![]() | Detail a Use Case |
![]() |
Find Actors and Use Cases |
![]() |
Prioritize Use Cases |
![]() |
Prototype User Interface |
![]() |
Structure the Use-Case Model |
A resolution is a mechanism for turning a received
responsibility
The term responsibility refers to a stereotype attached to a usage dependency to signify that the client has some kind of obligation to the supplier.result (construct)
The term result refers to an OCL construct that contains the return value of an OCL operation.One uses this term within a postcondition. The term result also refers to an OCL operation that returns the return value of the operation call wrapped in a given OclMessage instance.
result (operation)
reviewer
Within the RUP, a reviewer is a person playing the role of providing timely feedback to project team members on one or more artifacts.
review coordinator
Within the RUP, a review coordinator is a person playing the role of facilitating formal reviews and inspections as well as ensuring that they occur on a timely basis and are conducted to a satisfactory standard.
risk-driven
The term risk-driven refers to a process within which each new release is focused on addressing, and subsequently reducing, the most significant risks to the success of a development project.
Within the Unified Process, robustness analysis is a task that involves taking each sentence of a use case, determining the boundary objects, entity objects, and control objects that it needs in order to address the behavior it specifies, and drawing those objects and their relationships.
The results of robustness analysis are depicted on robustness diagrams.
Within the Unified Process, a robustness diagram is a special form of communication diagram that depicts a use case realization–analysis.
role
Within the RUP, a role is a definition of the behavior and responsibilities of an individual or group of individuals working together as a team.
Each role is associated with a set of cohesive activities. The responsibilities of each role are usually expressed in relation to certain artifacts that the role creates, modifies, or controls.
root
A root is a generalizable element that has no parents in a given generalization hierarchy.
run-to-completion step
The term run-to-completion step refers to the full processing of a particular event in the context of a state machine.