Prev Next

~E~

Terms starting with E

Name

Detail

See also

Element

  1. An atomic constituent of a model.
  2. A model object of any type, such as Class, Component, Node or Object.

Endpoint

Used in Interaction diagrams to reflect a lost message in sequence.

Entity

A store or persistence mechanism that captures the information or knowledge in a system. It is the Model in the Model-View-Controller Pattern.

Entry Action

An action executed upon entering a State in a StateMachine regardless of the transition taken to reach that State.

Entry Point

Used to define where external states can enter a Sub Machine.

Enumeration

A list of named values used as the range of a particular attribute type. For example, RGBColor = {red, green, blue}. Boolean is a predefined enumeration with values from the set {false, true}.

Event

The specification of a significant occurrence that has a location in time and space. In the context of State diagrams, an event is an occurrence that can trigger a transition.

Exception Handler

An element that defines the group of operations to carry out when an exception occurs.

Exit Action

An action executed upon exiting a State in a StateMachine regardless of the transition taken to exit that State.

Exit Point

Used in SubMachine states and StateMachines to denote the point where the machine is exited and the transition sourcing this exit point, for SubMachines, is triggered. Exit points are a type of pseudostate used in the StateMachine diagram.

Export

In the context of Packages, to make an element visible outside its enclosing namespace.

Visibility Import

Expose Interface

A toolbox icon that is a graphical way to depict the required and supplied interfaces of a Component, Class or Part.

Expression

A string that evaluates to a value of a particular type. For example, the expression (7 + 5 * 3) evaluates to a value of type number.

A relationship from an extension Use Case to a base Use Case, specifying how the behavior defined for the extension Use Case augments (subject to conditions specified in the extension) the behavior defined for the base Use Case. The behavior is inserted at the location defined by the extension point in the base Use Case. The base Use Case does not depend on performing the behavior of the extension Use Case.

Include

Extend

A connector used to indicate that an element extends the behavior of another. Extensions are used in Use Case models to indicate one Use Case (optionally) extends the behavior of another.

Include