An object-oriented programming language based on the earlier 'C' language.
An action state that invokes an operation on a classifier.
The number of elements in a set.
Computer Aided Software Engineering. A tool designed for the purpose of modeling and building software systems.
In a generalization relationship, the specialization of another element, the parent.
See also: subclass, subtype.
A pseudo-state used to compose complex transitional paths, where the outgoing transition path is decided by dynamic, run-time conditions determined by the actions performed by the state machine on the path leading to the choice.
A description of a set of objects that share the same attributes, operations, methods, relationships and semantics. A class can use a set of interfaces to specify collections of operations it provides to its environment.
See also: interface
A diagram that shows a collection of declarative (static) model elements, such as classes, types, and their contents and relationships.
The assignment of an object to a classifier.
See also: dynamic classification, multiple classification and static classification.
A mechanism that describes behavioral and structural features. Classifiers include interfaces, classes, datatypes, and components.
A classifier that requests a service from another classifier.
The specification of how an operation or classifier, such as a use case, is realized by a set of classifiers and associations playing specific roles used in a specific way. The collaboration defines an interaction.
See also: interaction
Used pre - UML 2.0.
Uses an Occurrence to apply a pattern defined by a collaboration to a specific situation.
A combined fragment reflects a piece or pieces of interaction (called interaction operands) controlled by an interaction operator, whose corresponding boolean conditions are known as interaction constraints. It appears graphically as a transparent window, divided by horizontal dashed lines for each operand.
An annotation attached to an element or a collection of elements. A note has no semantics.
A diagram that shows the interactions between elements at run-time in much the same manner as a sequence diagram. However, communication diagrams are used to visualize inter-object relationships, while sequence diagrams are more effective at visualizing processing over time.
Refers to something that occurs during the compilation of a software module.
See also: modeling time, run time
A modular, deployable, and replaceable part of a system that encapsulates implementation and exposes a set of interfaces. A component is typically specified by one or more classifiers (eg., implementation classes) that reside on it, and can be implemented by one or more artifacts (eg., binary, executable, or script files).
A diagram that shows the organizations and dependencies among components.
A class that is related to one or more classes by a composition relationship.
See also: composition
A state that consists of either concurrent (orthogonal) substates or sequential (disjoint) substates.
See also: substate
composite structure diagram
A diagram that reflects the internal collaboration of classes, interfaces, or components to describe a functionality. Composite structure diagrams are similar to class diagrams, except that they model a specific usage of the structure.
A form of aggregation which requires that a part instance be included in at most one composite at a time, and that the composite object is responsible for the creation and destruction of the parts. Composition can be recursive.
Synonym: composite aggregation
A class that can be directly instantiated.
Contrast: abstract class
The occurrence of two or more activities during the same time interval. Concurrency can be achieved by interleaving or simultaneously executing two or more threads.
See also: thread
A substate that can be held simultaneously with other substates contained in the same composite state.
See also: composite state
Contrast: disjoint substate
A logical link between model elements. Can be structural, dynamic or possessive.
|1.||A semantic condition or restriction. Certain constraints are predefined in the UML, others can be user defined. Constraints are one of three extensibility mechanisms in UML. |
See also: Tagged Value, stereotype
|2.||A rule or condition that applies to some element. It is often modeled as a pre- or post- condition.|
|1.||An instance that exists to contain other instances, and that provides operations to access or iterate over its contents.(for example, arrays, lists, sets).|
|2.||A component that exists to contain other components.|
A namespace hierarchy consisting of model elements, and the containment relationships that exist between them. A containment hierarchy forms a graph.
A view of a set of related modeling elements for a particular purpose, such as specifying an operation.
A Continuation is used in seq and alt combined fragments, to indicate the branches of continuation an operand follows.
A stereotyped class that represents a controlling entity or manager. A control organizes and schedules other activities and elements. It is the controller of the Model-View-Controller pattern.
A connector linking two nodes in an activity diagram. Control Flow connectors start a nodes activity when the preceding nodes action is finished.