~A~

Abstract Class

A Class that cannot be directly instantiated.

Abstraction

The essential characteristics of an entity that distinguish it from all other kinds of entities. An abstraction defines a boundary relative to the perspective of the viewer.

Action

The specification of an executable statement that forms an abstraction of a computation procedure. An action typically results in a change in the state of the system, and can be realized by sending a message to an object or modifying a connector or a value of an attribute.

Action Sequence

An expression that resolves to a sequence of actions.

Action State

A State that represents the execution of an atomic Action, typically the invocation of an operation.

Activation

The execution of an Action.

Active Class

A Class whose instances are Active Objects. When instantiated, an Active Class controls its execution. Rather than being invoked or activated by other objects, it can operate standalone, and define its own thread of behavior.

Active Object

An object that owns a thread and can initiate control activity. An instance of an active Class.

Activity

Defines the bounds for the structural organization that contains a set of basic or fundamental behaviors. It can used to model procedural type application development for system design through to modeling business processes in organizational structures and workflow.

Activity Diagram

A diagram used to model procedural type application development for system design through to modeling business processes in organizational structures and workflow.

Activity Graph

A special case of a StateMachine that is used to model processes involving one or more classifiers.

Actor (Class)

A coherent set of roles that users of Use Cases play when interacting with these Use Cases. An Actor has one role for each Use Case with which it communicates.

Actual Parameter

A binding for a parameter that resolves to a run-time instance.

Aggregate (Class)

A Class that represents the 'whole' in an Aggregation (whole-part) relationship.

Aggregation

A special form of Association that specifies a whole-part relationship between the Aggregate (whole) and a component part.

Analysis

The part of the software development process whose primary purpose is to formulate a model of the problem domain. Analysis focuses on what to do, design focuses on how to do it.

Analysis Diagram

A diagram used to capture high level business processes and early models of system behavior and elements. It is less formal than some other diagrams, but provides a good means of capturing the essential business characteristics and requirements.

Analysis Time

Refers to something that occurs during an analysis phase of the software development process.

Architecture

The organizational structure and associated behavior of a system. An architecture can be recursively decomposed into parts that interact through interfaces, relationships that connect parts, and constraints for assembling parts. Parts that interact through interfaces include Classes, Components and subsystems.

Argument

A binding for a parameter that resolves to a run-time instance.

Artifact

A physical piece of information that is used or produced by a business or development process. Examples of Artifacts include models, source files, scripts, and binary executable files. An Artifact can constitute the implementation of a deployable component.

Assembly

A connector that bridges the required interface of a component with the provided interface of a second component.

Association

The semantic relationship between two or more classifiers that specifies connections among their instances.

Association Class

A model element that has both Association and Class properties. An Association Class can be seen as an Association that also has Class properties, or as a Class that also has Association properties.

Association End

The endpoint of an Association, which connects the Association to a classifier.

Attribute

A feature within a classifier that describes a range of values that instances of the classifier can hold.

Auxiliary Class

A stereotyped Class that supports another more central or fundamental Class, typically by implementing secondary logic or control flow. Auxiliary Classes are typically used together with focus Classes, and are particularly useful for specifying the secondary business logic or control flow of components during design.