A class that cannot be directly instantiated.
Contrast: concrete class
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.
The specification of an executable statement that forms an abstraction of a computational 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 link or a value of an attribute.
An expression that resolves to a sequence of actions.
A state that represents the execution of an atomic action, typically the invocation of an operation.
The execution of an action.
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.
See also: active object
An object that owns a thread and can initiate control activity. An instance of active class.
See also: Active class, thread
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.
An activity diagram can used to model procedural type application development for system design through to modeling business processes in organizational structures and workflow.
A special case of a state machine that is used to model processes involving one or more classifiers.
Contrast: state chart diagram
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.
A class that represents the 'whole' in an aggregation (whole-part) relationship.
See also: aggregation
A special form of association that specifies a whole-part relationship between the aggregate (whole) and a component part.
See also: composition
The part of the software development process whose primary purpose is to formulate a model of the problem domain. Analysis focuses what to do, design focuses on how to do it.
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.
Refers to something that occurs during an analysis phase of the software development process.
See also: design time, modeling time
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.
A binding for a parameter that resolves to a run-time instance.
Synonym: actual parameter
A physical piece of information that is used or produced by a software development process. Examples of Artifacts include models, source files, scripts, and binary executable files. An artifact can constitute the implementation of a deployable component.
An assembly connector bridges the required interface of a component with the provided interface of a second component.
The semantic relationship between two or more classifiers that specifies connections among their instances.
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.
The endpoint of an association, which connects the association to a classifier.
A feature within a classifier that describes a range of values that instances of the classifier can hold.
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.
See also: focus