ITC556 Database Systems Assessment Item 2: ER Diagram for OP Clinic
VerifiedAdded on 2025/04/27
|5
|267
|302
AI Summary
Desklib provides past papers and solved assignments for students. This is a solved assignment for database design.

ITC556 - DATABASE SYSTEMS
ASSESSMENT ITEM 2
ASSESSMENT ITEM 2
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Contents
Assumptions..............................................................................................................................5
ER Diagram..............................................................................................................................5
References.................................................................................................................................7
Table of Figures
Figure 1: ER Diagram.............................................................................................................5
2
Assumptions..............................................................................................................................5
ER Diagram..............................................................................................................................5
References.................................................................................................................................7
Table of Figures
Figure 1: ER Diagram.............................................................................................................5
2

Assumptions
Clients entity has a Primary Key named as Cl_ID.
Clients entity makes one to many relationship with Bookings and Cl_ID acts as a
Foreign Key in Bookings entity.
Bookings entity has a Primary Key named as Bo_ID.
Bookings entity makes a one to many relationship with Paid Entity and Paid contains
Bo_ID as a Foreign Key.
Treaments has a TRT_Code that is made as a Primary Key and it makes one to many
relationship with Bookings.
Bookings also make one to many relationship with Appointments and Appointmetns
contains THP_ID, BO_ID as Foreign Keys.
Only one to one relationship exists that is between Appointments and RecordOfData
entity (Grau, J., & Miles, J. 2017).
Therapist entity also contains THP_ID as a Primary Key.
The ER diagram made below is based on OP Clinic.
3
Clients entity has a Primary Key named as Cl_ID.
Clients entity makes one to many relationship with Bookings and Cl_ID acts as a
Foreign Key in Bookings entity.
Bookings entity has a Primary Key named as Bo_ID.
Bookings entity makes a one to many relationship with Paid Entity and Paid contains
Bo_ID as a Foreign Key.
Treaments has a TRT_Code that is made as a Primary Key and it makes one to many
relationship with Bookings.
Bookings also make one to many relationship with Appointments and Appointmetns
contains THP_ID, BO_ID as Foreign Keys.
Only one to one relationship exists that is between Appointments and RecordOfData
entity (Grau, J., & Miles, J. 2017).
Therapist entity also contains THP_ID as a Primary Key.
The ER diagram made below is based on OP Clinic.
3
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

ER Diagram
Figure 1: ER Diagram
The Diagram shown above is made on draw.io. The ERD made contains seven entities
explained properly and assigned with Primary key attribute as well as the Foreign Keys
wherever required (Steinau et al., 2017). Relationships are also shown properly in order to
make the diagram more informative and knowledgeable.
4
Figure 1: ER Diagram
The Diagram shown above is made on draw.io. The ERD made contains seven entities
explained properly and assigned with Primary key attribute as well as the Foreign Keys
wherever required (Steinau et al., 2017). Relationships are also shown properly in order to
make the diagram more informative and knowledgeable.
4
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

References
Steinau, S., Künzle, V., Andrews, K., & Reichert, M. (2017, July). Coordinating business
processes using semantic relationships. In 2017 IEEE 19th Conference on Business
Informatics (CBI) (Vol. 1, pp. 33-42). IEEE.
Grau, J., & Miles, J. (2017). U.S. Patent No. 9,575,208. Washington, DC: U.S. Patent and
Trademark Office.
5
Steinau, S., Künzle, V., Andrews, K., & Reichert, M. (2017, July). Coordinating business
processes using semantic relationships. In 2017 IEEE 19th Conference on Business
Informatics (CBI) (Vol. 1, pp. 33-42). IEEE.
Grau, J., & Miles, J. (2017). U.S. Patent No. 9,575,208. Washington, DC: U.S. Patent and
Trademark Office.
5
1 out of 5
Related Documents

Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
Copyright © 2020–2025 A2Z Services. All Rights Reserved. Developed and managed by ZUCOL.