Difference between revisions of "UML"
Jump to navigation
Jump to search
| Line 27: | Line 27: | ||
hide circle | hide circle | ||
class Reservation { | class Reservation { | ||
| + | reservationtype:enum{normal,regular} | ||
date: Date | date: Date | ||
duration: int | duration: int | ||
| Line 42: | Line 43: | ||
Reservation "n" <- "1" Reservation | Reservation "n" <- "1" Reservation | ||
</uml> | </uml> | ||
| + | |||
==== Applying inheritance ==== | ==== Applying inheritance ==== | ||
<uml> | <uml> | ||
Revision as of 10:56, 15 December 2018
Tools
Stackoverflow Tags
Tool-Evaluations
- https://www.herzbube.ch/article/evaluation-free-uml-tools
- https://www.predictiveanalyticstoday.com/open-source-free-unified-modeling-language-uml-tools/
Stackoverflow Questions
Inheritance
When implementing inheritance there is usually some cost involved in terms of extra classes, tables, documentation and other results that need to be created after the decision to use inheritance.
Inheritance is about special and general cases. First you might want to ask what is the difference between the cases - (called a discriminator). In your case it is the type of reservation and you could avoid the inheritance by modelling this type of reservation and implementing the different behavior based on the reservation type. That would lead to a design like:
Avoiding inheritance
Applying inheritance
class Reservation { date: Date duration: int price: int delete(): boolean } class Client { name } </uml>