Understanding UML Associations, Aggregations, Compositions, Generalization and Specialization

Consider the differences and similarities among the object classes pet, dog, tail, and owner, illustrating relationships such as the owner feeding the pet (association), the tail being part of a dog or cat (aggregation/composition), and a cat being a kind of pet (generalization).

The three types of association connectors—association, aggregation, and composition—are shown in the following UML diagrams.

Association

If two classes need to communicate, a link—represented by an association connector—must exist between them.

An association is drawn as a line between the classes; arrows on the line indicate navigation direction, and a line with arrows on both ends denotes a bidirectional association.

Multiplicity can be shown by adding multiplicity symbols on the association line. For example, a student may have one or many mentors:

The reverse example shows that each teacher can have one or many students:

Roles can also be specified on an association to indicate the behavior of the linked objects.

Association vs Aggregation vs Composition

The question “What is the difference between association, aggregation, and composition?” is frequently asked.

Aggregation and composition are special kinds of association. In both cases one class “owns” another, but they differ subtly:

Aggregation means the child component can exist independently of the parent (e.g., a class A representing a class B like a class ‘Classroom’ and a class ‘Student’; deleting the class ‘Classroom’ does not delete the ‘Student’ objects).

Composition means the child cannot exist without the parent (e.g., a ‘House’ and its ‘Room’; removing the house also removes its rooms).

Composition Example

When a strong lifecycle dependency exists—deleting class A also deletes class B—a composition link should be used.

Aggregation Example

Aggregation does not imply ownership; it merely indicates that the aggregated object may be shared by multiple containers.

In summary, association is a generic relationship indicating that one class uses another; when the child cannot exist without the parent, the relationship is a composition; if the child can exist independently, it is an aggregation.

Generalization and Specialization

Generalization is a mechanism for grouping similar classes into a more abstract superclass that captures common attributes and behaviors, while allowing subclasses to have more specialized features.

Specialization is the inverse process, creating more specific subclasses from a general class.

For example, a bank account can be specialized into savings accounts and credit‑card accounts, which inherit common properties such as account number and balance, while adding their own unique attributes.

Generalization and Inheritance

In UML, generalization is the term used to represent the abstraction of common attributes into a base class; the UML generalization arrow also denotes inheritance in programming languages. Thus, generalization and inheritance refer to the same concept, differing only in context.

Thank you for reading.