Q1: Design an ER diagram for the following Dental Clinic database.

Your diagram should have all the

needed details. You may make any reasonable assumptions but you have to state them clearly.
The clinic has several dentists. Each dentist has a unique Number, name, nationality, multiple
roomnumber, salary, birth-date and home-address (Box, City, Zip).
Each client (patient) has a unique Code, name, home-phone, work-phone, address, and birth-date. Each
client is assigned to one dentist. All future visits will be to the same dentist. A client can be insured or
self-paying. An insured client should have an insurance company-name, and company-Phone, while a
self-paying client must have a bank-name and a bank account.
Each visit of a client is described by a date, type, action, fee, and date-of-next-appointment
1. Design an Entity Relationship (ER) Model to represent the above requirements.

Assumptions:

1. Insurance company insures zero or more patients

2. A bank account belongs to exactly one patient

2. Convert an ER Diagram that presented in part (A) to Relational Schema.

Dentist (dentist_unique_number, name, nationality, salary, birth_date, city, zip,
address_box);

Dentist_Rooms (dentist_unique_number, room_number);

Patient (patient_unique_code, name. homephone, workphone, address, birth_date,

insurance_company_ identifier, bank_identifier);

Insurance_Company (insurance_company_identifier, name, phone);

Bank (bank_identifier, name, account);

This study source was downloaded by 100000845597213 from CourseHero.com on 04-22-2022 14:14:02 GMT -05:00

https://www.coursehero.com/file/13919522/IT244-Assignment-2/
 Patient_Visits (patient_unique_code, dentist_unique_number, date, type, action, fee,
next_appointment_date);

This study source was downloaded by 100000845597213 from CourseHero.com on 04-22-2022 14:14:02 GMT -05:00

https://www.coursehero.com/file/13919522/IT244-Assignment-2/
 Q2.
a) Explain the distinction between condition-defined and user-defined constraints. Which of these
constraints can the system check automatically?
Answer: In a condition defined design constraint, membership in the lower level entity-sets is evaluated on the basis of whether
or not an entity satisfies an explicitly stated condition.

In user-defined constraints, membership is not constrained by any condition; instead, entities are assigned to a given entity set by
the database user.

Condition-defined constraints alone can be automatically handled by the system. Whenever any tuple is inserted into the
database, its membership in the various lower level entity-sets can be automatically decided by evaluating the respective
membership conditions. Similarly when a tuple is updated, its membership in the various entity sets can be re-evaluated
automatically.

b) Explain the distinction between disjoint and overlapping constraints. (1 Point)

In a disjoint design constraint, an entity can belong to not more than one lower-level entity set. In overlapping generalizations,
the same entity may belong to more than one lower-level entity sets.

c) Explain the distinction between total and partial constraints.

In a total design constraint, each higher-level entity must belong to a lower-level entity set. The same need not be true in a partial
design constraint. For instance, some employees may belong to no work-team while a manager must be an employee.

This study source was downloaded by 100000845597213 from CourseHero.com on 04-22-2022 14:14:02 GMT -05:00

https://www.coursehero.com/file/13919522/IT244-Assignment-2/
Powered by TCPDF (www.tcpdf.org)