ITC556 Database Systems Assessment: ER Diagram and Assumptions

Verified

Added on  2025/04/28

|5
|246
|459
AI Summary
Desklib provides past papers and solved assignments for students. This project focuses on ER diagrams and database design.
Document Page
ITC556 - DATABASE SYSTEMS ASSESSMENT
ITEM 2
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Table of Contents
Assumptions....................................................................................................................................3
ER Diagram.....................................................................................................................................4
References........................................................................................................................................5
2
Document Page
Assumptions
There are few assumptions that are considered while creating the ER diagram and these
assumptions are discussed thoroughly here:
Total numbers of entities that are created are Seven and are connected and dependent on
each other.
For every entity, there are different constraints added like primary and foreign keys.
The table BOOKING_TREATMENT created in order to avoid the many-to-many
relationship between the table appointment and treatment (Dunn,et al., (2017)).
The table appointment connected with a one-to-one relationship with table recorded_data.
The primary key is used to uniquely identify any data in entity Client ClientID is the
primary key for every client, Rec_ID and CA_ID in table Recorded_Data making it
composite, T_ID for a therapist, Payment_ID for Payments, CT_CODE for treatment and
CA_ID for appointments. All these are primary keys.
Another constraint is a foreign key in Booking_treatment table, payment and appointment
tables. All these foreign keys are assigned as primary keys in another table so as a foreign
key they are taking reference from other tables.
There is a one-to-one relationship among the table recorded_data and the appointment as
for booked appointment only one data can be recorded (Harahap, (2019)).
3
Document Page
ER Diagram
Figure 1 ERD
4
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
References
Harahap, S. H. (2019). ANALISIS PEMBELAJARAN SISTEM AKUNTANSI
MENGGUNAKAN DRAW. IO SEBAGAI PERANCANGAN DIAGRAM ALIR.
Dunn, C., & Nel, L. D. (2017). Entity Relationship Diagram Mapping.
5
chevron_up_icon
1 out of 5
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]