16acb01873 Fyp

ONLINE CAR MECHANIC SHOP SYSTEM
BY
WONG SAI KIT
A REPORT
SUBMITTED TO
Universiti Tunku Abdul Rahman
in partial fulfillment of the requirements
for the degree of
BACHELOR OF INFORMATION SYSTEMS (HONS)
INFORMATION SYSTEMS ENGINEERING
Faculty of Information and Communication Technology
(Kampar Campus)
JAN 2020
UNIVERSITI TUNKU ABDUL RAHMAN
REPORT STATUS DECLARATION FORM
Title: ONLINE CAR MECHANIC SHOP SYSTEM
Academic Session: JAN 2020
I WONG SAI KIT

(CAPITAL LETTER)
declare that I allow this Final Year Project Report to be kept in

Universiti Tunku Abdul Rahman Library subject to the regulations as follows:
1. The dissertation is a property of the Library.
2. The Library is allowed to make copies of this dissertation for academic purposes.
Verified by,
_________________________ _________________________
(Author’s signature) (Supervisor’s signature)
Address:
10A, PRSN SENGAT BARU 37, DR. MANORANJITHAM A/P
TMN BERSATU, SIMPANG MUNIANDY
PULAI, 31300 IPOH, PERAK Supervisor’s name
Date: 23 APRIL 2020 Date: 24 APRIL 2020

TITLE PAGE
ONLINE CAR MECHANIC SHOP SYSTEM

BY
WONG SAI KIT
A REPORT
SUBMITTED TO
in partial fulfillment of the requirements
for the degree of
BACHELOR OF INFORMATION SYSTEMS (HONS)
INFORMATION SYSTEMS ENGINEERING
Faculty of Information and Communication Technology
(Kampar Campus)
JAN 2020
i
BIS (HONS) Information Systems Engineering
Faculty of Information and Communication Technology (Kampar Campus), UTAR
DECLARATION OF ORIGINALITY
I declare that this report entitled “ONLINE CAR MECHANIC SHOP SYSTEM” is my
own work except as cited in the references. The report has not been accepted for any degree
and is not being submitted concurrently in candidature for any degree or other award.
Signature : _________________________
Name : WONG SAI KIT
Date : 23 APRIL 2020
ii
ACKNOWLEDGEMENTS
First of all, I would like to thank and appreciate for the guidance given by my
supervisor, Dr. Manoranjitham A/P Muniandy throughout the project. Without her help
when I facing any problems, I think I am not able to continue this project.
Next, I must thank my family especially my mother. This is because she is the one
to pull me out when I feel stressed and want to give up. Without the love, support, and
encouragement of my family, I think it is also hard for me to work on and complete this
project.
iii
ABSTRACT
Today, every family must have a car and will send their car for repair or regular
service. However, one of the mechanic shops in Simpang Pulai, Perak, Malaysia named
Pusat Servis Tayar Dan Kereta Maeng Wa still operate their business in a manual way. The
shop only accepts walk-in customers, put service reminder sticker on the car windscreen
to remind customers for next service due, and accept outdoor service requests by customers
through phone calling. As a result, this has affected both car mechanic shop and customers.
Firstly, walk-in customers may leave due to long waiting time and thus the shop lost its
profits. Secondly, customer perform regular car service lately due to faded or dropped
service reminder sticker and thus shop lost its profits again. Thirdly, customers need to
wait longer time of the arrival of the shop for outdoor service due to the shop may not
familiar of the location or the location stated by customers though phone calling is not clear.
Therefore, this final year project aims to deliver an online system for the shop and its
customers. Front-end mobile applications developed in Android platform and supported by
back-end Amazon Web Service Elastic Compute Cloud (AWS EC2) server will be used
by customers and the clerk of the shop. Ultimately, the main solutions provided by this
system are service booking, service reminder, and car breakdown assistant.
iv
TABLE OF CONTENTS
TITLE PAGE .................................................................................................................................. i
DECLARATION OF ORIGINALITY ........................................................................................ ii
ACKNOWLEDGEMENTS ......................................................................................................... iii
ABSTRACT ................................................................................................................................... iv
TABLE OF CONTENTS .............................................................................................................. v
LIST OF FIGURES ...................................................................................................................... ix
LIST OF TABLES .......................................................................................................................xiii
LIST OF ABBREVIATIONS ..................................................................................................... xv
CHAPTER 1 INTRODUCTION.............................................................................................. 1
1.1 Problem Statement............................................................................................................... 1
1.2 Background and Motivation ............................................................................................... 2
1.3 Objectives ............................................................................................................................. 5
1.4 Proposed Approach / Study ................................................................................................ 6
1.5 Highlight of What Have Been Achieved ............................................................................ 7
1.6 Report Organization ............................................................................................................ 8
CHAPTER 2 LITERATURE REVIEW.................................................................................. 9
2.1 Literature Review on Existing Service Reminder Solutions ............................................ 9
2.1.1 Solution 1 - Built-in Service Reminder Light (Motorist Assurance Program, 2019)
................................................................................................................................................. 9
2.1.2 Solution 1 Real World Application - Honda Built-in Service Reminder System
Codes (Honda Ireland, n.d.) .................................................................................................. 9
2.1.3 Solution 2 - SMS Reminder System (Swift SMS Gateway, 2017) ........................... 10
2.2 Literature Review on Researches about Practices on Capturing Coordinates Data ... 10
2.2.1 Existing Project - GPS-based Location Tracking System via Android Device
(Uddin, Islam & Nadim, 2013) ............................................................................................ 10
2.2.2 GPS (Universal Service Administrative Co., n.d.) ................................................... 12
2.2.3 Web-based Maps and Imagery (Universal Service Administrative Co., n.d.) ....... 12
2.2.4 Address Geocoding (Universal Service Administrative Co., n.d.) .......................... 13
2.3 Data Collection ................................................................................................................... 14
CHAPTER 3 SYSTEM DESIGN ........................................................................................... 16
3.1 Requirements...................................................................................................................... 16
3.2 Block Diagram.................................................................................................................... 17
v
3.3 Use Case Diagram .............................................................................................................. 18
3.4 Use Case Description ......................................................................................................... 19
3.4.1 User Auth Use Case .................................................................................................... 19
3.4.2 Manage Profile Use Case ............................................................................................ 19
3.4.3 Update Car Mileage Value Use Case......................................................................... 20
3.4.4 Make Service Booking Use Case ................................................................................ 20
3.4.5 Request Outdoor Service Use Case ........................................................................... 20
3.4.6 Insert Service Record Use Case ................................................................................. 21
3.4.7 View Booking Requests Use Case .............................................................................. 21
3.4.8 View Outdoor Service Requests Use Case ................................................................ 21
3.4.9 Execution of Scheduled Event Use Case ................................................................... 22
3.5 MySQL Entity Relationship Diagram.............................................................................. 23
3.6 MySQL Data Dictionary ................................................................................................... 24
3.6.1 Table “car” .................................................................................................................. 24
3.6.2 Table “car_service” .................................................................................................... 24
3.6.3 Table “car_service_service_item” ............................................................................. 25
3.6.4 Table “customer_car” ................................................................................................ 26
3.6.5 Table “customer_car_breakdown_service”.............................................................. 27
3.6.6 Table “customer_car_service” ................................................................................... 28
3.6.7 Table “customer_car_service_booking” ................................................................... 29
3.6.8 Table “customer_car_service_booking_requested_service” ................................... 30
3.6.9 Table “password_reset_temp” ................................................................................... 31
3.6.10 Table “service_booking_quota”............................................................................... 31
3.6.11 Table “service_item”................................................................................................. 32
3.6.12 Table “system_inbox” ............................................................................................... 32
3.6.13 Table “system_inbox_intent” ................................................................................... 33
3.6.14 Table “user_data” ..................................................................................................... 34
3.7 User Interface Design in Android Studio ......................................................................... 35
CHAPTER 4 SYSTEM IMPLEMENTATION .................................................................... 36
4.1 SDLC Method Adopted ..................................................................................................... 36
4.2 Implementation Tools ........................................................................................................ 37
4.3 AWS EC2 Instance Configuration ................................................................................... 39
vi
4.4 Linux Crontab Command in AWS EC2 Instance........................................................... 40
4.5 MySQL Table Creation ..................................................................................................... 41
4.5.1 Table “car” .................................................................................................................. 41
4.5.2 Table “car_service” .................................................................................................... 41
4.5.3 Table “car_service_service_item” ............................................................................. 42
4.5.4 Table “customer_car” ................................................................................................ 42
4.5.5 Table “customer_car_breakdown_service”.............................................................. 43
4.5.6 Table “customer_car_service” ................................................................................... 43
4.5.7 Table “customer_car_service_booking” ................................................................... 44
4.5.8 Table “customer_car_service_booking_requested_service” ................................... 44
4.5.9 Table “password_reset_temp” ................................................................................... 45
4.5.10 Table “service_booking_quota”............................................................................... 45
4.5.11 Table “service_item”................................................................................................. 46
4.5.12 Table “system_inbox” ............................................................................................... 46
4.5.13 Table “system_inbox_intent” ................................................................................... 47
4.5.14 Table “user_data” ..................................................................................................... 47
4.6 MySQL Event Creation ..................................................................................................... 48
4.6.1 Scheduled Event to Remove Inbox Message............................................................. 48
4.6.2 Scheduled Event to Reset “isUpdateMileageToday” Flag ...................................... 48
4.6.3 Scheduled Event to Remove Customer Service Booking......................................... 49
4.6.4 Scheduled Event to Auto Reject Breakdown Assistant Request (Sunday) ............ 49
4.6.5 Scheduled Event to Auto Reject Breakdown Assistant Request (Monday) ........... 50
4.6.6 Scheduled Event to Auto Reject Breakdown Assistant Request (Tuesday) .......... 50
4.6.7 Scheduled Event to Auto Reject Breakdown Assistant Request (Wednesday) ..... 51
4.6.8 Scheduled Event to Auto Reject Breakdown Assistant Request (Thursday) ........ 51
4.6.9 Scheduled Event to Auto Reject Breakdown Assistant Request (Friday) ............. 52
4.6.10 Scheduled Event to Auto Reject Breakdown Assistant Request (Saturday) ....... 52
4.7 “Facebook For Developer” Configuration for User Authentication Using Facebook
Account ..................................................................................................................................... 53
4.8 Google APIs Configuration for User Authentication Using Google Account............... 53
4.9 Firebase Configuration for Publishing Notification Using Firebase Cloud Messaging
................................................................................................................................................... 54
4.10 Google APIs Maps SDK for Android Configuration .................................................... 54
vii
4.11 Android Application Development ................................................................................. 55
4.11.1 Splash Screen............................................................................................................. 55
4.11.2 User Authentication Using Email/Password........................................................... 56
4.11.3 User Authentication Using Facebook & Google Account ..................................... 59
4.11.4 Customer Profile Management ................................................................................ 60
4.11.5 Customer Profile Management Special Case for Facebook or Google
Authenticated Users ............................................................................................................. 63
4.11.6 Customer Update Latest Car Mileage..................................................................... 64
4.11.7 Admin Insert Service Record ................................................................................... 65
4.11.8 Book a Service from Service Reminder Listing ..................................................... 69
4.11.9 Service Booking ......................................................................................................... 70
4.11.10 Car Breakdown Assistant ....................................................................................... 73
CHAPTER 5 SYSTEM TESTING ........................................................................................ 77
5.1 Devices Used for System Testing ...................................................................................... 77
5.2 Tested Items........................................................................................................................ 78
CHAPTER 6 CONCLUSION .............................................................................................. 101
6.1 Project Review, Discussions and Conclusions ............................................................... 101
6.2 Highlight any novelties and contributions the project has achieved ........................... 102
6.3 Future Work ..................................................................................................................... 103
REFERENCES ........................................................................................................................... 104
APPENDIX A POSTER.......................................................................................................B-1
APPENDIX B PLAGIARISM CHECK RESULT ............................................................B-1
APPENDIX C CHECKLIST FOR FYP2 THESIS SUBMISSION ................................. C-1
viii
LIST OF FIGURES
Figure Number Title Page

Figure 1.2.1 Amount of different type of vehicles in different states 2
of Malaysia up to 30 June, 2017
(Source: https://paultan.org/2017/10/03/vehicle-
registrations-in-malaysia-hit-28-2-million-
units/untitled-numbers/)
Figure 1.2.2 Reasons of car users in choosing service center or 4
general work shop
(Source: Wahab, Ibrahim & Latif 2018)
Figure 1.4.1 Proposed Approach 6
Figure 2.1.1 Service Reminder Light 9
Figure 2.1.2 Honda Service Reminder Codes 10
Figure 2.2.1 Existing Project Use Case Diagrams 11
Figure 2.2.2 Existing Project Level 1 Data Flow Diagram 11
Figure 2.2.3 Existing Project Outcome 11
Figure 2.2.4 Address Geocoding 13
Figure 3.2.1 System Block Diagram 17
Figure 3.3.1 Use Case Diagram 18
Figure 3.5.1 Entity Relation Diagram 23
Figure 3.7.1 Sample of User Interface Design in Android Studio 35
Figure 4.1 SDLC Adopted 36
Figure 4.3.1 AWS EC2 Instance Details 39
Figure 4.3.2 AWS EC2 Instance Is Running Prove 39
Figure 4.4.1 AWS EC2 Instance Scheduled Tasks Using Crontab 40
Figure 4.5.1 MySQL Create Table “car” 41
Figure 4.5.2 MySQL Create Table “car_service” 41
Figure 4.5.3 MySQL Create Table “car_service_service_item” 42
Figure 4.5.4 MySQL Create Table “customer_car” 42
ix
Figure 4.5.5 MySQL Create Table 43
“customer_car_breakdown_service”
Figure 4.5.6 MySQL Create Table “customer_car_service” 43
Figure 4.5.7 MySQL Create Table “customer_car_service_booking” 44
Figure 4.5.8 MySQL Create Table 44
“customer_car_service_booking_requested_service”
Figure 4.5.9 MySQL Create Table “password_reset_temp” 45
Figure 4.5.10 MySQL Create Table “service_booking_quota” 45
Figure 4.5.11 MySQL Create Table “service_item” 46
Figure 4.5.12 MySQL Create Table “system_inbox” 46
Figure 4.5.13 MySQL Create Table “system_inbox_intent” 47
Figure 4.5.14 MySQL Create Table “user_data” 47
Figure 4.6.1 MySQL Create Event “Remove Some Inbox Message 48
Type”
Figure 4.6.2 MySQL Create Event “Reset Customers Update Their 48
Car Mileage Daily”
Figure 4.6.3 MySQL Create Event “Remove Customer Service 49
Booking After Today Date”
Figure 4.6.4 MySQL Create Event “Sunday Update Pending Admin 49
Approval Breakdown Assistant”
Figure 4.6.5 MySQL Create Event “Monday Update Pending 50
Admin Approval Breakdown Assistant”
Figure 4.6.6 MySQL Create Event “Tuesday Update Pending 50
Figure 4.6.7 MySQL Create Event “Wednesday Update Pending 51
Figure 4.6.8 MySQL Create Event “Thursday Update Pending 51
Figure 4.6.9 MySQL Create Event “Friday Update Pending Admin 52
Approval Breakdown Assistant”
x
Figure 4.6.10 MySQL Create Event “Saturday Update Pending 52
Figure 4.7.1 Facebook for Developer User Authentication 53
Configuration
Figure 4.8.1 Google APIs User Authentication Configuration 53
Figure 4.9.1 Firebase Configuration 54
Figure 4.10.1 Google APIs Maps SDK for Android Configuration 54
Figure 4.11.1 Splash Screen 55
Figure 4.11.2 User Authentication Using Email/Password (1) 56
Figure 4.11.5 User Authentication Using Facebook & Google 59
Account
Figure 4.11.6 Customer Profile Management (1) 60
Figure 4.11.9 Customer Profile Management Special Case 63
Figure 4.11.10 Customer Update Latest Car Mileage 64
Figure 4.11.11 Admin Insert Service Record (1) 65
Figure 4.11.15 Book a Service from Service Reminder Listing 69
Figure 4.11.16 Service Booking (1) 70
Figure 4.11.19 Service Booking Reminder One Day Before the 72
Booking Date and Time
Figure 4.11.20 Car Breakdown Assistant (1) 73
xi
Figure 5.1.1 System Testing Device 1 77
Figure 5.1.2 System Testing Device 2 77
xii
LIST OF TABLES
Table Number Title Page

Table 2.1 Interview & Findings 14
Table 3.1 Description for User Auth Use Case 19
Table 3.2 Description for Manage Profile Use Case 19
Table 3.3 Description for Update Car Mileage Value Use 20
Case
Table 3.4 Description for Make Service Booking Use Case 20
Table 3.5 Description for Request Outdoor Service Use Case 20
Table 3.6 Description for Insert Service Record Use Case 21
Table 3.7 Description for View Booking Requests Use Case 21
Table 3.8 Description for View Outdoor Service Requests Use 21
Case
Table 3.9 Description for Execution of Scheduled Event Use 22
Case
Table 3.10 Data Dictionary for “car” Table 24
Table 3.11 Data Dictionary for “car_service” Table 24
Table 3.12 Data Dictionary for “car_service_service_item” 25
Table
Table 3.13 Data Dictionary for “customer_car” Table 26
Table 3.14 Data Dictionary for 27
“customer_car_breakdown_service” Table
Table 3.15 Data Dictionary for “customer_car_service” Table 28
“customer_car_service_booking” Table
“customer_car_service_booking_requested_service”
Table
xiii
Table 3.18 Data Dictionary for “password_reset_temp” Table 31
Table 3.19 Data Dictionary for “service_booking_quota” Table 31
Table 3.20 Data Dictionary for “service_item” Table 32
Table 3.21 Data Dictionary for “system_inbox” Table 32
Table 3.22 Data Dictionary for “system_inbox_intent” Table 33
Table 3.23 Data Dictionary for “user_data” Table 34
Table 5.1 System Testing 78
Table 6.1 Project Review 101
xiv
LIST OF ABBREVIATIONS
AWS Amazon Web Service

EC2 Elastic Compute Cloud
FYP Final Year Project
HTTP Hypertext Transfer Protocol
IDE Integrated Development Environment
SDLC Software Development Life Cycle
SMS Short Message Service
UTAR Universiti Tunku Abdul Rahman
xv
CHAPTER 1: INTRODUCTION
CHAPTER 1 INTRODUCTION
1.1 Problem Statement
After taking an interview at Pusat Servis Tayar Dan Kereta Maeng Wa Simpang
Pulai branch, several challenges facing by the shop have been identified.
First of all, there is a challenge of car outdoor service in terms of locating exact
GPS coordinate of the car, hence help may not reach on time. The current way that their
customers to request for car outdoor service is either call the shop using phone or ask for
other to fetch them to the shop to bring a mechanic to the break-down location. However,
this will introduce some inconveniences. Especially for merely phone calling, it may
require the shop to spend more time and efforts to call back the customers again and again
to confirm the correct car model, car plate number and broken-down location in case the
shop cannot find the car and the customer.
Moreover, the shop is also currently facing the problem of some customers cannot
wait for long queue. If long queue happened, some customers may choose not to wait their
turn and leave the shop. Therefore, the shop is now losing this particular group of customers
and also losing some potential profits from them at the same time.
Last but not least, the only way the shop is currently using to remind their customers
for next service due is through using the marker pen to write out the next service date or
mileage on the physical service reminder sticker and stick it on the car windscreen.
However, this method is not reliable. Due to the car might be exposed to the sunlight for a
long period and the windscreen will become extremely hot, words written on the sticker
may faded or the sticker itself may not be able to stick on the windscreen anymore after
some time and fall down to somewhere else. Customers may end up not sure when to
perform the car service and may results in the service is performed after the stipulated date
or mileage. This will not only cause some potential damage to the car, but also the shop
may as well as losing some profits. Imagine that the customers service their car lately for
two times, but actually they need to service their car for three times according to the
stipulated next service date or mileage. In this case, the shop has earned one time lesser.
1
1.2 Background and Motivation

According to the Nielsen Global Survey of Automotive Demand in past few year
of 2014, even though the car ownership in South-East Asia is quite low in which 47% of
households in Philippine do not have a car and 46% of households in Indonesia do not have
a car, but surprisingly Malaysia ranked as the third highest percentage i.e. 93% of car
ownership in the world and 54% households having multiple car (The Start Online 2014).
Recently for only the month of April in the year of 2019, car registrations in Malaysia
already having an amount of 109012 (Trading Economics, n.d). Another record according
to the Malaysian Vehicle Registration Data released by the Malaysia Automotive
Association (MAA) showing that up to June 30, 2017, the total number of vehicles on the
roads is 28,181,203 units which also near to 28.2 million units (paultan.org 2017). Below
diagram showing details on how the figure actually to reach 28,181,203.
Figure 1.2.1: Amount of different type of vehicles in different states of Malaysia up to

30 June, 2017 (Source: https://paultan.org/2017/10/03/vehicle-registrations-in-malaysia-
hit-28-2-million-units/untitled-numbers/)
From here we assume that almost every Malaysians are having a car nowadays.
However, we must also know the fact of no matter how luxurious a car is, it is still like a
human being, luxury or ordinary cars also will be broken anytime and requires to send to
2
“car hospital” which is the mechanic shop for repairing or regular maintenance. Owner can
choose to send their car back to genuine service center or any other third-party car
mechanic shops. However, for the case of third-party car mechanic shops in Malaysia, most
of them are still operating their business in a traditional and manual way.
The first traditional and manual way is that the shop is running on first come first
serve basis. We can only wait until the mechanics finish serving the customers come before
us, then only the mechanics will come to serve us.
Next, after changing engine oil, or gear box oil, or performing tires services such
as tires rotation, wheel balancing, and wheel alignment, the mechanics will manually write
the next service due mileage on a sticker and stick it on the car windscreen to remind us to
perform the particular service again when the mileage is reached.
The last part talking about how the normal mechanic shops handle the car outdoor
services. We cannot predict the timing of our car that suddenly breakdown on the road due
to maybe tire puncture or car cannot start. When this happened, we can search online for
nearby car mechanic shops contact number and call them using our phone to come assist
us. The other available option is to seek help from people around the area to fetch us to a
mechanic shop and bring a mechanic from the shop to help us.
Above mentioning are so-called “outdated” practices of a local normal mechanic

shop. However, some people still want to visit third-party mechanic shops may due to the
following reasons or factors. According to the survey results in (Wahab, Ibrahim & Latif
2018), in the question “Reason of car users’ preference towards car maintenance”, 81.94%
of respondents send their car to general workshop because of “Affordable costs”, 63.23%
send their car to general workshop because of “Warranty ended/forfeited”, and 56.13%
says that they will go general workshop because “Easy to discuss and get advisory
services”. These perhaps are the advantages of a third-party mechanic shop to retain their
customers.
3
Figure 1.2.2: Reasons of car users in choosing service center or general work shop
(Source: Wahab, Ibrahim & Latif 2018)
4
1.3 Objectives
1. To study the challenges facing by Pusat Servis Tayar Dan Kereta Maeng Wa
Simpang Pulai Main Branch.
2. To provide solution in terms of incorporation of GPS coordinate to locate

precisely the customers of Pusat Servis Tayar Dan Kereta Maeng Wa Simpang
Pulai Main Branch that requesting for car outdoor services.
3. To provide solution in terms of service booking to help customers of Pusat

Servis Tayar Dan Kereta Maeng Wa Simpang Pulai Main Branch to lower down
the rate of long waiting time.
4. To provide solution in terms of service reminder to notify customers of Pusat

Servis Tayar Dan Kereta Maeng Wa Simpang Pulai Main Branch to service
their car before the mileage due.
5. To validate the prototype by deploying it in Pusat Servis Tayar Dan Kereta

Maeng Wa Simpang Pulai Main Branch.
5
1.4 Proposed Approach / Study
Figure 1.4.1: Proposed Approach
Figure 1.3.1 shows the architecture of the proposed approach in this project in
which Android mobile application will be developed to be made use by the customers and
clerk of the target mechanic shop and the back-end implementation is using AWS EC2
Instance cloud server. Customers and clerk will communicate with each other through the
server to solve the challenges that are currently facing by them.
6
1.5 Highlight of What Have Been Achieved

A mobile application is completed with the functionalities of:
Seeking for Car Breakdown Assistant
Customers able to pin the location where their car is broken at and request for type of
service they want. On the other side, admin able to view the pinned location and type of
service requested by the customers. Lastly, admin able to perform an action by either accept
or reject the request.
Booking for Service(s)
Customers able to book a particular timeslot for their car to be serviced. On the other side,
admin able to check is there any booked service in a timeslot. If yes, priority will be given
to the car to service first.
Reminder for Next Service(s)
After service is performed, admin able to enter the type of service performed and current
mileage value of the car to the system. System is then able to calculate the next service
mileage due based on the type of service entered by the admin. On the other side, customers
able to view the added service history by the admin and the next service mileage due
generated by the system. To make the service reminder possible, customer able to report
the latest mileage value of their car to the system and system will notify the user on how
many kilometers left for the customers to send their car back to the shop for a service.
7
1.6 Report Organization

This report consists of 6 chapters. In Chapter 1 Introduction, there have sub-
chapters of problem statement, background and information, project objectives, proposed
approach/study, highlight of what have been achieved, and report organization. In Chapter
2 Literature Review, there have sub chapters of 3 existing service reminder solutions, 4
researches about practices on capturing coordinates data, and data collection for this project.
In Chapter 3 System Design, there have sub chapters of system block diagram, use case
diagram, use case description, MySQL database entity relationship diagram, MySQL
database data dictionary, and user interface design using Android Studio. In Chapter 4
System Implementation, there have sub-chapters of SDLC method adopted,
implementation tools, screen captures of some configurations, and screen captures of the
implemented Android mobile application. In Chapter 5 System Testing, there have sub-
chapters of devices used to perform testing, and list of items which have been tested. In
last chapter which is Chapter 6 Conclusion, it contains sub-chapters to summarize the
project, list out any novelties, and make suggestion on possible future work to be done.
8
CHAPTER 2: LITERATURE REVIEW
CHAPTER 2 LITERATURE REVIEW

2.1 Literature Review on Existing Service Reminder Solutions
2.1.1 Solution 1 - Built-in Service Reminder Light (Motorist Assurance Program,
2019)
Today, some car manufacturers will equip their cars with a mileage or condition-
based reminder system. It will keep track of the mileage driven since the last maintenance
service was performed and signal the car owner with a reminder light when the next service
is due and need to be performed. The possible weakness for this solution maybe is it may
not available to some old model cars, so a more practical way for service reminder can be
through SMS approach presented in the later part or an application-based service reminder.
Figure 2.1.1: Service Reminder Light
2.1.2 Solution 1 Real World Application - Honda Built-in Service Reminder System
Codes (Honda Ireland, n.d.)
Recently new Honda models is all now having a built-in service reminder system
to tell the owner when the service is due and show out a series of codes to indicate what
type of service is needed. The service reminder spanner sensory signal will keep lighting
for 30 days starting from the first day of the service is due.
9
Figure 2.1.2: Honda Service Reminder Codes
2.1.3 Solution 2 - SMS Reminder System (Swift SMS Gateway, 2017)

Because of response rates are higher, automotive shops can also make use of SMS
to keep their customers for coming back to perform routine car service maintenance. In this
article, it reveals that SMS has an average open rate of 99 percent with a click-thru rate of
36% based on the statistic of marketing blog Business 2 Community.
2.2 Literature Review on Researches about Practices on Capturing Coordinates Data

2.2.1 Existing Project - GPS-based Location Tracking System via Android Device
(Uddin, Islam & Nadim, 2013)
This project is mainly focusing on developing a system that able to let admin track
for the user. Some works done by the project developer are shown as below.
10
Figure 2.2.1: Existing Project Use Case Diagrams
Figure 2.2.2: Existing Project Level 1 Data Flow Diagram
Figure 2.2.3: Existing Project Outcome
Showing above is from the admin view on user’s location marker (left) and user’s
visited path (right).
11
2.2.2 GPS (Universal Service Administrative Co., n.d.)

Many mobile devices such as smartphones or tablet today are GPS-enabled. This is
the most reliable methods to capture coordinates data because it produces the most accurate
results with the least errors and ensure that the coordinates data which is the
latitude/longitude data are gathered for the correct location. Additional jobs for data
collection, verification, and/or clean-up also can be reduced. The requirements for this
geolocation methods to work are telco service can reach the place or have enough telco
signal and the mobile devices have internet connection.
2.2.3 Web-based Maps and Imagery (Universal Service Administrative Co., n.d.)
The second method to identify specific location and its corresponding
latitude/longitude coordinates is through the desktop geolocation using secondary
resources i.e. web-based maps and imagery. This is so-called manual or passive
geolocation methods but it also can provide accurate results like what GPS does providing
that the web-based maps and imagery are in good quality and also the location specified
can be properly identified. The workflow is typically as follow:
1. Open the web-based map.

2. Navigate to the location that want to geolocate by either searching for an address
or zooming the map.
3. Turn on the imagery.
4. Look for the specific location.
5. The latitude/longitude coordinates of the specific location are there.
This method relies highly on whether the map is updated or not, especially in some rural
areas, it may not frequently update the new structures and results in an outdated map.
Moreover, it sometimes is hard to identify specific buildings if there is tree cover the
particular building in the map.
12
2.2.4 Address Geocoding (Universal Service Administrative Co., n.d.)

This method uses an address geocoder program to convert user entered address
information into latitude/longitude coordinates. The program will decipher the address and
based on the underlying referenced data to produce matching latitude/longitude coordinates.
Thus, it relies highly on the maintenance of the referenced data to be the most up to date
one. The program also may not cover the addresses so deeply until rural areas, therefore
results in the result is not reliable when you enter an address that is within a rural area. This
means that if want to apply this geocoding method, large maintenance work is a must to
ensure the accuracy!
Figure 2.2.4: Address Geocoding
13
2.3 Data Collection

To gather user requirements for this project, interview approach is selected. On 8th
August 2019 10AM, I have interviewed Madam Chu who is a clerk from Pusat Servis
Tayar Dan Kereta Maeng Wa Simpang Pulai main branch. Showing below is the main
points that I extracted from the interview session.
Interview & Findings

Interviewee Question Keywords of the answer Findings
Madam “do you mind to “we lost customers who The shop needs a
Chu, clerk in briefly share with cannot wait for their turn to system
Pusat Servis me the issues or let us service their car and incorporating
Tayar Dan challenges your leave our shop.” Service Timeslot
Kereta company is facing Booking feature.
Maeng Wa because of still “we found that some customers The shop needs a
Simpang using traditional come to change engine oil or system
Pulai Main way in running the gear box transmission oil incorporating
Branch business?” after the mileage is due. Some Service Reminder
of them complaint that it is feature.
because the reminder sticker
on the windscreen drop to
somewhere else or the words
written on the sticker has
faded and cannot be seen
clearly, therefore they don’t
know when need to change
the particular lubricant oil.”
“customers call from phone The shop needs a
saying their car broken down system
at somewhere else but incorporating
sometimes the location
14
mentioning by them is Outdoor Service

unclear or we may not Request feature.
familiar on that place. So, it
requires us to keep on contact
the customers to confirm their
actual location which is very
inconvenience for us and
customers themselves.”
Table 2.1: Interview & Findings
15
CHAPTER 3: SYSTEM DESIGN
CHAPTER 3 SYSTEM DESIGN

3.1 Requirements
Before stepping into System Design phase, functional requirements and non-
functional requirements for this project are listed as follow:
Functional Requirements
1. Customers able to perform user authentication using registered email/password,

Facebook, and Google Account.
2. Customers able to perform profile management.
3. Customers able to update latest car mileage.
4. Admin able to insert service record.
5. Customers able to book a service from service reminder listing or not from service
reminder listing.
6. Customers able to request car breakdown assistant.
Non-functional Requirements
1. The application should be easy to learn, easy to remember, effective, pleasant, and
error-free.
2. The SQL process should be accurate, and do not have any latency to avoid delaying
from the front-end.
16
3.2 Block Diagram
Figure 3.2.1: System Block Diagram
Figure 3.2.1 shows the overall architecture of the system going to be implemented
which consists of AWS EC2 server in between customers side and admin side mainly to
support for functionalities of Request Outdoor Services, Make Service Booking, and
Service Reminder.
17
3.3 Use Case Diagram
Figure 3.3.1: Use Case Diagram
18
3.4 Use Case Description

3.4.1 User Auth Use Case
Use Case Name USER AUTH
Actor CUSTOMER, CLERK
Normal Flow of Events 1. User enter login credentials
2. System verify user
3. User login successfully
4. System update database
Alternate/Exceptional Flows 1a1 Customer choose to login using Facebook account

1b1 Customer choose to login using Google account
1c1 Customer choose forget password and proceed to
update new password
1d1 Customer choose to register new account
3a1 User login failure and display error message
Table 3.1: Description for User Auth Use Case
3.4.2 Manage Profile Use Case

Use Case Name MANAGE PROFILE
Actor CUSTOMER
Normal Flow of Events 1. Customer update profile picture
2. System verify the action
Alternate/Exceptional Flows 1a1 Customer choose to update cover picture

1b1 Customer choose to update personal details
1c1 Customer choose to reset password
1d1 Customer choose to add car
2a1 System display error message
Table 3.2: Description for Manage Profile Use Case
19
3.4.3 Update Car Mileage Value Use Case

Use Case Name UPDATE CAR MILEAGE
Actor CUSTOMER
Normal Flow of Events 1. Customer enter mileage
4. System alert user for overdue service
Alternate/Exceptional Flows 2a1 System display error message

4a1 System do nothing
Table 3.3: Description for Update Car Mileage Value Use Case
3.4.4 Make Service Booking Use Case

Use Case Name MAKE SERVICE BOOKING
Actor CUSTOMER
Normal Flow of Events 1. Customer fill up service booking form
4. System forward request to clerk
5. System notify user to remember visit the shop
at the booked date and time

5a1 System do nothing
Table 3.4: Description for Make Service Booking Use Case
3.4.5 Request Outdoor Service Use Case

Use Case Name REQUEST OUTDOOR SERVICE
Actor CUSTOMER
Normal Flow of Events 1. Customer fill up car breakdown assistant form
4. System forward request to clerk
Table 3.5: Description for Request Outdoor Service Use Case

20
3.4.6 Insert Service Record Use Case

Use Case Name INSERT SERVICE RECORD
Actor CLERK
Normal Flow of Events 1. Clerk fill up the insert service record form
4. System forward service record has been updated
message to customer
Table 3.6: Description for Insert Service Record Use Case
3.4.7 View Booking Requests Use Case

Use Case Name VIEW BOOKING REQUESTS
Actor CLERK
Normal Flow of Events 1. System list all service booking made by
customer
Alternate/Exceptional Flows -
Table 3.7: Description for View Booking Requests Use Case
3.4.8 View Outdoor Service Requests Use Case

Use Case Name VIEW OUTDOOR SERVICE REQUESTS
Actor CLERK
Normal Flow of Events 1. System list all outdoor service requests asked by
customer
2. Admin responds on those requests
3. System forward the message to customer in
which the content is the decision of admin
towards their request
Alternate/Exceptional Flows -
Table 3.8: Description for View Outdoor Service Requests Use Case
21
3.4.9 Execution of Scheduled Event Use Case

Use Case Name EXECUTION OF SCHEDULED EVENT
Actor SYSTEM
Normal Flow of Events 1. System execute event on the scheduled date and
time
2. System message customer in the notification bar
and in-app inbox
Alternate/Exceptional Flows 2a1 System message customer in the in-app inbox

because customer is not signed-in the application
Table 3.9: Description for Execution of Scheduled Event Use Case
22
3.5 MySQL Entity Relationship Diagram
Figure 3.5.1: Entity Relationship Diagram
23
3.6 MySQL Data Dictionary

3.6.1 Table “car”
Column Type Attributes Null Default Extra Links to Comments MIME
id int(4) No auto_inc
rement
manufacturer text No
model text No
generation text No
productionyear text No
pic text No
Table 3.10: Data Dictionary for “car” Table
3.6.2 Table “car_service”

rement
servicename text No
availablefor tinyint(1) No
booking
outdoorservice
servicereminder
Table 3.11: Data Dictionary for “car_service” Table
24
3.6.3 Table “car_service_service_item”

rement
service int(2) No ->
car_service.id
ON UPDATE
RESTRICT
ON DELETE
RESTRICT
item int(3) Yes NULL ->
service_item.id
ON UPDATE
RESTRICT
ON DELETE
RESTRICT
milesbetwee int(6) No
nservices
Table 3.12: Data Dictionary for “car_service_service_item” Table
25
3.6.4 Table “customer_car”

rement
regno text No
pic int(4) No -> car.id ON
UPDATE
RESTRICT
ON DELETE
RESTRICT
updatedMile int(6) Yes NULL
age
updatedMile datetime Yes NULL
ageDateTim
e
isUpdateMil tinyint(1) No
eageToday
owner int(11) No ->
user_data.id
ON
UPDATE
RESTRICT
ON DELETE
RESTRICT
Table 3.13: Data Dictionary for “customer_car” Table
26
3.6.5 Table “customer_car_breakdown_service”

rement
car int(11) No ->
customer_car.id
ON UPDATE
RESTRICT
ON DELETE
RESTRICT
servicerequ int(2) No ->
ested car_service.id
ON UPDATE
RESTRICT
ON DELETE
RESTRICT
address text No
longitude text No
latitude text No
requestbrea datetime No
kdownservic
edatetime
status text No
actiondateti datetime No
me
Table 3.14: Data Dictionary for “customer_car_breakdown_service” Table
27
3.6.6 Table “customer_car_service”

rement
car int(11) No ->
customer_car.id
ON UPDATE
RESTRICT
ON DELETE
RESTRICT
service int(3) No ->
car_service_serv
ice_item.id
ON UPDATE
RESTRICT ON
DELETE
RESTRICT
current_serv int(6) Yes NULL
ice_mileage
current_serv date No
ice_date
recordadded int(11) No ->
by user_data.id
ON UPDATE
RESTRICT
ON DELETE
RESTRICT
recordadded datetime No
bydatetime
status text No
Table 3.15: Data Dictionary for “customer_car_service” Table
28
3.6.7 Table “customer_car_service_booking”

rement
car int(11) No ->
customer_car.id
ON UPDATE
RESTRICT
ON DELETE
RESTRICT
requestbook datetime No
ingdatetime
Table 3.16: Data Dictionary for “customer_car_service_booking” Table
29
3.6.8 Table “customer_car_service_booking_requested_service”

rement
booking int(11) No ->
customer_car_s
ervice_booking.id
ON UPDATE
CASCADE
ON DELETE
CASCADE
servicerequ int(2) No -> car_service.id
ested ON UPDATE
RESTRICT
ON DELETE
RESTRICT
dateNtimesl int(11) No ->
ot service_booking
_quota.id ON
UPDATE
CASCADE ON
DELETE
CASCADE
Table 3.17: Data Dictionary for “customer_car_service_booking_requested_service” Table
30
3.6.9 Table “password_reset_temp”

email int(11) No ->
user_data.id
ON
UPDATE
RESTRICT
ON DELETE
RESTRICT
key varchar(250 No
)
expDate datetime No
Table 3.18: Data Dictionary for “password_reset_temp” Table
3.6.10 Table “service_booking_quota”

rement
date date No
start time No
end time No
limitednumb int(1) No
erofpax
Table 3.19: Data Dictionary for “service_booking_quota” Table
31
3.6.11 Table “service_item”

rement
item_name Text No
Table 3.20: Data Dictionary for “service_item” Table
3.6.12 Table “system_inbox”

rement
receiver int(11) No ->
user_data.id
ON
UPDATE
RESTRICT
ON DELETE
RESTRICT
title text No
body text No
targetActivit text No
y
inboxType text No
inboxDateTi datetime No
me
Table 3.21: Data Dictionary for “system_inbox” Table
32
3.6.13 Table “system_inbox_intent”

rement
name text No
value text No
inbox int(11) No ->
system_inbox.id
ON UPDATE
CASCADE
ON DELETE
CASCADE
Table 3.22: Data Dictionary for “system_inbox_intent” Table
33
3.6.14 Table “user_data”

rement
token text Yes NULL
role text No
coverurl text Yes NULL
imageurl text Yes NULL
firstname text Yes NULL
lastname text Yes NULL
contactnum text Yes NULL
ber
provider text No
username text No
password text Yes NULL
confirmpass text Yes NULL
word
isverified tinyint(1) Yes NULL
securityque text Yes NULL
stion1
securityque text Yes NULL
stion2
created datetime No
signedin datetime Yes NULL
uid text Yes NULL
Table 3.23: Data Dictionary for “user_data” Table
34
3.7 User Interface Design in Android Studio
Figure 3.7.1: Sample of User Interface Design in Android Studio
Figure 3.7.1 shows the one of the sample screen (Customer Add Car) is designed
conveniently using the drag-and-drop feature provided by Android Studio.
35
CHAPTER 4: SYSTEM IMPLEMENTATION
CHAPTER 4 SYSTEM IMPLEMENTATION

4.1 SDLC Method Adopted
Figure 4.1: SDLC Adopted
The adopted software development life cycle is the incremental model. It consists
of several phases, such as Initial Planning, Planning, Requirements, Analysis & Design,
Implementation, Testing, Evaluation, and Deployment. The overall concept is like this: We
first plan the project, second gather user requirements, third analyze those gathered
requirements to come out some system functionalities, fourth design the system based on
functionalities that must be included, fifth implement the functionalities to the system
based on the design, sixth test the implemented functionalities, then deploy the version of
the system to the user. User will then test and evaluate the system. If developer or user
think that the system needs to add on anything, the process will be run again from planning,
requirements, analysis, design, implementation, alpha testing, deployment, beta testing,
and evaluation.
36
4.2 Implementation Tools

Cloud Computing Software
1. Amazon Web Services (AWS) EC2 Instance for web service.

2. Web-based phpMyAdmin database management tool reside in the instance to
manage the cloud database.
3. Cloud MySQL database reside in the instance to store mobile application data.
4. Apache HTTP server reside in the instance to handling HTTP request from
the mobile application
Software
1. Android Studio act as the IDE to develop the mobile applications and test run
the mobile applications in the Android emulator.
2. WinSCP to view and edit the php programs store in the AWS EC2 instance
(remote computer) from our computer (local).
3. Web Browser to connect phpMyAdmin and to view uploaded images in the
instance.
4. Postman for testing PHP scripts.
Hardware
Android smartphone / Android Studio Emulator to run the mobile applications
37
APIs
1. Facebook Login API for Facebook User Authentication

2. Google Login API for Google User Authentication
3. Google Map API for locating the customers with car breakdown assistant need
4. Firebase Cloud Messaging API for handling notification from device to
device
Library
PHPMailer to send emails safely and easily via PHP code from a web server for user
account verification and forgot password usage.
38
4.3 AWS EC2 Instance Configuration
Figure 4.3.1: AWS EC2 Instance Details
Figure 4.3.1 shows the public DNS and other details of the configured Amazon
Linux server.
Figure 4.3.2: AWS EC2 Instance Is Running Prove
Figure 4.3.2 shows the server page is loaded successfully in the browser using the
public DNS which proved that the server is in running state
39
4.4 Linux Crontab Command in AWS EC2 Instance
Figure 4.4.1: AWS EC2 Instance Scheduled Tasks Using Crontab
9 * * 1-5 /usr/bin/php /var/www/html/fyp/scheduleSendMultiplePush.php
Above Linux command means scheduleSendMultiplePush php script will be executed on

5pm every Monday to Friday. The script is to ask customers to update latest mileage
value of their car.
0 4 * * * /usr/bin/php
/var/www/html/fyp/scheduleSendMultiplePushForServiceReminder.php
Above Linux command means scheduleSendMultiplePushForServiceReminder php script

will be executed on 12pm every day. The script is to remind customers of the remaining
kilometers to go for the next service.
* * * * * /usr/bin/php
/var/www/html/fyp/scheduleSendMultiplePushForServiceBookingReminder.php
Above Linux command means scheduleSendMultiplePushForServiceBookingReminder

php script will be executed on every single minute. The script is to remind customers one
day and one hour before the date time they choose to send their car for some service(s).
40
4.5 MySQL Table Creation

4.5.1 Table “car”
Figure 4.5.1: MySQL Create Table “car”
Figure 4.5.1 shows the created “car” table in MySQL database using the table
structure designed during system design phase.
4.5.2 Table “car_service”
Figure 4.5.2: MySQL Create Table “car_service”
Figure 4.5.2 shows the created “car_service” table in MySQL database using the
table structure designed during system design phase.
41
4.5.3 Table “car_service_service_item”
Figure 4.5.3: MySQL Create Table “car_service_service_item”
Figure 4.5.3 shows the created “car_service_service_item” table in MySQL

database using the table structure designed during system design phase.
4.5.4 Table “customer_car”
Figure 4.5.4: MySQL Create Table “customer_car”
Figure 4.5.4 shows the created “customer_car” table in MySQL database using the
42
4.5.5 Table “customer_car_breakdown_service”
Figure 4.5.5: MySQL Create Table “customer_car_breakdown_service”
Figure 4.5.5 shows the created “customer_car_breakdown_service” table in

MySQL database using the table structure designed during system design phase.
4.5.6 Table “customer_car_service”
Figure 4.5.6: MySQL Create Table “customer_car_service”
Figure 4.5.6 shows the created “customer_car_service” table in MySQL database

using the table structure designed during system design phase.
43
4.5.7 Table “customer_car_service_booking”
Figure 4.5.7: MySQL Create Table “customer_car_service_booking”
Figure 4.5.7 shows the created “customer_car_service_booking” table in MySQL

4.5.8 Table “customer_car_service_booking_requested_service”
Figure 4.5.8: MySQL Create Table “customer_car_service_booking_requested_service”
Figure 4.5.8 shows the created “customer_car_service_booking_requested_service”

table in MySQL database using the table structure designed during system design phase.
44
4.5.9 Table “password_reset_temp”
Figure 4.5.9: MySQL Create Table “password_reset_temp”
Figure 4.5.9 shows the created “password_reset_temp” table in MySQL database

4.5.10 Table “service_booking_quota”
Figure 4.5.10: MySQL Create Table “service_booking_quota”
Figure 4.5.10 shows the created “service_booking_quota” table in MySQL

45
4.5.11 Table “service_item”
Figure 4.5.11: MySQL Create Table “service_item”
Figure 4.5.11 shows the created “service_item” table in MySQL database using the
4.5.12 Table “system_inbox”
Figure 4.5.12: MySQL Create Table “system_inbox”
Figure 4.5.12 shows the created “system_inbox” table in MySQL database using
the table structure designed during system design phase.
46
4.5.13 Table “system_inbox_intent”
Figure 4.5.13: MySQL Create Table “system_inbox_intent”
Figure 4.5.13 shows the created “system_inbox_intent” table in MySQL database

4.5.14 Table “user_data”
Figure 4.5.14: MySQL Create Table “user_data”
Figure 4.5.14 shows the created “user_data” table in MySQL database using the
47
4.6 MySQL Event Creation

4.6.1 Scheduled Event to Remove Inbox Message
Figure 4.6.1: MySQL Create Event “Remove Some Inbox Message Type”
Figure 4.6.1 shows the created “Remove Some Inbox Message Type” event in
MySQL database with the purpose of removing all the “Request Update Latest Car
Mileage”, “Service Reminder”, and “Service Booking Reminder” message from the inbox
on 12am every day.
4.6.2 Scheduled Event to Reset “isUpdateMileageToday” Flag
Figure 4.6.2: MySQL Create Event “Reset Customers Update Their Car Mileage Daily”
Figure 4.6.2 shows the created “Reset Customers Update Their Car Mileage Daily”
event in MySQL database with the purpose of setting the status of all the customer car to
“car mileage is not yet updated today” on 12am every day.
48
4.6.3 Scheduled Event to Remove Customer Service Booking
Figure 4.6.3: MySQL Create Event “Remove Customer Service Booking After Today
Date”
Figure 4.6.3 shows the created “Remove Customer Service Booking After Today
Date” event in MySQL database with the purpose of removing all that day’s customer
service booking requests on 11.59pm every day.
4.6.4 Scheduled Event to Auto Reject Breakdown Assistant Request (Sunday)
Figure 4.6.4: MySQL Create Event “Sunday Update Pending Admin Approval
Breakdown Assistant”
Figure 4.6.4 shows the created “Sunday Update Pending Admin Approval
Breakdown Assistant” event in MySQL database with the purpose of auto reject all the
customer car breakdown assistant requests which are still in pending admin approval state
on 5pm at Sunday (Shop closing time).
49
4.6.5 Scheduled Event to Auto Reject Breakdown Assistant Request (Monday)
Figure 4.6.5: MySQL Create Event “Monday Update Pending Admin Approval
Figure 4.6.5 shows the created “Monday Update Pending Admin Approval
on 7pm at Monday (Shop closing time).
4.6.6 Scheduled Event to Auto Reject Breakdown Assistant Request (Tuesday)
Figure 4.6.6: MySQL Create Event “Tuesday Update Pending Admin Approval
Figure 4.6.6 shows the created “Tuesday Update Pending Admin Approval
on 7pm at Tuesday (Shop closing time).
50
4.6.7 Scheduled Event to Auto Reject Breakdown Assistant Request (Wednesday)
Figure 4.6.7: MySQL Create Event “Wednesday Update Pending Admin Approval
Figure 4.6.7 shows the created “Wednesday Update Pending Admin Approval
on 7pm at Wednesday (Shop closing time).
4.6.8 Scheduled Event to Auto Reject Breakdown Assistant Request (Thursday)
Figure 4.6.8: MySQL Create Event “Thursday Update Pending Admin Approval
Figure 4.6.8 shows the created “Thursday Update Pending Admin Approval
on 7pm at Thursday (Shop closing time).
51
4.6.9 Scheduled Event to Auto Reject Breakdown Assistant Request (Friday)
Figure 4.6.9: MySQL Create Event “Friday Update Pending Admin Approval
Figure 4.6.9 shows the created “Friday Update Pending Admin Approval
on 7pm at Friday (Shop closing time).
4.6.10 Scheduled Event to Auto Reject Breakdown Assistant Request (Saturday)
Figure 4.6.10: MySQL Create Event “Saturday Update Pending Admin Approval
Figure 4.6.10 shows the created “Saturday Update Pending Admin Approval
on 7pm at Saturday (Shop closing time).
52
4.7 “Facebook For Developer” Configuration for User Authentication Using

Facebook Account
Figure 4.7.1: Facebook for Developer User Authentication Configuration
Figure 4.7.1 shows the configuration at Facebook for Developer to make the
Android mobile application able to authenticate customers with their Facebook account.
4.8 Google APIs Configuration for User Authentication Using Google Account
Figure 4.8.1: Google APIs User Authentication Configuration
Figure 4.8.1 shows the configuration at Google APIs to make the Android mobile
application able to authenticate customers with their Google account.
53
4.9 Firebase Configuration for Publishing Notification Using Firebase Cloud

Messaging
Figure 4.9.1: Firebase Configuration
Figure 4.9.1 shows the configuration at Firebase to make use of the Firebase Cloud
Messaging feature so that any notification of the Android mobile application able to send
from single device to single device, and system to multiple devices.
4.10 Google APIs Maps SDK for Android Configuration
Figure 4.10.1: Google APIs Maps SDK for Android Configuration
Figure 4.10.1 shows the configuration at Google APIs to make use of the Maps
SDK for Android so that the Android mobile application able to locate the customers at
their current coordinate.
54
4.11 Android Application Development

4.11.1 Splash Screen
Figure 4.11.1: Splash Screen
Figure 4.11.1 shows the completely implemented splash screen and User Login
screen.
55
4.11.2 User Authentication Using Email/Password
Figure 4.11.2: User Authentication Using Email/Password (1)
56
57
Figure 4.11.2 to Figure 4.11.4 shows the flow of completely implemented User
Authentication Using Email/Password function which covers Registration, New User
Account Verification, Login, Logout, and Password Recovery features.
58
4.11.3 User Authentication Using Facebook & Google Account
Figure 4.11.5: User Authentication Using Facebook & Google Account
Figure 4.11.5 shows the flow of completely implemented User Authentication

Using Facebook & Google Account function.
59
4.11.4 Customer Profile Management
Figure 4.11.6: Customer Profile Management (1)
60
61
Figure 4.11.6 to Figure 4.11.8 shows the flow of completely implemented

Customer Profile Management function which covers Change Picture, Update Personal
Details, Reset Password, and Add Car features.
62
4.11.5 Customer Profile Management Special Case for Facebook or Google

Authenticated Users
Figure 4.11.9: Customer Profile Management Special Case
Figure 4.11.9 shows 2 special cases of the implemented Customer Profile

Management function for customers signed in using Facebook or Google Account in which
the customer will be alerted to update his phone number and the customer cannot make use
of reset password feature.
63
4.11.6 Customer Update Latest Car Mileage
Figure 4.11.10: Customer Update Latest Car Mileage
Figure 4.11.10 shows the flow of completely implemented Customer Update Latest
Car Mileage function which covers System to Request Customer to Update Latest Car
Mileage on 5pm every day, and Customer to Update Car Mileage features.
64
4.11.7 Admin Insert Service Record
Figure 4.11.11: Admin Insert Service Record (1)
65
66
67
Figure 4.11.11 to Figure 4.11.14 shows the flow of completely implemented Admin
Insert Service Record function which covers Admin to Insert Service Record, Admin to
View Owner Details and Car Details of the Added Service Record, Customer to View the
Added/Updated Service Record, and Service Reminder features.
68
4.11.8 Book a Service from Service Reminder Listing
Figure 4.11.15: Book a Service from Service Reminder Listing
Figure 4.11.15 shows the flow of completely implemented Book a Service from
Service Reminder Listing function which covers Customer to Make Service Booking with
auto-filled Car Registration Number and Service, and Admin to View the Details of Service
Booking Made by Customer features.
69
4.11.9 Service Booking
Figure 4.11.16: Service Booking (1)
70
71
Figure 4.11.19: Service Booking Reminder One Day Before the Booking Date and Time
Figure 4.11.16 to Figure 4.11.18 shows the flow of implemented Service Booking
function which is not initiated from the Service Reminder Listing and thus the Car
Registration Number and Service are not auto-filled. Figure 4.11.19 shows the features of
System to Remind Customer to Present in the Booked Date and Time.
72
4.11.10 Car Breakdown Assistant
Figure 4.11.20: Car Breakdown Assistant (1)
73
74
75
Figure 4.11.20 to Figure 4.11.23 shows the flow of completely implemented Car
Breakdown Assistant function which covers Customer to Request Assistant, and Admin to
Perform Action on Customer Request features.
76
CHAPTER 5: SYSTEM TESTING
CHAPTER 5 SYSTEM TESTING

5.1 Devices Used for System Testing
Device 1 (Real Android Smartphone):
Figure 5.1.1: System Testing Device 1
Device 2 (Android Emulator):
Figure 5.1.2: System Testing Device 2
77
5.2 Tested Items

Category Items Results Verified by
Device Device
1 2
1. Splash Animated splash screen is √ √ Wong Sai Kit
Screen functioned.
If no user logged in, User Login √ √ Wong Sai Kit
screen is launched after
animated splash screen.
If there is user logged in, Main √ √ Wong Sai Kit
Menu screen is launched after
splash screen.
Username and password are √ √ Wong Sai Kit
auto filled up if previously
“Remember me?” is ticked.
Username and password fields √ √ Wong Sai Kit
are empty if previously
“Remember me?” is unticked.
2. User User Registration screen able to √ √ Wong Sai Kit
Authentication reach if user clicked on
Using “Register” button at User Login
Email/Password screen.
Camera able to launch when √ √ Wong Sai Kit
user choose to take a picture to
upload his profile picture or
cover picture.
Image gallery able to launch √ √ Wong Sai Kit
when user choose to select
existing picture from image
78
gallery to upload his profile

picture or cover picture.
Picture able to attach in profile √ √ Wong Sai Kit
picture or cover picture section
after selecting an image from
device image gallery.
Picture able to attach in profile √ √ Wong Sai Kit
picture or cover picture section
after capturing image using
device camera.
If profile picture or cover picture √ √ Wong Sai Kit
is made by capturing using
device camera, the system able
to keep a copy of the captured
image in the device gallery.
User able to view attached √ √ Wong Sai Kit
profile picture and cover picture
in a pop-up window after
clicking it.
System able to alert user with √ √ Wong Sai Kit
corresponding error message
when profile picture is empty,
cover picture is empty, field
validation rule is violated, or the
username (Email address) is
existing in database.
User registration is success √ √ Wong Sai Kit
when all the necessarily
information is provided in
correct format.
79
System able to store the user √ √ Wong Sai Kit

information provided into the
database.
System able to mark all newly √ √ Wong Sai Kit
registered users as account not
yet verified status.
System able to send an account √ √ Wong Sai Kit
verification email to the
username (Email address)
provided by the user.
System able to mark users as √ √ Wong Sai Kit
account verified when the
account verification link in the
email is clicked.
The account verification link is √ √ Wong Sai Kit
one-time usage only and so
subsequent time of clicking it
will display invalid link
message.
System do not allow for account √ √ Wong Sai Kit
not verified user from signing in
the application by alerting the
user with an error message.
If account is verified, system √ √ Wong Sai Kit
will make sure the login
credential entered is matched
with the database, else error
message will be alerted.
If sign in success, system able to √ √ Wong Sai Kit
alert user with his display name
80
and provider used for signing in

the application.
System able to generate a √ √ Wong Sai Kit
Firebase token to successfully
signed in user for receiving
notification purpose.
System able to display profile √ √ Wong Sai Kit
picture, cover picture, and
display name section in the side
drawer with the profile picture,
cover picture, and display name
of the successfully signed in
user.
System able to sign out the user √ √ Wong Sai Kit
and clear off the Firebase token
granted.
System able to prompt user an √ √ Wong Sai Kit
error message if the user clicked
on “Forget password?” but the
username field is empty.
System able to send a password √ √ Wong Sai Kit
recovery email to the username
(Email address) entered by the
user providing that the username
is found in the database, else
error message will be alerted.
User able to reach password √ √ Wong Sai Kit
recovery page in the browser
when clicked on the link in the
password recovery email.
81
System able to update the √ √ Wong Sai Kit

password of the user in database
to new password entered by the
user in the password recovery
page providing that all the field
validation rules are passed, else
error message will be prompted.
The password recovery link will √ √ Wong Sai Kit
be deactivated once the
password is updated
successfully, else will be expired
after 24 hours.
3. User System able to sign in those √ √ Wong Sai Kit
Authentication users who using Facebook
Using Facebook account to authenticate
& Google themselves.
Account System able to sign in those √ √ Wong Sai Kit
users who using Google account
to authenticate themselves.
If sign in successfully, system √ √ Wong Sai Kit
able to alert user with his display
name and provider used for
signing in the application.
4. Customer My Profile screen able to reach √ √ Wong Sai Kit
Profile if user clicked on “My Profile”
Management button at Main Menu screen or
side drawer.
System able to display profile √ √ Wong Sai Kit
picture, cover picture, display
name, and username section
82
with the profile picture, cover

picture, display name, and
username (Email address) of the
signed in user.
List of actions such as to view √ √ Wong Sai Kit
picture in a pop-up window,
update picture by taking picture
using device camera, and update
picture by selecting picture from
device image gallery will appear
at the bottom when user clicked
on profile picture or cover
picture.
Profile picture or cover picture √ √ Wong Sai Kit
will display in a pop-up window
when preview picture selection
is chosen.
Camera able to launch when √ √ Wong Sai Kit
take picture from camera is
chosen.
Image gallery able to launch √ √ Wong Sai Kit
when select image from gallery
is chosen.
User able to update his profile √ √ Wong Sai Kit
picture or cover picture to a new
one after capturing an image
using camera.
User able to update his profile √ √ Wong Sai Kit
picture and cover picture to a
83
new one after selecting an image

from image gallery.
If new profile picture or cover √ √ Wong Sai Kit
picture is captured using device
camera, the system able to keep
a copy of the captured image in
the device gallery.
Personal details and my cars √ √ Wong Sai Kit
section are collapsed at first the
screen is loaded.
By clicking the tab of the √ √ Wong Sai Kit
collapsed section respectively,
the particular section will
expand.
By clicking the tab of the √ √ Wong Sai Kit
expanded section respectively,
the particular section will
collapse.
System able to display all the √ √ Wong Sai Kit
information in the personal
details section matched to the
signed in user correctly.
“Edit” and “Reset Password” √ √ Wong Sai Kit
menu will be prompted when the
vertical ellipsis in the right most
of the “Personal Details” bar is
clicked.
Edit Personal Details screen able √ √ Wong Sai Kit
to reach if user clicked on the
“Edit” menu item.
84
All fields in Edit Personal √ √ Wong Sai Kit

Details screen is auto filled up
with old values.
Error message will be alerted if √ √ Wong Sai Kit
user submit the edit personal
details form without making any
changes or violating field
validation rules.
User will be redirect back to My √ √ Wong Sai Kit
Profile screen and able the see
the changes of their personal
details under personal details
section if the edit personal
details form is submitted
successfully.
Reset Password screen able to √ √ Wong Sai Kit
reach if user clicked on the
“Reset Password” menu item.
user submit the reset password
form by violating field
validation rules, providing
wrong old password, wrong
security question 1, or wrong
security question 2.
System able to update that √ √ Wong Sai Kit
particular user’s information in
the database with the new
password entered and prompt to
ask user whether to sign out if
85
the reset password form is

submitted successfully.
User unable to sign in the √ √ Wong Sai Kit
application with old password
after reset password
successfully.
System able to display list of √ √ Wong Sai Kit
cars in the expanded my car
section if the user has added any
car to the system or else display
no car is added message.
“Add” menu will be prompted √ √ Wong Sai Kit
when the vertical ellipsis in the
right most of the “My Car” bar is
clicked.
Insert New Car screen able to √ √ Wong Sai Kit
reach if user clicked on the
“Add” menu item or no car is
added message.
List of car manufacturer will pop √ √ Wong Sai Kit
up for user to select if
manufacturer dropdown list is
clicked.
Car model will be dynamically √ √ Wong Sai Kit
listed out according to the
selected car manufacturer.
Car sample picture will be √ √ Wong Sai Kit
dynamically listed out according
to the selected car model.
86

car registration number is
existing in the database, car
registration number field is
empty, car manufacturer is not
selected, car model is not
selected, or car sample picture is
not selected.
User will be redirect back to My √ √ Wong Sai Kit
Profile screen and able the see
the car registration number of
the newly added car under my
car section if the insert new car
form is submitted successfully.
Car information will be √ √ Wong Sai Kit
prompted at the bottom if user
click on the info button at the
right most of the listed car
registration number under my
car section.
5. Customer System able to change the √ √ Wong Sai Kit
Profile displayed username (Email
Management address) to display
Special Case for “Facebook/Google
Facebook or authenticated” since email
Google address of Facebook or Google
Authenticated authenticated user is not
Users available in the system.
System able to alert user to √ √ Wong Sai Kit
update his phone number since
87
phone number of the user is not

taken and saved to the database
for users who signed in to the
application using Facebook or
Google account for the first
time.
System able to update database √ √ Wong Sai Kit
with the phone number entered
by user providing that the phone
number is not empty and in
correct format, else error
message will be prompted.
System will not alert message to √ √ Wong Sai Kit
request for phone number
anymore if the phone number is
successfully updated in the
database.
System able to lock the √ √ Wong Sai Kit
password reset feature for users
who signed in to the application
using Facebook or Google
account.
6. Customer System able to send the message √ √ Wong Sai Kit
Update Latest to users requesting them to
Car Mileage update the latest mileage value
of all their added car through
notification bar (user is signed
in) and in-app inbox (user is not
signed in) on 5pm every day.
88
System able to reset all the √ √ Wong Sai Kit

customer car to the status of not
yet update latest car mileage
value on 12am every day.
System able to launch Service √ √ Wong Sai Kit
Reminder screen of a car once
user clicked on the request for
updating car mileage message in
the notification bar or in-app
inbox.
System able to determine √ √ Wong Sai Kit
whether the user has updated the
car mileage on that day (if yes,
alert message saying no need to
update car mileage for that day;
if no, ask for entering current
mileage value of that car). If it is
not the first time to update the
latest car mileage value, system
will able to display last updated
car mileage value and date time
the user performed that update.
the entered latest car mileage
value is empty, contains leading
zero, smaller than last reported
mileage value (if not the first
time of updating mileage value
of that car). Or else the value
will be successfully updated.
89
User will see the changes of the √ √ Wong Sai Kit

reported mileage value and date
time made the report once the
latest mileage value is
successfully updated.
For all the listed service √ √ Wong Sai Kit
reminder, once update latest car
mileage value request is
accepted successfully, system
able to calculate and display the
remaining kilometers to go for
next service. If found the
reported mileage is exceed the
next service due, system able to
alert user and change the status
of that service reminder to
“Overdue”.
System able to send the message √ √ Wong Sai Kit
to users on 12pm every day
reminding them the remaining
kilometers to go for next service
or service that already overdue
(if any) providing that the user
has updated the latest mileage of
his car.
7. Admin Insert Admin able to navigate to Latest √ √ Wong Sai Kit
Service Record Service Record screen with
customer service record listing
and collapsed New Service
Record section.
90
New Service Record section √ √ Wong Sai Kit

able to expand to reveal the
insert new customer service
record form when the “+” button
is clicked.
System able to display the √ √ Wong Sai Kit
filterable customer car
registration number listing when
the car dropdown list is clicked.
filterable service type (mainly
for service reminder) listing
when the service type dropdown
list is clicked.
System able to reveal the service √ √ Wong Sai Kit
item dropdown list if the
selected service type does have
list of items to select.
filterable service item listing
when the service item dropdown
list is clicked.
calendar when date is clicked.
System able to ask for entering √ √ Wong Sai Kit
mileage value of that car during
that service when mileage is
clicked.
System able to verify the √ √ Wong Sai Kit
mileage value is not empty, do
91
not contains leading zero, or

greater than the last reported
mileage value by the owner (if
there is last reported mileage
value). Or else error message
will be prompted and disallow
the insertion of invalid car
mileage value.
Providing that not exiting the √ √ Wong Sai Kit
Latest Service Record screen,
application able to load back the
cached selected date and
successfully inserted car
mileage value.
When click to submit insert new √ √ Wong Sai Kit
customer service request,
system able to alert admin if car
is not selected, service type is
not selected, service item (if
any) is not selected, date is not
selected, or mileage value is not
entered. Else the request can be
proceeded.
If the request is allowed to √ √ Wong Sai Kit
proceed, system able to check
first whether the combination of
the car and the service type is
found in the database. If found,
just update the item and mileage
92
column of that row, or else insert

a new row.
System able to display the most √ √ Wong Sai Kit
recent updated / inserted
customer service record at the
first row of customer service
record listing.
Admin able to filter the √ √ Wong Sai Kit
displayed customer service
record listing by using car
registration number.
Admin able to navigate to √ √ Wong Sai Kit
Owner Details screen and Car
Details screen by selecting the
showing “Owner details” or
“Car details” menu item
respectively when clicked the
listed customer service record.
Admin able to view the owner √ √ Wong Sai Kit
personal details in Owner
Details screen.
Admin able to view the picture √ √ Wong Sai Kit
in a pop-up window when
clicked on the picture in Owner
Details screen.
Admin able to view car √ √ Wong Sai Kit
information in Car Details
screen.
System able to send message to √ √ Wong Sai Kit
the car owner through
93
notification bar or in-app inbox

saying that admin has recently
updated his car service record.
At customer side, system able to √ √ Wong Sai Kit
launch Service Reminder screen
of that car once he clicked the
car service record updated
message in the notification bar
or in-app inbox and that
particular service record will
appear in the service reminder
listing.
8. Book a System able to launch Schedule √ √ Wong Sai Kit
Service from a Service screen with expanded
Service Book for Service section
Reminder contains auto-filled car
Listing registration number and service
to be booked when user click on
any service reminder in the
Service Reminder screen.
calendar when date is clicked.
System able to alert user if the √ √ Wong Sai Kit
selected date is not after today
date.
Schedule a Service screen,
cached selected date.
94
System able to display the only √ √ Wong Sai Kit

timeslots which are occupied by
0 or 1 car on the selected date
when timeslot dropdown list is
clicked.
When click to submit service √ √ Wong Sai Kit
booking, system able to alert
user if date is not selected,
timeslot is not selected, or the
combination of the car and
service is found in the database.
Else the details of the booking
will be saved.
System able to display the most √ √ Wong Sai Kit
recent service booking at the
first row of service booking
listing.
User able to filter the displayed √ √ Wong Sai Kit
service booking listing by using
car registration number.
the user through notification bar
or in-app inbox one day before
and one hour before the booked
date time to remind the user for
the service booking he made.
the admin through notification
bar or in-app inbox informing
that the customer has booked the
95
time from xx to xx at xx date for

his xx car to be having xx
service.
At admin side, system able to √ √ Wong Sai Kit
launch Service Booking
Requests screen once he clicked
the customer service booking
message in the notification bar
or in-app inbox and that
particular customer service
booking will appear in the
customer service booking
listing.
System able to remove all the √ √ Wong Sai Kit
service booking record after that
booking date at 11:59pm every
day.
9. Service System able to launch Schedule √ √ Wong Sai Kit
Booking a Service screen with collapsed
Book for Service section when
user clicked on “Service
Booking” button at Main Menu
screen or side drawer.
Book for Service able to expand √ √ Wong Sai Kit
once the “+” button is clicked.
System able to list car √ √ Wong Sai Kit
registration number of all the
cars added by the user when car
dropdown list is clicked.
96
System able to list all services √ √ Wong Sai Kit

available for booking when
service dropdown list is clicked.
System able to alert user if user √ √ Wong Sai Kit
do not select any service from
the service listing.
User able to select more than one √ √ Wong Sai Kit
service for service booking.
Schedule a Service screen,
cached selected date and
selected service(s).
System able to change the listing √ √ Wong Sai Kit
timeslot duration dynamically
based on number of services
selected and make sure not
include those timeslots that
contains hour that occupied by 2
cars.
10. Car System able to launch Car √ √ Wong Sai Kit
Breakdown Breakdown Assistant screen
Assistant with Google Map displayed, a
person icon on the map
representing the current
coordinate of the user, and a
collapsed Seek for Assistant
section when user clicked on
“Breakdown Assistant” button
97
at Main Menu screen or side

drawer.
System able to display address √ √ Wong Sai Kit
of the coordinate on top of the
person icon if user clicked on the
person icon.
System able to expand the Seek √ √ Wong Sai Kit
for Assistant section with auto-
filled address, longitude, and
latitude information and the map
will be re-centered if user
clicked on the SOS button.
System able to list car √ √ Wong Sai Kit
registration number of all the
cars added by the user when car
System able to list all services √ √ Wong Sai Kit
available for breakdown
assistant when service
When click to submit car √ √ Wong Sai Kit
breakdown assistant request,
system able to alert user if car is
not selected, service is not
selected, there is other cars
owned by the user is/are in
pending admin approval status,
or the time is not within business
hour of that day. Else the car
98
breakdown assistant request will

be proceeded.
System able to add a car icon to √ √ Wong Sai Kit
the coordinate where the user
requested breakdown assistant
for his car.
User able to trace back his car √ √ Wong Sai Kit
breakdown assistant request
once “My Requests” button is
clicked.
System able to move the view to √ √ Wong Sai Kit
focus on the pinned location of
the broken-down car
corresponding to the clicked
request in “My Requests”.
admin through notification bar
or in-app inbox saying that
customer has recently requested
for an assistant for his broken-
down car.
At admin side, system able to √ √ Wong Sai Kit
launch Breakdown Assistant
Requests screen once he clicked
the customer car breakdown
assistant request message in the
notification bar or in-app inbox
and that particular request will
appear in the alert once
99
“Customer Requests” button is

clicked.
Admin able to perform action on √ √ Wong Sai Kit
the car breakdown assistant
requested by users in accepting
the request, rejecting the
request, or marking the request
as solved.
users through notification bar or
in-app inbox for whatever action
by the admin towards the car
breakdown assistant requested
by them.
Table 5.1: System Testing
100
CHAPTER 6: CONCLUSION
CHAPTER 6 CONCLUSION
6.1 Project Review, Discussions and Conclusions
Project Outcomes Objectives Is
Objective
Achieved?
1 Challenges facing by the target user To study the challenges Yes
able to identified through interview. facing by Pusat Servis Tayar
Dan Kereta Maeng Wa
Simpang Pulai Main Branch.
2 Customers able to pin the location To provide solution in terms Yes
where their car is broken at and of incorporation of GPS
request for type of service they want. coordinate to locate
On the other side, admin able to view precisely the customers of
the pinned location and type of Pusat Servis Tayar Dan
service requested by the customers. Kereta Maeng Wa Simpang
Lastly, admin able to perform an Pulai Main Branch that
action by either accept or reject the requesting for car outdoor
request. services.
3 Customers able to book a particular To provide solution in terms Yes
timeslot for their car to be serviced. of service booking to help
On the other side, admin able to customers of Pusat Servis
check is there any booked service in Tayar Dan Kereta Maeng
a timeslot. If yes, priority will be Wa Simpang Pulai Main
given to the car to service first. Branch to lower down the
rate of long waiting time.
4 After service is performed, admin To provide solution in terms Yes
able to enter the type of service of service reminder to notify
performed and current mileage value customers of Pusat Servis
of the car to the system. System is Tayar Dan Kereta Maeng
then able to calculate the next service Wa Simpang Pulai Main
101
mileage due based on the type of Branch to service their car

service entered by the admin. On the before the mileage due.
other side, customers able to view the
added service history by the admin
and the next service mileage due
generated by the system. To make the
service reminder possible, customer
able to report the latest mileage value
of their car to the system and system
will notify the user on how many
kilometers left for the customers to
send their car back to the shop for a
service.
5 Because of 2020 Malaysia movement To validate the prototype by Partially
control order, user testing is not deploying it in Pusat Servis Achieved
available but system testing made by Tayar Dan Kereta Maeng
developer is available. Wa Simpang Pulai Main
Branch.
Table 6.1: Project Review
6.2 Highlight any novelties and contributions the project has achieved
First of all, the shop no need to rely on phone calling from those customers who
asking for breakdown assistant because customer can now use the application to pin the
location of their broken-down car. Secondly, the shop no need to worry on losing customers
who leave due to long waiting since the customers can now use the application to check on
what date and what time the shop is available for service booking and appoint to it, then
priority will be given to that customer. Last but not least, the shop no need to make us of
physical service reminder sticker to remind customers for next service due because
customer can now use the application to check for their “digital service reminder”.
102
6.3 Future Work

More advanced car breakdown assistant function might need in which the customer
able to know where is the current location of the mechanic that the admin sent out to assist
him time to time like what Grab Car is implemented. For service reminder, it can be more
advanced also by installing a hardware in the customer car that will update its mileage
value time to time to the server, so that customers no need to update it manually through
the mobile application.
103
REFERENCES
Md. Palash Uddin, Md. Zahidul Islam, & Md. Nadim, 2013. GPS-based Location Tracking
System via Android Device. International Journal of Research in Computer
Engineering and Electronics Volume 2 Issue 5 ISSN 2319-376X.
Honda Ireland, n.d. Service Reminder System Codes.
Available from:
<https://www.honda.ie/Page/119/servicing-reminder-system>
[20 Jul 2019]
M. A. F. Abdul Wahab, M. F. Ibrahim, & M. H. Mohd Latif, 2018. Authorised Service
Centre vs General Workshop: Consumers’ Preference of Car Maintenance. Journal
of the Society of Automotive Engineers Malaysia Volume 2, Issue 2, pp 151-156,
May 2018 e-ISSN 2550-2239 & ISSN 2600-8092.
Motorist Assurance Program, 2019. Service Reminder Light.
Available from:
<https://www.motorist.org/service-reminder-light/>
[20 Jul 2019]
paultan.org, 2017. Vehicle registrations in Malaysia hit 28.2 million units.
Available from:
<https://paultan.org/2017/10/03/vehicle-registrations-in-malaysia-hit-28-2-
million-units/>
[20 Jul 2019]

104
Swift SMS Gateway, 2017. How Automated Reminders Can Improve Automotive Service
Sales.
Available from:
<https://www.swiftsmsgateway.com/2017/09/13/how-automated-reminders-
can-improve-automotive-service-sales/>
[20 Jul 2019]
The Start Online, 2014. Car ownership in M’sia third highest in the world: Nielsen.
Available from:
<https://www.thestar.com.my/business/business-news/2014/04/16/car-ownership-
in-msia-third-highest-in-the-world>
[20 Jul 2019]
Trading Economics, n.d. Malaysia New Vehicles Registered.
Available from:
<https://tradingeconomics.com/malaysia/car-registrations>
[20 Jul 2019]
Universal Service Administrative Co., n.d. Geolocation Methods: A guide to successfully
collecting broadband deployment data.
Available from:
<https://www.usac.org/_res/documents/hc/pdf/tools/HUBBGeolocationMethods.p
df>
[20 Jul 2019]
105
APPENDIX A POSTER
APPENDIX A
POSTER
B-1
APPENDIX B PLAGIARISM CHECK RESULT
APPENDIX B
PLAGIARISM CHECK RESULT
B-1
B-2
B-3
B-4
B-5
Form Title : Supervisor’s Comments on Originality Report Generated by Turnitin
for Submission of Final Year Project Report (for Undergraduate Programmes)
Form Number: FM-IAD-005 Rev No.: 0 Effective Date: 01/10/2013 Page No.: 1of 1
FACULTY OF INFORMATION AND COMMUNICATION

TECHNOLOGY
Full Name(s) of WONG SAI KIT

Candidate(s)
ID Number(s) 16ACB01873
Programme / Course BACHELOR OF INFORMATION SYSTEMS (HONS) INFORMATION
SYSTEMS ENGINEERING
Title of Final Year Project ONLINE CAR MECHANIC SHOP SYSTEM
Similarity Supervisor’s Comments

(Compulsory if parameters of originality exceeds
the limits approved by UTAR)
Overall similarity index: 9%
Similarity by source
Internet Sources: 4%
Publications: 0%
Student Papers: 8%
Number of individual sources listed of

more than 3% similarity: 0
Parameters of originality required and limits approved by UTAR are as Follows:
(i) Overall similarity index is 20% and below, and
(ii) Matching of individual sources listed must be less than 3% each, and
(iii) Matching texts in continuous block must not exceed 8 words
Note: Parameters (i) – (ii) shall exclude quotes, bibliography and text matches which are less than 8 words.
Note Supervisor/Candidate(s) is/are required to provide softcopy of full set of the originality
report to Faculty/Institute
Based on the above results, I hereby declare that I am satisfied with the originality of the
Final Year Project Report submitted by my student(s) as named above.
______________________________ ______________________________
Signature of Supervisor Signature of Co-Supervisor
Name: DR. MANORANJITHAM A/P MUNIANDY Name:
Date: 24 APRIL 2020 Date:
B-6
APPENDIX C CHECKLIST FOR FYP2 THESIS
SUBMISSION
UNIVERSITI TUNKU ABDUL RAHMAN
FACULTY OF INFORMATION & COMMUNICATION
TECHNOLOGY (KAMPAR CAMPUS)
CHECKLIST FOR FYP2 THESIS SUBMISSION
Student Id 16ACB01873
Student Name WONG SAI KIT
Supervisor Name DR MANORANJITHAM A/P MUNIANDY
TICK (√) DOCUMENT ITEMS

Your report must include all the items below. Put a tick on the left column after you have
checked your report with respect to the corresponding item.
√ Front Cover
√ Signed Report Status Declaration Form
√ Title Page
√ Signed form of the Declaration of Originality
√ Acknowledgement
√ Abstract
√ Table of Contents
√ List of Figures (if applicable)
√ List of Tables (if applicable)
List of Symbols (if applicable)
√ List of Abbreviations (if applicable)
√ Chapters / Content
√ Bibliography (or References)
√ All references in bibliography are cited in the thesis, especially in the chapter
of literature review
√ Appendices (if applicable)
√ Poster
√ Signed Turnitin Report (Plagiarism Check Result – Form Number: FM-IAD-005)
*Include this form (checklist) in the thesis (Bind together as the last page)
I, the author, have checked and confirmed Supervisor verification. Report with
all the items listed in the table are included incorrect format can get 5 mark (1 grade)
in my report. reduction.
______________________ ______________________
(Signature of Student) (Signature of Supervisor)
Date: 23 APRIL 2020 Date: 24 APRIL 2020
C-1

16acb01873 Fyp

Uploaded by

Copyright:

Available Formats

16acb01873 Fyp

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

16acb01873 Fyp

Uploaded by

Copyright:

Available Formats

ONLINE CAR MECHANIC SHOP SYSTEM

REPORT STATUS DECLARATION FORM

Title: ONLINE CAR MECHANIC SHOP SYSTEM

Academic Session: JAN 2020

I WONG SAI KIT

declare that I allow this Final Year Project Report to be kept in

Date: 23 APRIL 2020 Date: 24 APRIL 2020

ONLINE CAR MECHANIC SHOP SYSTEM

Name : WONG SAI KIT

Date : 23 APRIL 2020

Figure Number Title Page

Table Number Title Page

AWS Amazon Web Service

1.2 Background and Motivation

Figure 1.2.1: Amount of different type of vehicles in different states of Malaysia up to

Above mentioning are so-called “outdated” practices of a local normal mechanic

(Source: Wahab, Ibrahim & Latif 2018)

2. To provide solution in terms of incorporation of GPS coordinate to locate

3. To provide solution in terms of service booking to help customers of Pusat

4. To provide solution in terms of service reminder to notify customers of Pusat

5. To validate the prototype by deploying it in Pusat Servis Tayar Dan Kereta

1.4 Proposed Approach / Study

Figure 1.4.1: Proposed Approach

1.5 Highlight of What Have Been Achieved

Seeking for Car Breakdown Assistant

Booking for Service(s)

Reminder for Next Service(s)

1.6 Report Organization

CHAPTER 2 LITERATURE REVIEW

Figure 2.1.1: Service Reminder Light

Figure 2.1.2: Honda Service Reminder Codes

2.1.3 Solution 2 - SMS Reminder System (Swift SMS Gateway, 2017)

2.2 Literature Review on Researches about Practices on Capturing Coordinates Data

Figure 2.2.1: Existing Project Use Case Diagrams

Figure 2.2.2: Existing Project Level 1 Data Flow Diagram

Figure 2.2.3: Existing Project Outcome

2.2.2 GPS (Universal Service Administrative Co., n.d.)

1. Open the web-based map.

2.2.4 Address Geocoding (Universal Service Administrative Co., n.d.)

Figure 2.2.4: Address Geocoding

2.3 Data Collection

Interview & Findings

mentioning by them is Outdoor Service

CHAPTER 3 SYSTEM DESIGN

1. Customers able to perform user authentication using registered email/password,

3.2 Block Diagram

Figure 3.2.1: System Block Diagram

3.3 Use Case Diagram

Figure 3.3.1: Use Case Diagram

3.4 Use Case Description

Alternate/Exceptional Flows 1a1 Customer choose to login using Facebook account

Table 3.1: Description for User Auth Use Case

3.4.2 Manage Profile Use Case

Alternate/Exceptional Flows 1a1 Customer choose to update cover picture

Table 3.2: Description for Manage Profile Use Case

3.4.3 Update Car Mileage Value Use Case

Alternate/Exceptional Flows 2a1 System display error message

3.4.4 Make Service Booking Use Case

Alternate/Exceptional Flows 2a1 System display error message