diff options
| author | mo khan <mo.khan@gmail.com> | 2020-03-03 18:43:16 -0700 |
|---|---|---|
| committer | mo khan <mo.khan@gmail.com> | 2020-03-03 18:43:16 -0700 |
| commit | eadec5895c9bacb42a5fe0c998b24aa04677c85d (patch) | |
| tree | d3b808c1c7b83cd521f6687b153d463d970b76d3 | |
| parent | 9eae3e3aeb82645ea6dae9ed894e1aaec3854ddc (diff) | |
Add inheritance to EER diagram
| -rw-r--r-- | assignments/final/README.md | 2 | ||||
| -rw-r--r-- | assignments/final/module-1.png | bin | 31666 -> 48735 bytes | |||
| -rw-r--r-- | assignments/final/module-1.puml | 32 |
3 files changed, 26 insertions, 8 deletions
diff --git a/assignments/final/README.md b/assignments/final/README.md index ce61fd9..c45071a 100644 --- a/assignments/final/README.md +++ b/assignments/final/README.md @@ -100,7 +100,7 @@ It's possible that implementation inheritance may need to be modeled in this cas I think that when people model data they tend to jump towards class/subclass relationship too early in the design process. I prefer to favour composition over inheritance. If the Liskov substitution principle holds -true for any relationship than I think moving towards implementation inheritance is fine. +true for any relationship then I think moving towards implementation inheritance is fine. **Can the business rules paradigm, and the ability to easily define, implement, and maintain business rules, be used as a competitive advantage in a hospital environment such as the RVH?** diff --git a/assignments/final/module-1.png b/assignments/final/module-1.png Binary files differindex d3b9221..626986e 100644 --- a/assignments/final/module-1.png +++ b/assignments/final/module-1.png diff --git a/assignments/final/module-1.puml b/assignments/final/module-1.puml index 62dc90e..d5b0cf7 100644 --- a/assignments/final/module-1.puml +++ b/assignments/final/module-1.puml @@ -7,8 +7,6 @@ entity "Bed" as beds { -- bed_number : number room_number : number - care_centre_id : number <<FK>> - patient_id : number <<FK>> } entity "CareCentre" as care_centres { @@ -19,11 +17,16 @@ entity "CareCentre" as care_centres { nurse_in_charge : number <<FK>> } +entity "Timesheet" as timesheets { + id : number << generated >> + -- + hours : number + week : number +} + entity "Consumption" as consumptions { id : number << generated >> -- - item_id : number <<FK>> - patient_id : number <<FK>> consumed_at : datetime quantity : integer total_cost : decimal @@ -97,8 +100,6 @@ entity "Treatment" as treatments { -- number : number name : text - patient_id : number <<FK>> - physician_id : number <<FK>> occurred_at : datetime results : text } @@ -106,7 +107,6 @@ entity "Treatment" as treatments { entity "Visit" as visits { id : number << generated >> -- - patient_id : number <<FK>> comments : text scheduled_at : datetime } @@ -118,6 +118,11 @@ entity "Volunteer" as volunteers { } ' relationships +' Zero or One |o-- +' Exactly One ||-- +' Zero or Many }o-- +' One or Many }|-- + beds ||--o| patients beds }|--|| care_centres consumptions }|--|| items @@ -126,4 +131,17 @@ patients }|--|| physicians treatments }|--|| patients treatments }|--|| physicians visits }|--|| patients +care_centres ||--|| nurses +care_centres ||--|{ timesheets +employees ||--o{ timesheets +laboratories ||--|{ technicians + +employees <|-- nurses +employees <|-- physicians +employees <|-- staff +employees <|-- technicians +people <|-- employees +people <|-- volunteers +people <|-- patients + @enduml |
