INTRODUCTION TO RELATIONAL

DATABASE AND SQL

CARER DATABASE SCHEDULING SYSTEM

Submitted by: Ademola Kazeem

Student No: 15200214

Due: 14th April, 2016

Project Idea
Carer Database Scheduling System is a project that allows Carer to specify their availability
for job scheduling. Each carer is assigned to clients based on the carers' availability by an
administrator who is the manager of a Homecare Company. The carers can also schedule
their holidays and admin can either grant or deny the holiday for any holiday requests by any
carer. The admin can send email to all carers about possible covers for other carers and the
covers are assigned to each carer based on which carer respond to the mails first.

The carers are allowed to accept or reject the assignment based on the information about
the clients, their availability etc. and others who are available for extra work could be
allowed to cover for any rejection by any carer.
Business Rules

Carer is an employee of the company that takes care of the companys Clients.
Each Carer has manager and 1 manager can manage more than one Carers.
The Carer specifies his/her availability in the system, which in our case is a many-tomany relationship, so it was divided into 2 called Carer_Availability.
The Manager assigns Carer to different Clients by setting up a roster (called Visit in the
diagram)
A Carer can book many holidays in a year, based on the acceptance or rejection of the
Manager and number of holiday days the Carer is allowed by the Company.
The manager can either grant or deny holiday request by the Carer.
Once a Carer is on holiday, there is need for cover.
A Cover is also a Carer, except that he/she would be covering for someone on holiday.
The Manager sends out an email informing other employees (Carers) if they are
interested in covering for the person that is on holiday.
The Manager assigns cover based on the first person to respond to the email.
A manager assigns visits, and a Carer can visit many Clients while 1 Clients can be
visited by many Carer.
A Carer can visit many times within a period.
A period is a range of days that a Carer is scheduled to visit some specific Clients, the
range of time could be 3 weeks range.
Clients have comments, apart from their names, address etc.
These Comments may include medication, personal care, Grooming/Dressing, Client
safety, house work, and other information needed by the Carer to take care of the
Client.

Entities in the Database

1. Manager(adminId, username, password, firstname, lastname, DateOfBirth,
securityLevel, email, dateCreated, dateUpdated)
2. Carer(carerId, username, password, firstname, lastname, sex, address, county, phone,
ppsNumber, adminNote, userStatus, DateOfBirth, email, dateCreated, dateUpdated)

3. Client(clientId, firstname, lastname, sex, address, county, phone, DateOfBirth,

commentId)
4. Comment(commentId, dressing, communication, housework, medication, safety,
nutrition)
5. Availability (availabilityId, dayOfTheWeek, time)
6. Period(periodId, fromdate, todate, fromtime, totime, duration)
7. Holiday(carerId,
adminId,
date,
numberOfDays,
numberOfDaysAllowed,
numberOfDaysTaken, status, date)
8. Visit (Carer_Client)(carerId, clientId, periodId, adminId)
9. Email(emailId, from, to, subject, message)
10. Cover(carerId, coverCarerId, visitId)
11. Carer_Availability (carerId, availabilityId)

1 to Many Relationship
1 Manager Grants Many Holidays
1 Manager sends many emails
1 Manager assigns cover
1 Carer has many holidays

Many to Many Relationship

Many carers has many availabilities (Carer_availabilities)
Many carers visit many Clients

1 to 1 Relationship
1 Manager assigns 1 Cover
1 Client has 1 Comment