Regarding the table, it should be like what we had for the first workshop. We need to have a row for each patient, not a different table. UML must be like the ones we have in quizzes. There are 2 cardinalities between 2 entities. You only defined one. Classparticipant entity is a weak entity, so it should be in the middle and there should have been 4 cardinalities for this UML. Data test, you need to add some test records and check if your UML worked. You put only one record that already existed.
 

Transcribed Image Text:

Patient PatientID [PK] 1...0...* 12:2entName PatientSurname DOB Address Appointment AppointmentID[PK] PatientID [FK 5G (83) Physiotherapist Date Time Duration Patient PatientID 987 FirstName Sam LastName Huynh DOB Address 01/01/1890 123 Name Street, VIC Appointment AppoinementID PatientID 654 - 987 Physio Bruno Date Time Duration Monday 17 April 2023 9am 30 Minutes The Patient entity have a unique ID which is our Primary Key, it includes all the patient's details of their full name, DOB, address etc The Appointment Entity allow us to schedule an appointment with a physio, each appointment has a unique identifier (Primary Key) with a link to a Patient as a foreign key With this, a patient can have multiple appointments and each appointment is created specified for that patient. Workshop 4 Part 1: Class ClassID [PK] Instructor/Physio Patient PatientID [PK] ** PatientName PatientSurname [FK] DOB Address ExerciseType StartTime EndTime * * Class Participant ClassParticipantID [PK] ClassID [FK] PatientID [FK] SWIN BUR ONLINE *NE For Patient, can have multiple classes and each class can have multiple patients. Class Participant allow Patients to have multiple classes and each class can have multiple patients as it is associated with 2 foreign keys the ClassID and PatientID ClassID each class have a unique key where each class can have different type of exercise, e.g. if it's a cardio class we can have ID class of CA001, or swimming class with SW001. Each class to have a duration, which allow patients to have multiple classes. Part 2: Patient PatientID 987 FirstName Sam 2 of 3 LastName Huynh DOB 01/01/1890 Address 123 Name Street, VIC Patient PatientID [PK] 1...0...* 12:2entName PatientSurname DOB Address Appointment AppointmentID[PK] PatientID [FK 5G (83) Physiotherapist Date Time Duration Patient PatientID 987 FirstName Sam LastName Huynh DOB Address 01/01/1890 123 Name Street, VIC Appointment AppoinementID PatientID 654 - 987 Physio Bruno Date Time Duration Monday 17 April 2023 9am 30 Minutes The Patient entity have a unique ID which is our Primary Key, it includes all the patient's details of their full name, DOB, address etc The Appointment Entity allow us to schedule an appointment with a physio, each appointment has a unique identifier (Primary Key) with a link to a Patient as a foreign key With this, a patient can have multiple appointments and each appointment is created specified for that patient. Workshop 4 Part 1: Class ClassID [PK] Instructor/Physio Patient PatientID [PK] ** PatientName PatientSurname [FK] DOB Address ExerciseType StartTime EndTime * * Class Participant ClassParticipantID [PK] ClassID [FK] PatientID [FK] SWIN BUR ONLINE *NE For Patient, can have multiple classes and each class can have multiple patients. Class Participant allow Patients to have multiple classes and each class can have multiple patients as it is associated with 2 foreign keys the ClassID and PatientID ClassID each class have a unique key where each class can have different type of exercise, e.g. if it's a cardio class we can have ID class of CA001, or swimming class with SW001. Each class to have a duration, which allow patients to have multiple classes. Part 2: Patient PatientID 987 FirstName Sam 2 of 3 LastName Huynh DOB 01/01/1890 Address 123 Name Street, VIC