Difference between revisions of "UML"
| Line 33: | Line 33: | ||
name | name | ||
} | } | ||
| + | </uml> | ||
==== Avoiding inheritance ==== | ==== Avoiding inheritance ==== | ||
class Regular_Reservation { | class Regular_Reservation { | ||
Revision as of 10:48, 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
class Regular_Reservation { start:date end:date frequency:int new(date,date,int) } Reservation -> Client Reservation <|-- Regular_Reservation Reservation "n" <- "1" Regular_Reservation </uml>
