|
| |
[E]
- elaboration
The second phase of the process where the
product vision and its architecture
are defined.
element
An atomic constituent of a model.
enclosed document
A document can be enclosed by another
document to collect a set of documents into a whole; the enclosing document as
well as the individual enclosures are regarded as separate artifacts.
enhancement request
A type of stakeholder request that
specifies a new feature or functionality of the
system. See also: change request
entity class
A class used to model information that has been
stored by the system, and the associated behavior. A generic class, reused in
many use cases, often with persistent
characteristics. An entity class defines a set of entity objects, which
participate in several use cases and typically survive those use cases.
entry action
An action executed upon entering a state in a state
machine regardless of the transition taken to reach that state.
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.
environment
A core supporting workflow in the
software-engineering process, whose purpose is to define and manage the
environment in which the system is being developed. Includes process
descriptions, configuration management,
and development tools.
evolution
The life of the software after its initial development cycle; any subsequent
cycle, during which the product evolves.
evolutionary
An iterative development strategy that acknowledges that user needs are not
fully understood and therefore requirements are refined in each succeeding
iteration (elaboration phase).
exit action
An action executed upon exiting a state in a state
machine regardless of the transition taken to exit that state.
export
In the context of packages, to make an element
visible outside its enclosing namespace. See: visibility.
Contrast: export
[OMA], import.
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.
extend
A relationship from an extension use case to a base use case, specifying how
the behavior defined for the extension use case can be inserted into the
behavior defined for the base use case.
extend-relationship
An extend-relationship from a use-case class A to a use-case class B
indicates that an instance of B may include (subject to specific conditions
specified in the extension) the behavior specified by A. Behavior specified by
several extenders of a single target use case can occur within a single
use-case instance.
[F]
facade
A special package, stereotyped «facade», within a subsystem that organizes
and exports all information needed by the clients of the subsystem. Included
in this package are interfaces (where the
interfaces are unique to the subsystem), realization relationships to
interfaces outside the subsystem, and any documentation needed by clients of
the subsystem to use the subsystem.
fault
An accidental condition that causes a component in the implementation model
to fail to perform its required behavior. A fault is the root cause of one or
more defects.
feature
An externally observable service provided by the system which directly
fulfills a stakeholder need.
A property, like operation or attribute, which is encapsulated within a
classifier, such as an interface, a class, or a datatype.
final state
A special kind of state signifying that the enclosing composite
state or the entire state machine
is completed.
fire
To execute a state transition. See: transition.
focus of control
A symbol on a sequence diagram that
shows the period of time during which an object is performing an action,
either directly or through a subordinate procedure.
formal parameter
Synonym: parameter.
framework
A micro-architecture that provides an
extensible template for applications within a
specific domain.
FURPS
An acronym representing categories for assessing product quality:
Functionality, Usability, Reliability, Performance, Supportability.
[G H]
- generalizable element
A model element that may participate in a generalization relationship. See: generalization.
generalization
A taxonomic relationship between a more general element and a more specific
element. The more specific element is fully consistent with the more general
element and contains additional information. An instance of the more specific
element may be used where the more general element is allowed. See: inheritance.
generation
Final release at the end of a cycle.
green-field development
Development "starting from scratch", as opposed to "evolution
of an existing system" or "reengineering of a legacy piece".
(Originated from the transformation that takes place when building a new
factory on an undeveloped site - with grass on it.)
guard condition
A condition that must be satisfied in order to enable an associated transition
to fire.
|
