DATABASE DESIGN CAR SERVICE CENTRE

Car Service System
Assignment
Designed by Lim Yao Cheng

P1 Explain the features of a relational
database

What is Entity?
• An object in a system that store information.
• Usually recognizable concepts, either concrete or abstract, such as
person, places, events.
• Example: student, restaurant, course

What is Attribute?
• Characteristic of an entity or view object.
• Correspond to a database column or independent of a column.

Entities for PERODUA Car Service Centre
• peroOwner
• peroCar
• loginDetail
• peroService
• peroAppointment

Attributes for Perodua Car Service
• ownerID(PK)
• ownerName
• address
• contactNo
• dateOfBirth
• email
• password
• grantLevel
• peroCarID(PK)
• peroCarModel
• peroYear
• peroColor
• peroTransmission
• peroFuelType
• peroMileage
• peroEnginePower
• peroEngineType
• peroCarNo
• peroRegNo
peroOwner peroCar

• loginID(PK)
• loginName
• loginDateTime
• ownerID(FK)
• peroServiceID(PK)
• peroServiceName
• peroServiceType
• peroServiceFees
loginDetail peroAppointment
• peroAppID(PK)
• peroAppDateTime
• peroEmployee
• peroAppStatus
peroService
Attributes for Perodua Car Service

List the tables which will be created

Tables
1. peroOwner
2. peroCar
3. peroCarOwner
4. loginDetail
5. peroService
6. peroAppointment
7. peroCarAppointment
8. peroCarService

How the tables in the scenario are related to each
other using primary and foreign keys

Relationship Between Tables
Table Cardinality Primary Key Foreign Key Assumption
peroOwner - ownerID
peroCar - peroCarID
peroCarOwner - peroCarID+ownerID PeroCarID
ownerID
peroCar and
peroCarOwner
One to One One car is belonged
to only one owner
peroOwner and
peroCarOwner
One to Many One owner may
have one or many
car owners

loginDetail - loginID ownerID
peroOwner and
Account
One to Many One owner may
login one or many
times
account and
peroOwner
One to One One account has
only one owner

peroService - peroServiceID
peroCarService peroAppID+peroSer
viceID
peroAppID
peroServiceID
peroService and
peroCarService
One to Many One service may
have one or many
appointments
peroCarService and
peroservice
One to One One appointment is
related with only
one service

peroAppointment - peroAppID
peroCarAppointment peroAppID+PeroCarID PeroAppID
PeroCarID
peroCar and
peroAppointment
One to Many One car may be
able to make one
or many
appointments
peroAppointment
and peroCar
One to One One appointment
is related with only
one car

Explain referential integrity using an example from
the above scenario

Entity Relationship with reasoning Attributes Constraints
peroCar 1:M(One car may schedule one or many
appointments). If a car is accidently crashed and it
is removed from appointment table, the associated
car and appointment records will be automatically
deleted from perocarappointment table by enforcing
cascade delete option of referential integerity
peroCarID(PK)
peroCarModel
peroYear
peroColor
peroTransmission
peroFuelType
peroMileage
peroEnginePower
peroEngineType
peroCarNo
peroRegNo
peroCarID(PK)
appoint (R) M:1 peroAppID
peroCarID
Composite Primary Key
peroAppoinment 1:1(One appointment must be related with only one
car) If an appointment has been cancelled in
peroappointment table, the corresponding car and
appointment records from perocarappointment table
will be automatically removed
peroAppID(PK)
peroAppDateTime
peroEmployee
peroAppStatus
peroAppID(PK)
Referential Integrity

P2 Design a relational database for a
specified user need

Plan the tables
• peroOwner
• PeroCar
• peroCarOwner
• loginDetail
• peroService
• peroAppointment
• peroCarService
• peroCarAppointment

Plan the Columns
• peroCarID(PK)
• peroModel
• peroYear
• peroColor
• peroTransmission
• peroFuelType
• peroMileage
• peroEnginePower
• peroEngineType
• peroCarNo
• peroRegNo
peroCar
• peroCarID
• ownerID
peroCarOwne
r Composite
PrimaryKey
• ownerID(PK)
• ownerName
• address
• contactNo
• dateOfBirth
• email
• password
• grantLevel
peroOwner

Plan the Columns
• loginID(PK)
• loginName
• loginDateTime
• ownerID(FK)
loginDetail peroAppointment
• peroAppID(PK)
• peroAppDateTime
• peroEmployee
• peroAppStatus
• peroServiceID(PK)
• perServiceName
• peroServiceType
• peroServicFees
peroService

Plan the Columns
• peroAppID
• peroServiceID
CarService
• peroAppID
• peroCarID
CarAppointment
Composite
PrimaryKey
Composite
PrimaryKey

M1 Explain referential integrity and the purpose
of primary keys in building the relationships
between tables

Purpose of Primary Key
Table Primary Key Purpose of P.K Foreign Key Purpose of F.K
perowner ownerID To uniquely identify
each owner record
perocar peroCarID To implement data
integrity
perocarowner (peroCarID+
ownerID) Composite
Key
To implement a
relationship between 2
tables (owner & percar)
in a relational database
peroCarID
ownerID
Referential Integrity is
not allowed to enter a
record in foreign key
table(peroowner) if that
record is not included in
primary key table(owner,
peroCar)
…..To Continue NEXT SLIDE

logindetail loginID Ensure row-level
accessibility
ownerID If the user attempts to
enter a record in the
logindetail table using
an ownerID that is not
found in the owner
table, the database will
reject that entry and
display a warning
message
peroservice peroServiceID To uniquely identify
each owner record
…..To Continue NEXT SLIDE

peroappointment peroAppID To implement data
integrity among the
appointment records
perocarservice (peroAppID+
peroServiceID)
Composite Key
Combination of columns
is selected to guarantee
that two services never
have the same
appointment unique
value
peroAppID
peroServiceID
Due to the properties of
referential integrity, all
records have ACID
properties like Atomicity,
Consistency, Isolation
and Durability
perocarappointment (peroAppID+
peroCarID) Composite
Key
Combination of columns
is selected to guarantee
that two cars never have
the same appointment
unique value
peroAppID
peroCarID
The enforce referential
integrity among the
tables, cascade delete
cascade update option
are provided for foreign
key tables

Explain how you can create primary key in a
table using script or phpMyAdmin for the above
scenario

P3 Create and populate a database

Create required tables & their
relationship using PHPMyAdmin

Establish the relationships and referential
integrity between the tables

Relationship among perowwner, perocar,
perocarowner Tables

Relationship between peroowner and
logindetail Tables

Relationship among perocar,
peroappointment and perocarappointment

Relationship among peroservice,
peroappointment and percarservice

Relationship Diagram for Perodua Car Service
Centre

Insert data to each of the table created

Insert Data Script into peroonwer Table

Insert Data Result into peroonwer Table

Insert Data Script into perocar Table

Insert Data Result into perocar Table

Insert Data Result into perocarowner Table

Insert Data Script into logindetail Table

Insert Data Result into logindetail Table

Insert Data Script into peroservice Table

Insert Data Result into peroserevice Table

Insert Data Script into peroappointment Table

Insert Data Result into peroappointment
Table

Insert Data Script into perocarappointment
Table

Insert Data Result into perocarappointment
Table

Insert Data Script into peroCarService Table

Insert Data Result into perocarservice Table

M2 Import data from an
external source

peroowner after import CSV File

perocarowner after import CSV File

logindetail after import CSV File

peroervice after import CSV File

peroappointment after import CSV File

perocarservice after import CSV File

perocarappointment after import CSV File

M3 Export data from an
external source

Insert Data into peroowner Table

Export CSV from peroowner Table

P5 Perform queries using
multiple tables and multiple
criteria

Display all owners and car information

Display all owners and car information for a
particular car number

Find and display Owner, Car & Service
Appointments for a particular Owner
based on owner email and for service
appointment within the next 1 month

P6 Include an advanced feature in a
database design

Create 3 indexes to speed up data retrieval

Create a field Called Created On all Tables

M4 Implement an Automated Function

Code for Backup-ing perocarservice data

Code for the Time to Launch a Backup App

Code for the Time to Launch Ampps

No Test Objective Test Case Expected Result Actual
Result
Pass/Fail
1 Include test to ensure
referential integrity
If the user attempts to enter a
record in the logindetail table
using ownerID that is not
found in the table
The database will reject that entry
and display warning message
Successful Pass
If a car record is deleted from
car table
The associated peroCarID,ownerID,
peroAppID and peroCarID will
automatically be removed from
perocarowner table and
perocarappointment table
respectively.
2 Include test to ensure
default field
Set “CURRENT_TIMESTAMP” as
default for createdOn field in
perocar table
Successful Pass

No Test Objective Test Case Expected Result Actual Result Pass/Fail
To ensure auto
generated fields are
working as expected
Set peroCarID as
AUTO_INCREMENT services
table
Successful Pass
3 To ensure field sizes
meets requirements
If I enter peroColor field over
15 characters
If I enter contactNo field over
20 characters
That peroColor data is not
allowed to save into the database
That contactNo is not allowed to
save into the database
Successful
Successful
Pass
Pass

No Test Objective Test Case Expected Result Actual
Result
Pass/Fail
4 Null values are
handled for non-
mandatory fields
If I leave as blank for non-
mandatory fields in owner
register form
Successful Pass

P4 Create features in data entry forms to
ensure validity and integrity of data

The owner registration form should have
information about owner along with 1 car
information

The form should display a thank you page after
registration

This form can save (perocar, perowner,
and perocarowner) table

The form should have all the fields mandatory
for an owner and his 1st car.

The form should ensure the data size do not
exceed the field size in the database

If phone field exceed the field size, that
related data is not entered into the database

If car number field exceed the field size, that
related data is not entered into the database

If a a car is accidentally crashed, the related
owner and car information are automatically
removed from database

D2 evaluate a database against
specified user need

No Requirement Query Used Database Meets
Requirements
(YES/NO)
Comments
1 Users able to register
themselves
Users able to register
themselves
Yes Figure 1
Yes Figure 2
Yes Figure 3

Requirements
(YES/NO)
Comments
2 Users are able to login to the
portal
Yes Figure 4
3 Users are able to register their
cars
Yes Figure 5 & 6

Requirements
(YES/NO)
Comments
4 Users are able to Add Cars Yes
Figure 5 & 6
Users are able to Delete Cars Yes Figure 7 & 8

Requirements
(YES/NO)
Comments
5 Users are able to book for
appointment
Yes Figure 9, 10 & 11

Requirements
(YES/NO)
Comments
5 Delete existing, unexpired
appointment for their car
servicing
Yes Figure 12 & 13

Figure 12 & 13
Before Deleting After Deleting

Requirements
(YES/NO)
Comments
6 To count car quantity
based on owner ID
Yes Figure 14
To count number of
appointment times based
on carID
Yes Figure 15

Requirements
(YES/NO)
Comments
6 To count number of
appointment based on
serviceID
Yes Figure 16

D1 Discuss how potential errors in the design
and construction of a database can be
avoided

UNF (Un-normalized Form)
ownerID, ownerName, address, contactNo, dateOfBirth, email,
peroCarID, peroCarModel, peroYear, peroColor, peroTransmission,
peroaMileage, peroEnginePower, peroEngineType, peroCarNo,
peroRegNo, loginID, loginName, password, grantLevel, peroServiceID,
peroServiceName, peroServiceType, peroServiceFees, peroAppID,
peroAppDateTime, peroEmployee, peroAppStatus

FNF (Remove any duplicate attributes to a new
table and a composite key is created)
• Owner (ownerID, ownerName, address, contactNo, dateOfBirth, IC,
email)
• carAppointment(ownerID, peroCarID, loginID, peroServiceID,
peroAppID, peroCarModel, peroYear, peroColor, peroTransmission,
peroMileage, peroEnginePower, peroEngineType, peroCarNo,
peroRegNo, loginName, password, grantLevel, serviceName,
serviceType, serviceFees, appDate, appTime, employee, appStatus)

SNF (Assure that no non-key attributes are
dependent on any candidate keys)
• Owner (ownerID, ownerName, address, contactNo, dateOfBirth, IC,
email, password, grantLevel)
• Car(peroCarID, peroCarModel, peroYear, peroColor, peroTransmission,
peroFuelType, peroMileage, peroEnginePower, peroEngineType,
peroCarNo, peroRegNo, ownerID)
• Service(peroServiceID, peroServiceName, peroServiceType,
peroServiceFees)
• loginDetail(loginID, loginName, loginDateTime, ownerID)
• Appointment(perocarID, peroServiceID, peroAppDateTime,
peroEmployee, peroAppStatus)

TNF (Eliminate any column reference in reference data that
are not dependent on the primary key. Only foreign key
columns should be used to referenced another table, and no
other columns from the parent table should exist in the
referenced table)

• peroowner (ownerID, ownerName, address, contactNo, dateOfBirth, IC, email, password,
grantLevel)
• perocarowner(ownerID, peroCarID)
• perocar(peroCarID, peroCarModel, peroYear, peroColor, peroTransmission, peroFuelType,
peroMileage, peroEnginePower, peroEngineType, peroCarNo, peroRegNo)
• peroservice(peroServiceID, peroServiceName, peroServiceType, peroServiceFe)
• logindetail(loginID, loginName, loginDateTime, ownerID)
• peroappointment(peroAppID, peroAppDateTime, peroEmployee, peroAppStatus)
• perocarappointment(peroCarID, peroappID)
• perocarservice(peroAppID, peroServiceID)

POTENTIAL ERRORS IN THE
DESIGN AND CONSTRUCTION
OF DATABASE THAT CAN BE
AVOIDED

1) Accidental deletion of fields
• When a database is in use, you may find it really easy to accidently delete data which
could mean allot of stress.
• One main way to AVOID this would be to make sure that back-ups are made of the data,
so whatever the matter the data will not be completely lost. However, it is very annoying
when data becomes deleted because it takes allot of time and effort to retype the data.
• The best way to stop accidental deletion is to set the database to only the designer can
manipulate it, so anyone using the database without authorisation cannot manipulate
and is only able to read the database with no risk of deletion.

2) Incorrect data types
• Incorrect data type issues can occurs when an unmatched data type is used.
• An example would be, a field called ‘fees’ in a table in a database, it will go wrong if a
‘text value’ is inserted instead of a ‘numerical value’ like ‘two hundred’ instead of ‘200’.
• This can be avoided as you can tell the database to only allow numerical values to be
inputted within that field so this error won’t occur again. The database won’t allow
anything inputted other than numbers.

3) Renaming Incorrectly
• Renaming something or someone incorrectly on a database can be a huge mistake,
hugely if it were to happen to be a bank.
• This is mostly done by human error as a typo or misheard information.
• This means if the error isn’t spotted then it will not be sorted out; so a way to sort out
the problem is by double checking the information given and typed.

4) Validation
• Validation within computers is on par with people verification checks, but checks the data to see if the data
entered is sensible and reasonable.
• When a user puts information in to a database which might not be right then the computer will do
validation checks to see a match between the users input and information given to the database to run
though a list of checks.
• Example: The database is given a set of rules to run by which would be >=18 which means that nothing
under the number (age) is allow to carry on to the next step. So if someone that is the age of 17 or under
will not be allowed to move forward. So as you can see this helps to validate information allowing and
disallowing data which helps to organise the database making sure all the data is correct.

5) Null Values
• The meaning of a null value equals to “nothing there” within a database.
• This would be a big problem with the database as the database will not be able to work properly
as it doesn’t understand what it is told and might cause other errors within the database.
• If the data base has not been set to understand the null values it would carry on to the next step,
but to prevent this from happening you can the use of a validation rule. The validation rule will
work to stop the null value from happening like in an ‘online application form’ where if no value
were to be entered then a user wouldn’t be able to carry on to the next step; the validation rule
will work in the same way to stop the null value from arising and missing values from happening.

DATABASE DESIGN CAR SERVICE CENTRE

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to DATABASE DESIGN CAR SERVICE CENTRE

Similar to DATABASE DESIGN CAR SERVICE CENTRE (20)

Recently uploaded

Recently uploaded (20)

DATABASE DESIGN CAR SERVICE CENTRE