Class diagram
From Wikipedia, the free encyclopedia
In the Unified Modeling Language (UML), a class diagram is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, and the relationships between the classes.
Contents |
[edit] Classes
A class in the software system is represented by a box with the name of the class written inside it. Classes may also be used to represent domain or other non-software elements.
An optional compartment below the class name can show the class's attributes (i.e., its properties). Each attribute is shown with at least its name, and optionally with its type, initial value, and other properties.
The class's operations (indicating the methods) can appear in another compartment. Each operation is shown with at least its name, and optionally also with its parameters and return type.
Other compartments may be defined, e.g., to capture responsibilities, requirements, constraints.
Attributes and operations may have their visibility marked as follows:
- "+" for public
- "#" for protected
- "-" for private
- "~" for package
[edit] Relationships
A relationship is a general term covering the specific types of logical connections found on class and object diagrams. UML shows the following relationships:
[edit] Instance-Level Relationships
[edit] Link
A Link is the basic relationship among objects. It is represented as a line connecting two or more object boxes. It can be shown on an object diagram or class diagram. A link is an instance of an association.
[edit] Association
An association represents a family of links. Binary associations (with two ends) are normally represented as a line, with each end connected to a class box. Higher order associations can be drawn with more than two ends. In such cases, the ends are connected to a central diamond.
An association can be named, and the ends of an association can be adorned with role names, ownership indicators, multiplicity, visibility, and other properties.
Associations can only be shown on class diagrams.
[edit] Aggregation
Aggregation is a variant of the "has a" or association relationship; composition is more specific than aggregation. As a type of association, an aggregation can be named and have the same adornments that an association can. However, an aggregation may not involve more than two classes.
Aggregation can occur when a class is a collection or container of other classes, but where the contained classes do not have a strong life cycle dependency on the container--essentially, if the container is destroyed, its contents are not.
In UML, it is graphically represented as a clear diamond shape on the containing class end of the tree of lines that connect contained class(es) to the containing class.
[edit] Composition
Composition is a stronger variant of the "has a" or association relationship; composition is more specific than aggregation.
Composition a strong life cycle dependency between instances of the container class and instances of the contained class(es): If the container is destroyed, any containees are also destroyed.
The UML graphical representation of a composition relationship is a black diamond shape on the containing class end of the tree of lines that connect contained class(es) to their containing class.
[edit] Differences between Composition and Aggregation
The whole of a composition must have a multiplicity of 0..1 or 1, indicating that a part must be for only one whole. The whole of an aggregation may have any multiplicity.
When attempting to represent real-world whole-part relationships, e.g., an engine is part of a car, the composition relationship is most appropriate. However, when representing a software or database relationship, e.g., car model engine ENG01 is part of a car model CM01, an aggregation relationship is best, as the engine, ENG01 may be also part of a different car model, CM02. This is often called a "catalog" relationship.
[edit] Class Level Relationships
[edit] Generalization
The generalization relationship indicates that one of the two related classes (the supertype) is considered to be a more general form of the other (the subtype). In practice, this means that any instance of the subtype is also an instance of the supertype (An exemplary tree of generalizations of this form is found in binomial nomenclature: human beings are a subtype of simian, which are a subtype of mammal, and so on). The relationship is most easily understood by the phrase 'A is a B' (a human is a mammal, a mammal is an animal).
The UML graphical representation of a Generalization is a hollow triangle shape on the supertype end of the line (or tree of lines) that connects it to one or more subtypes.
The generalization relationship is also known as the inheritance or "is a" relationship.
The supertype in the generalization relationship is also known as the "parent", superclass, base class, or base type.
The subtype in the generalization relationship is also known as the "child", subclass, derived class, derived type, inheriting class, or inheriting type.
Note that this relationship bears no resemblance to the biological parent/child relationship: the use of these terms is extremely common, but can be misleading.
- Generalization-Specialization relationship
- A is a type of B
- E.g. "an oak is a type of tree", "a sedan is a type of vehicle"
Generalizations can only be shown on class diagrams.
[edit] Realization
In UML modeling, a realization relationship is a relationship between two model elements, in which one model element (the client) realizes the behavior that the other model element (the supplier) specifies. A realization is displayed in the diagram editor as a dashed line with an unfilled arrowhead
Realizations can only be shown on class diagrams.
[edit] General Relationship
[edit] Dependency (UML)
A dependency exists between two defined elements if a change to the definition of one would result in a change to the other. This is indicated by a dashed arrow pointing from the dependent to the independent element. Several named varieties exist. A dependency can be between instances, classes, or both.
[edit] Multiplicity
The association relationship indicates that (at least) one of the two related classes makes reference to the other. In contrast with the generalization relationship, this is most easily understood through the phrase 'A has a B' (a mother cat has kittens, kittens have a mother cat).
The UML representation of an association is a line with an optional arrowhead indicating the role of the object(s) in the relationship, and an optional notation at each end indicating the multiplicity of instances of that entity (the number of objects that participate in the association). Common multiplicities are:
| 0..1 | No instances, or one instance (optional, may) |
| 1 | Exactly one instance |
| 0..* or * | Zero or more instances |
| 1..* | One or more instances (at least one) |
The association relationship is also known as the "has a" relationship.
In the diagram above (used to illustrate aggregation) One Professor has at least one class or more. One class has exactly one professor.
