| ... | ... | @@ -5,7 +5,7 @@ The **class diagram** is used to describe central classes within a software syst |
|
|
|
For example, you can use it in the early design phase of a new software system to model the essential classes, attributes, and their relations.
|
|
|
|
|
|
|
|
# Obligations for the lectures and the final exam in "Softwaretechnik" (Tips for Modeling)
|
|
|
|
When creating a **class diagram**, remember that it must contain all necessary information (attributes, methods, visibility, relationships). Otherwise a component diagram is useless and can be thrown away. Especially for relationships (associations) it is important to specify the cardinality (e.g., 1, 0..\*, 1..\*) and the name of it (e.g., "provides", "contains", "has")
|
|
|
|
When creating a **class diagram**, remember that it must contain all necessary information (attributes, methods, visibility, relationships). Otherwise a class diagram is useless and can be thrown away. Especially for relationships (associations) it is important to specify the cardinality (e.g., 1, 0..\*, 1..\*) and the name of it (e.g., "provides", "contains", "has")
|
|
|
|
An example class diagram is shown in [Example Class Diagram](#an-example-class-diagram-for-the-given-scenario).
|
|
|
|
|
|
|
|
# What is a Class?
|
| ... | ... | |
