E
elaboration phase
Within the Unified Process, the elaboration phase is the phase of a development project in which most of the use case model is specified in detail and the architecture is designed.
The primary goal of this phase is to produce an architecture baseline that can serve as the foundation for the new system. The UML defines two types of elements: model elements and presentation elements.
element
An element is an atomic constituent of a model.
The term element import is a stereotype attached to a dependency to signify that the package serving as the client has the right to add the public contents of the package serving as the supplier to its namespace.
If a package imports an element with the same name as an element contained within the package, the import must have an associated alias.
else
The term else is a word used in conjunction with a branch to indicate the path to be taken if the guards on the associated paths all evaluate to False.An encapsulated classifier is a structured classifier that can own ports.
encapsulated classifier
The term entity is a stereotype on a component that signifies persistent information related to some business concept.
entity class
Within the Unified Process, the term entity class is a stereotype attached to a class to signify that the class models long-lived information that may be persistent. Within the Unified Process, an entity object is an instance of an entity class.
entry action
An entry action is an action that is performed unconditionally just after an object enters a particular state. The entry action must finish before the object performs any other actions or activities.
An entry action is denoted with the word entry.
An entry point is a pseudostate that represents an entry point of a state machine.
entry point
enumeration
The term enumeration is a stereotype that signifies a predefined or user-defined datatype that has an ordered list of enumeration literals.
An enumeration constant expression is a constant expression that refers to an enumeration literal.
enumeration constant expression
enumeration literal
An enumeration literal is a member of an enumeration.
Within the RUP, the Environment artifact set is a set of artifacts related to the environment in which the development of a system occurs.
The Environment artifact set contains the following artifacts:
![]() |
development case |
![]() |
development infrastructure |
![]() |
development organization assessment |
![]() |
project-specific guidelines |
![]() |
project-specific templates |
![]() |
tools |
Environment discipline
Within the RUP, the purpose of the Environment discipline is to support the development team with processes and tools.![]() |
Prepare Environment for Iteration |
![]() |
Prepare Environment for Project |
![]() |
Support Environment During Iteration |
equals
The term equals refers to an OCL operator that works on Collections.![]() |
For two Sets, an operation containing the equals operator returns True if both Sets contain the same elements. |
![]() |
For two Bags, that operation returns True if both Bags contain the same elements and the number of times each of those elements appears in each Bag is also the same. |
![]() |
For two Sequences, that operation returns True if both Sets contain the same elements and the order of those elements is the same within both Sequences. |
Evaluate Project Scope and Risk
Within the RUP, Evaluate Project Scope and Risk is an activity within the Project Management discipline.
The purpose of this activity is to evaluate the intended capabilities and characteristics of the project, and the associated risks, after the project is initiated and again at the end of each iteration.
This activity involves evaluating the testing efforts within a given iteration by comparing the results with the goals described in the test plan.
event
An event is a noteworthy occurrence, of interest to one or more objects, that has a location in time and space.
The UML defines four kinds of events:
![]() |
call event |
![]() |
change event |
![]() |
signal event |
![]() |
time event |
event-driven object
The term event-driven object is a synonym of reactive object.An event occurrence is an interaction fragment that represents a moment in time with which an action is associated. This takes the form of a syntactic point at the end of a message or at the beginning or end of an execution occurrence.
exception
The term exception signifies a signal used in conjunction with a class to model an exception that the given class can throw or receive in response to a failure during system execution.A exception handler is an element that specifies an executable node to execute in case a specified exception occurs during the execution of another executable node.
exception handler
The term excludes refers to an OCL operation that returns True if a specified object is not an element of a given Collection.
The term excludesAll refers to an OCL operation that returns True if none of the objects within a specified Collection are elements of another given Collection.
excluding
The term excluding refers to an OCL operation that works on a Collection.
![]() |
For a Set, the including operation removes a given object. |
![]() |
For a Bag or a Sequence, the operation removes all occurrences of a given object. |
executable
The term executable is a stereotype attached to an artifact to signify a piece of executable software.executable node
An executable node is an activity node that may be executed. An executable node owns one or more exception handlers via composition relationships.
execution environment
The term execution environment is a stereotype attached to a node to signify that the node offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts.
execution occurrence
An execution occurrence is an interaction fragment that represents the instantiation of a unit of a particular behavior on a lifeline, expressed in terms of a starting event occurrence (such as the receipt of a message) and an ending event occurrence (such as a reply to that message).
The term exists refers to an OCL operation that returns True if a specified expression is true for at least one element within a given Collection.
exit action
An exit action is an action that is performed unconditionally just before an object leaves a given state.One denotes an exit action with the word exit.
An exit point is a pseudostate that represents an exit point of a state machine.
exit point
expansion kind
The term expansion kind refers to an enumeration that describes how multiple executions of an expansion region interact. There are three values:
iterative ( parallel ( stream (
An expansion node is an object node that indicates a flow across the boundary of an expansion region. A flow into a region contains a collection that is broken into its individual elements inside the region; the region then executes once per element. A flow out of a region combines individual elements into a collection for use outside the region.
expansion node
An expansion region is a structured activity node that executes once for each element within a given collection of values in a particular expansion node.
These executions occur based on a specified expansion kind value. The results of the executions may form one or more new expansion nodes.
Explore Process Automation
Within the RUP, Explore Process Automation is an activity within the Business Modeling discipline.
The purpose of this activity is to explore the possibilities of automating some or all of the business processes that the new system needs to execute. An expression is a structured tree of symbols that denotes a (possibly empty) set of values when evaluated in a context. The term extend refers to a directed relationship within which the client use case "extends" the behavior of the supplier use case at the supplier’s extension points. An extend relationship may specify, in the form of a constraint, the condition(s) under which the extension is relevant. If there is no constraint, the extension is unconditional. One generally uses an extend relationship to model optional system behavior, such as error handling, or behavior that only occurs under certain conditions.
export
In the context of a package, to export an element is to make it accessible outside of the namespace to which it belongs by setting its visibility to a level that permits it to be seen by other packages.
expression
extend
extensibility
The term extensibility refers to the ability to extend the UML in controlled ways.
The UML defines three extensibility mechanisms:
![]() |
constraint |
![]() |
stereotype |
![]() |
tag definition |
An extension is an association that indicates that the properties of a particular metaclass are extended through a particular stereotype.
An extension end is a property that ties an extension to a stereotype.
extension point
An extension point is a named marker that references one or more locations within the behavioral sequence of a use case at which additional behavior can be inserted, thus extending the use case.
An extension point must specify the point(s) in the use case at which the extending behavior comes into play.