Class diagrams in UML can show various relationships between classes including generalization, association, aggregation, composition, and dependency. Generalization specifies inheritance between a base class and derived class. Association defines a relationship between two classes without ownership. Aggregation represents a whole-part relationship where the part can exist without the whole. Composition is a stronger form of aggregation where the part cannot exist without the whole. Dependency specifies that a change to one class may affect another class.

1. Relations between Class Diagrams - UML Harish Alwala

3. Class Diagram A Class defines the attributes and the methods of a set of objects. All objects of this class (instances of this class) share the same behaviour, and have the same set of attributes (each object has its own set). Stereotype for Attributes & Operations private - public + protected # Class Dependency Dependency is a form of association that specifies a dependency relationship between two classes. An arrowhead can be used to indicate an asymmetric dependency. Symmetric dependency doesn’t have arrowhead

4. Generalization- Inheritance a Generalisation association between two classes puts them in a hierarchy representing the concept of inheritance of a derived class from a base class

5. Association Associations can have a role that specifies the purpose of the association and can be uni- or bidirectional (indicates if the two objects participating in the relationship can send messages to the other) An association usually means that you have a sentence that describes a relation between two (or more) classes. Examples of associations: Node class contains Attribute classes. Driver class drives Car class. Transaction class modifies Table classes. Manager class starts Machine class. Page class contains Widget classes.

6. Composite Aggregation Composition is a form of symmetric association that specifies a whole-part relationship between the composition (whole) class and a subordinate (part) class in which removing the whole also removes the parts. For example: In relational databases, a cascading delete is a good example of a composition relationship. Window contains title, Table row and columns A whole-part relationship between the Person (whole) class and the Head (part) class. In this example, removing the person also removes the head and removing the head effectively destroys the person - the person and head must exist together in the context of a living person