Start work on next section of project

2 files changed, 22 insertions, 9 deletions

diff --git a/assignments/final/README.md b/assignments/final/README.md
index c45071a..0da0d82 100644
--- a/assignments/final/README.md
+++ b/assignments/final/README.md
@@ -125,13 +125,28 @@ requiring an associated outpatient owner entity.
 
 Use the relational schema of the EER diagram you developed in Module 1 to answer the following questions.
 
-    Should the RVH use normalization when designing its database? (3 marks)
-    Why are entity integrity and referential integrity constraints of importance to the hospital? (3 marks)
-    Map the EER diagram to a relational schema, and transform the relation into 3NF. (10 marks)
-    Besides the 3NF relations, what additional types of information are required to create a physical database design? (3 marks)
-    Are there opportunities for horizontal or vertical partitioning of the database? Are there other opportunities to denormalize the relations of this database? If no, explain why? If yes, how might you denormalize the database? (3 marks)
-    Suppose the date treatment performed was not entered. What procedures are required to handle the missing data? (3 marks)
-    Consider the following query against the RVH database.
+**Should the RVH use normalization when designing its database?**
+
+Yes, minimizing duplication will make it easier to keep changes synchronized.
+At the moment there is no identified need to de-normalize the database.
+
+**Why are entity integrity and referential integrity constraints of importance to the hospital?**
+
+It's possible that people will need to change their address or phone number. By ensuring that
+the proper referential integrity constraints in place we make it easier to update records and
+limit the risk of creating orphaned records. This helps to keep out single source of truth
+organized, which makes it easier for scheduling personell and ensuring that patients receive the
+care that they need.
+
+**Map the EER diagram to a relational schema, and transform the relation into 3NF**
+
+**Besides the 3NF relations, what additional types of information are required to create a physical database design? (3 marks)**
+
+**Are there opportunities for horizontal or vertical partitioning of the database? Are there other opportunities to denormalize the relations of this database? If no, explain why? If yes, how might you denormalize the database? (3 marks)**
+
+**Suppose the date treatment performed was not entered. What procedures are required to handle the missing data? (3 marks)**
+
+**Consider the following query against the RVH database.**
 
 For each treatment performed in the past two weeks, list the physicians performing the treatment (grouped by treatment), and the number of times this physician performed that particular treatment, on that particular day. Order the list by treatment ID, and by reverse chronological order for each treatment ID.
 
diff --git a/assignments/final/module-1.puml b/assignments/final/module-1.puml
index a9f0690..51aa6c1 100644
--- a/assignments/final/module-1.puml
+++ b/assignments/final/module-1.puml
@@ -57,8 +57,6 @@ entity "Nurse" as nurses {
 
 entity "Patient" as patients {
   contacted_at : datetime
-  referred_by_physician_id : number <<FK>>
-  physician_id : number <<FK>>
 }
 
 entity "People" as people {