Kelvin WAHOME

Dan MBUGUA

• Health : Doctor-patient appointments management

• Relations Derived : Doctors

Patients

Appointments

• Three physical sites on three different O/S platforms (Windows 10, MacOS, Ubuntu 14.04)

• Three different DBMS:• SQL SERVER – Running on Windows 10

• PostgreSQL – Running on MacOS

• MySQL – Running on Ubuntu 14.04

• Patients RelationNot fragmented

Stored at site 1

• Doctors RelationFragmented vertically to derive two fragments:

• doctors_personal_details stored at Site 1

• doctors_official_details – Further fragmented along its tuples to derive two fragments (horizontal fragmentation): doctors_official_details for doctor’s whose specialization is listed as General Practitioner -

stored at Site 2

doctors_official_details for doctor’s whose specialization is not General Practitioner – stored at Site 3

• Appointment’s RelationFragmented using derived horizontal fragmentation:

• Appointment_details in which the participating doctor has their specialization listed as General Practitioner - stored at Site 2

• Appointment_details in which the participating doctor is not listed as a General Practitioner - stored at Site 3

doctors_personal_details patients_personal_details

doctors_official_details appointments

doctors_official_details appointments

• Doctors relation Reconstructing doctor’s personal details and official details using the shared

attribute doctor_id

• Appointments relation Reconstructing doctor’s personal details and official details using the shared

attribute doctor_id