UML Class Diagrams show types and the relationships between them, e.g. specialization or composition. The UML Class Diagrams supported in ARCWAY Cockpit only contain a small, simplified subset of the various syntactical elements of UML Class Diagrams as defined by the UML standard.
 |
The Package serves as a container for types. |
 |
The Type represents an object type or data type, e.g. a certain class or a primitive type like Integer. |
 |
Attributes represent properties of a type. Alternativly this attribute can als be a type. In this case the inner type is part of the outer type. The semantics are equal to a composition then. |
 |
The Specialization indicates that one type is a specialization of another type. In this example Supplier and Customer are specializations of the type Person. |
 |
The Aggregation indicates an association between one instance of a type and many instances of another type, in which the instances of the two types are independent of each other. In this example each Customer is associated with many Orders. |
 |
The Composition indicates an association between one instance of a type and many instances of another type, in which the instances of the latter depend on the existence of the instance of the first. In this example each Order is associated with many Line Items, but Line Items cannot exist without an Order. |
 |
The Association indicates a general association between instances of two types. The cardinality of the association is 1:1, unless otherwise stated at the ends of the association. |
|
A plan element that contains another element graphically is also
considered to be its container in the repository. A containment
will also emerge from modeling a specialisation, a composition or
an aggregation between two types. |
| An association between two types will create a bidirectional access relation between these types. |