Choose a domain/topic for your homework.
Create a conceptual model of that domain using UML Class Diagrams and a structured textual description (see e.g. this data specification) of what is represented in the domain model.
The consecutive homework parts will then be governed by this conceptual model.
- 5 to 8 classes
Each class 2 to 4 attributes, some with multiplicity
Attributes inherited from a parent class in an inheritance hierarchy count as well, i.e. it is ok not to create attributes for a child class if parent class already has 2 to 4.
- At least 4 associations. Include association end multiplicities
Use a tool that allows you to draw UML Class Diagrams and export them, ideally as SVG, PNG if SVG not possible.
For example, diagrams.net, PlantUML or LucidChart.
Beware that the free version of LucidChart does not support "copy as new" functionality.
The homework is to be turned in via the study system by a group leader.
- A zipped file named
.png) with the image of the conceptual model and
UTF-8 containing the structured textual description of the domain model.
Some of you were still thinking about data in terms of an application, and what the application means, instead of focusing on what the data represents in the real world.
Attributes should be primitive values (strings, dates, booleans) of the real world entity represented by the class.
When they are more complex, they typically represent another real world entity and its primitive attributes.
Common mistake was including attribute of another real world entity, which should be solved by introducing a new class and a relationship to it.
Typically something, which exists independently of the current entity, and has a label.
For instance, "country" attribute of a "customer".
Country exists independently of the customer.
Country name is an attribute of the "country" real world entity, not of the "customer".
"Customer" lives in a country - is a relationship.
1..* multiplicities means that the source entity cannot exists in your data without at least one relationship to the other entity.
For instance, having a food producer connected to their items sold in an eshop this way means, that when their last item from the eshop is removed, data about the producer needs to be removed as well.
I.e. there cannot be data about any producers, which (even temporarily) do not have any items... might be problematic.