A

ACID:

Atomic, Consistent, Isolated, and Durable. Terminology used to identify principles that should be followed when designing transactions and session beans involving transactions.

activation:

The reloading of a swapped out stateful session EJB that may be needed again.

activity diagram:

A UML diagram that is an extension of a statechart diagram. Allows modeling of the systems behavior in terms of interaction or flow of control.

actor:

Used in use case diagrams. An actor represents something or someone outside the system, for example, a user of the system.

aggregation:

A stronger form of association. Used to show a logical containment relationship, that is, a whole formed of parts.

analysis:

The process of understanding the requirements and transforming them into a system design.

analysis class:

Classes created during analysis that are typically not implemented in software. Rather, they are refined later into design classes and subsystems.

architecture:

The architecture of a software system deals with the structural aspects of the system as well as the system's usability, performance, resilience, reuse, and so on.

association:

An association between two classes specifies that some sort of structural relationship exists between the classes.