The UML 2 Class Diagram – Part 2
Filed under Common
Associations
An association implies that two or more model elements having a relationship, implemented as an instance variable in one class. With this connector you may include, named roles at each end, cardinality, direction and constraints.
Generalizations
With a generalization you indicate inheritance. If it’s drawn from a specific classifier to a general classifier, the generalize implication is that the source inherits the target’s characteristics.
Aggregations
Aggregations are depicting elements which are made up of smaller components. This aggregation relationships will be shown by a white diamond-shaped arrowhead pointing towards the target or parent class.
Association Classes
With an association class you can construct an association connection to make operations and attributes.
Dependencies
If you need to model a wide range of dependent relationships between model elements you use dependencies. This will be done early in the design process. Later on the dependencies will be stereotyped or replaced with more specific data.
Traces
With traces yo can easily track requirements or model changes, because it is a specialization of a dependency, linking model elements or sets of elements, representing the same idea across models.
Realizations
A realization expresses traceability and completeness in a model.
Nestings
Nestings are connectors showing source elements within a target element.
Click to read part 1 of the UML 2 Class Diagram
