Internet Based Android Application for Vehicle Maintenance and Services

(Vehicle Relief)

Muhammad Ziaullah

Furqan Shahid

Shamshad Hussain

Waseem Mukhtar

Supervised By

Ms. Bushra Khan

Submitted for the partial fulfillment of B.S in Software Engineering degree to

the Faculty of Engineering & Computer Science

NATIONAL UNIVERSITY OF MODERN LANGUAGES ISLAMABAD

October, 2019
 ABSTRACT

It is common to get stuck with a faulty vehicle having problems such as run out of fuel,
technical defects or sometimes one may not have time to get your vehicle to the service station.
A faulty vehicle leaves the driver with missed appointments and stress. This “Internet Based
Android Application for Vehicle Maintenance and Services” provides services to the people
using cars and motorcycles whenever needed.

In this system Google maps API is used for the map and navigation, Firebase API is used for
the database, Google Play services API is used for the compatibility of system with new
updated android versions, GitHub API is used by android studio to auto backup code and the
Google text to Speech API is used for the voice order. The best compatible environment for
this system is above android marshmallow 6.0. Running the system on android version below
6.0 may result in system crash or some of the features may not work properly. The system uses
Firebase mobile number authentication for user registration.

This system has been developed by using Android Studio and Firebase for Database. The
System has been tested on many of the latest android smartphones. System testing and
regression testing are done manually by using test cases whereas unit testing is done by the
developer to ensure the quality and stability of the developed system.

i
 CERTIFICATE
Dated: ________________

Final Approval

It is certified that project report titled “Internet Based Android Application for Vehicle
Maintenance and Services” submitted by Muhammad Ziaullah, Furqan Shahid,
Shamshad Hussain and Waseem Mukhtar for the partial fulfillment of the requirement of
“Bachelor’s Degree in Software Engineering” is approved.

COMMITTEE

Dr. Muhammad Akbar

Dean Engineering & CS Signature: _____

Col(R) Engr. Jamil Ahmad Zia

HoD Engineering Signature:

Engr. Sumaira Nazir

Head Project Committee Signature:

Ms. Bushra Khan

Supervisor Name Signature:

ii
 DECLARATION
We hereby declare that our dissertation is entirely our work and genuine / original. We
understand that in case of discovery of any PLAGIARISM at any stage, our group will be
assigned an F (FAIL) grade and it may result in withdrawal of our Bachelor’s degree.

Group Members Signatures

1. Muhammad Ziaullah ___________________

2. Furqan Shahisd ___________________

3. Shamshad Hussain __________________

4. Waseem Mukhtar __________________

iii
 PLAGIARISM CERTIFICATE
This is to certify that the project entitled “Internet Based Android Application for Vehicle
Maintenance and Services”. This is being submitted for the award of the “Degree of
Bachelors” in “Software Engineering”. This is the result of the original work by
Muhammad Ziaullah, Furqan Shahid, Shamshad Hussain and Waseem Mukhtar under
my supervision and guidance. The work embodied in this project has not been done earlier
for the basis of award of any degree or compatible certificate or similar title of this for any
other diploma/examining body or university to the best of my knowledge and belief.

Turnitin Originality Report

Processed on 26-Sep-2019 02:31PM (UTC+0500)
ID: 1178182410
Word Count: 10504
Similarity Index
14%
Similarity by Source
Internet Sources:
3%
Publications:
0%
Student Papers:
12%

________________________
Bushra Khan (Supervisor)

iv
 TURNITIN ORIGINALITY REPORT
Internet Based Android Application for Vehicle Maintenance and Services From
projects (BSSE)
Processed on 26-Sep-2019 02:31PM (UTC+0500)
ID: 1178182410
Word Count: 10504
Similarity Index
14%
Similarity by Source
Internet Sources:
3%
Publications:
0%
Student Papers:
12%

SOURCES:
10% match (Student papers)
Submitted to Higher Education Commission Pakistan
1% match (Internet Source)
prodmrright.azurewebsites.net
1% match (Internet Source)
www.carcrew.in
4. <1% match (student papers)
Submitted to Texas A & M University, Kingville

5. <1% match (Internet Source)

www.timesaverz.com

6. <1% match (Student Paper)

Submitted to La Trobe University

7. <1% match (student papers)

Submitted to Sunway Education Group

8. <1% match (Student Paper)

Submitted to HELP UNIVERSITY

v
9. <1% match (Internet Source)

porto.polito.it

10. <1% match (Student Paper)

Submitted to Colorado Technical University Online

11. <1% match (Internet Source)

acikerisim.deu.edu.tr

12. <1% match (Internet Source)

www.cs.vu.nl

13. <1% match (Internet Source)

www.ijarse.com

14. <1% match (Student Paper)

Submitted to University of East London

15. <1% match (Student Paper)

Submitted to Kolej Universiti Linton

vi
 TABLE OF CONTENT
CHAPTER 1 ............................................................................................................................. 1

1.0 Introduction .......................................................................................................................... 2

1.1Internet Based Android Application for Vehicle Maintenance and Services System .......... 2

1.2 Aims and Objectives ............................................................................................................ 3

1.3 Scope of Developed System ................................................................................................ 3

1.4 Features of Developed System............................................................................................. 3

1.4.1 Making Selection and Placing Order ................................................................................ 3

1.4.2 Navigation for Customers and Employees ....................................................................... 4

1.4.3 Calculations....................................................................................................................... 4

1.5 Resource Requirements ....................................................................................................... 4

1.5.1 Software requirements ...................................................................................................... 4

1.5.1.1 Android Studio ............................................................................................................... 5

1.5.1.2 Data Manipulator ........................................................................................................... 5

1.5.2 Hardware Requirements.................................................................................................... 5

1.5.2.1 Android Based Smart Phones ........................................................................................ 5

1.5.2.2 Desktop Based Systems ................................................................................................. 5

1.6 Structure of the Report ......................................................................................................... 5

CHAPTER 2 ............................................................................................................................. 6

2.0 Introduction .......................................................................................................................... 7

2.1 Background of Vehicle relief ............................................................................................... 7

2.2 Existing System ................................................................................................................... 7

2.2.1 CarCrew ............................................................................................................................ 7

2.2.1.1 Limitations of Existing Systems .................................................................................... 7

2.2.2 Mr.Right ............................................................................................................................ 7

2.2.2.1 Limitations of Existing Systems .................................................................................... 8

2.2.3 TimeSaverz ....................................................................................................................... 8

vii
2.2.3.1 Limitations of Existing Systems .................................................................................... 8

2.3 Functional Requirements ..................................................................................................... 8

2.3.1 Login/Register................................................................................................................... 8

2.3.2 Selected Options ............................................................................................................... 8

2.3.3 Customer Side Options ..................................................................................................... 9

2.3.3 Place Order through Voice................................................................................................ 9

2.3.4 Employee Side Options..................................................................................................... 9

2.4 Non-Functional Requirements ........................................................................................... 10

2.4.1 Reliability........................................................................................................................ 10

2.4.2 Security ........................................................................................................................... 11

2.4.3 Maintainability ................................................................................................................ 11

2.4.4 Portability........................................................................................................................ 11

2.4.5 Usability .......................................................................................................................... 11

2.4.6 Testability ....................................................................................................................... 11

CHAPTER 3 ........................................................................................................................... 14

3.0 Introduction ........................................................................................................................ 14

3.1 Flow Chart ......................................................................................................................... 15

3.2 Use Case............................................................................................................................. 18

3.2.1 Registration Use Case ..................................................................................................... 19

3.2.2 Accept Order Use Case ................................................................................................... 19

3.2.3 Job Done Use Case ......................................................................................................... 20

3.2.4 Rating Use Case .............................................................................................................. 20

3.2.5 Place Order Use Case...................................................................................................... 21

3.2.6 Activate User Use Case .................................................................................................. 21

3.2.7 View User Profile Use Case ........................................................................................... 22

3.2.8 Voice Order Use Case ..................................................................................................... 22

3.3 Sequence Diagram ............................................................................................................. 23

viii
3.3.1 Customer and Employee Registration ............................................................................ 23

3.3.2 Accept Order ................................................................................................................... 24

3.3.3 Place Order...................................................................................................................... 24

CHAPTER 4 ........................................................................................................................... 26

4.0 Introduction ........................................................................................................................ 27

4.1 Development Walkthrough ................................................................................................ 27

4.2 Design of the Application .................................................................................................. 28

4.3 Employee and Customer Registration ............................................................................... 28

4.4 Placing Order ..................................................................................................................... 28

4.4.1 Selection Method ............................................................................................................ 29

4.4.2 Voice Method.................................................................................................................. 29

4.5 Calculate cost ..................................................................................................................... 29

4.6 Component Diagram .......................................................................................................... 29

4.7 Activity Diagram ............................................................................................................... 30

4.7.1 Customer Activity Diagram ............................................................................................ 30

4.7.2 Employee Activity Diagram ........................................................................................... 33

4.7.3 Admin Activity Diagram ................................................................................................ 34

4.8 Deployment Diagram ......................................................................................................... 35

4.9 State Machine Diagram...................................................................................................... 36

4.9.1 Customer State Machine Diagram .................................................................................. 36

4.9.2 Employee State Machine Diagram ................................................................................. 37

4.9.3 Admin State Machine Diagram ...................................................................................... 38

CHAPTER 5 ........................................................................................................................... 39

5.0 Introduction ........................................................................................................................ 40

5.1 Test Cases .......................................................................................................................... 40

5.1.1 Registration in Application ............................................................................................. 40

5.1.2 Admin Sign In ................................................................................................................. 42

ix
5.1.3 Place Order...................................................................................................................... 43

5.1.4 Accept Order or Reject Order ......................................................................................... 44

5.1.5 Check History ................................................................................................................. 44

5.1.6 Voice Order ..................................................................................................................... 45

5.2 Difficulties during Testing and Implementation ................................................................ 46

CHAPTER 6 ........................................................................................................................... 48

6.0 Introduction ........................................................................................................................ 49

6.1 System Overview ............................................................................................................... 49

6.2 Limitation ........................................................................................................................... 50

6.3 Future Work ....................................................................................................................... 50

6.3.1 Payment Method ............................................................................................................. 50

6.3.2 Including More Vehicles................................................................................................. 50

6.3.3 Order Scheduling ............................................................................................................ 51

6.3.4 Voice auto place order .................................................................................................... 51

6.3.5 Language Option ............................................................................................................. 51

6.3.6 Cost Custom Setting ....................................................................................................... 51

6.3.7 Contacting with a greater firm ........................................................................................ 51

6.3.8 Transection Record ......................................................................................................... 52

6.3.9 Complaints ...................................................................................................................... 52

6.3.10 Area Increase ................................................................................................................ 52

6.3.11 Car Rental ..................................................................................................................... 52

APPENDCIES ........................................................................................................................ 53

Appendix I User Manual .......................................................................................................... 53

References ............................................................................................................................... 56

x
 LIST OF FIGURES

Figure Caption
Page

3. 1 System Flow Chart Diagram ........................................................................................... 164

3. 2 System Flow Chart Diagram ........................................................................................... 175
3. 3 Use Case Diagram........................................................................................................... 186
3. 4 Vehicle Relief Sequence Diagram for Customer and Employee Registration ............... 242
3. 5 Vehicle Relief Sequence Diagram for Accept Order Use Case ...................................... 242
3. 6 Vehicle Relief Sequence Diagram for Place Order Use Case ........................................ 253
4.1 Vehicle Relief Component Diagram ................................................................................ 308
4. 2 Vehicle Relief Activity Diagram for Customer .............................................................. 320
4. 3 Vehicle Relief Activity Diagram for Employee ............................................................. 342
4. 4 Activity Diagram for Admin ........................................................................................... 353
4. 5 Vehicle Relief Activity Diagram for Admin .................................................................. 364
4. 6 Vehicle Relief State Machine Diagram for Customer .................................................... 375
4. 7 Vehicle Relief State Machine Diagram for Employee ................................................... 386
4. 8 State Machine Diagram for Admin ................................................................................. 386

xi
 LIST OF TABLES

Table Caption
Page

3. 1 Registration ..................................................................................................................... 197

3. 2 Accept Order ................................................................................................................... 197
3. 3 Job Done ......................................................................................................................... 208
3. 4 Rating .............................................................................................................................. 208
3. 5 Place Order........................................................................................................................ 19
3. 6 Activate User .................................................................................................................... 19
3. 7 View User Profile ........................................................................................................... 220
3. 8 Voice Order ..................................................................................................................... 220
5. 1 Registration of Application Test Case .............................................................................. 39
5. 2 Admin Sign in Test Case .................................................................................................. 40
5. 3 Place Order Test Case ..................................................................................................... 431
5. 4 Accept or Reject Order Test Case ................................................................................... 442
5. 5 Check History Test Case ................................................................................................. 443
5. 6 Voice Order Test Case .................................................................................................... 453

xii
 CHAPTER 1

INTRODUCTION
1.0 Introduction
This current chapter is an introduction to the developed system. In this chapter is going to
tell you about the basic functionalities of the developed system, aims and objectives that
why the system is developed, scope of the developed system to understand the value of the
system. Also, this chapter will give information about the features of the developed system
and how much resources are required to build this software system. The structure of the
report is also going to be discussed in this system. As this is an introductory chapter so this
will provide an overview of the developed system and its features and functionalities.

1.1 Internet Based Android Application for Vehicle

Maintenance and Services System
The Developed system has additional features to provide help to the user. “Vehicle Relief”
is installed on the user smart phone so they can get help each and every time it is requisite.
There is no need to go to the mechanic or waste your significant time on service stations.
User can hire mechanic or driver by using this this developed system through internet,
which can save the user time. “Vehicle Relief” provides solution for the problems to repair
vehicle and other automobile related problems. On a click, one can perform many
functionalities provided by the developed system. User can select their required features
then it is processed by the application and provide quick response to the user. As soon as
the user gets response from the application, ones problem is answered ASAP. Employees
makes sure that users are satisfied with their work and give them a good rating. The
application has following functionalities.

1. Motor repair
2. Bike/Car wash
3. Fuel order
4. Mobil Oil change
5. Vehicle Accessory order
6. Hire a driving teacher
7. Hire a driver
8. Voice order place
9. For Employment

2
1.2 Aims and Objectives
The focus of vehicle relief is to provide help to the user related to their vehicles. User should
have internet to access these functionalities. User need internet to contact ones nearest
service provider so that Employee can help Customer with the vehicle related problem
through this application. Because users feel uncomfortable to visit and wait for the
mechanic or face many difficulties on their way. This application can help user to
overcome/reduce their problems and provide them safe journey. Voice message is also
provided for the non-technical users. Those users who do not know much about this
application or facing any difficulties using this application we have provided them the voice
recognition.

1.3 Scope of Developed System

This application is developed to save time and help them to get rid of their problems without
wasting much time. This system is developed to relief the problem relevant to the vehicles.
All android users can use this system. Because this system is developed for android users.
Every person can use this system to get benefits from this system. There are no restrictions
for technical or non-technical user to use system. This system is providing users to have
safe and comfortable journey. Users can fulfill their needs with the help of vehicle relief
and to reduce their vehicle related problems. Users can solve their vehicle related problems
by just sitting at their home or office only by using this system. Also, there are some
application but they did not give one this much.

And they have limited functionalities in them. This system is providing all those
functionalities at your finger.

1.4 Features of Developed System

There are some system requirements for different modules to work. These requirements
are mentioned below:

1.4.1 Making Selection and Placing Order

First the user can select ones required functionality. User is able to choose ones vehicle
type from the given options. After that one can be given further choices according to given
choices one has to select the needed one and proceed the next step. User have to choose

3
only those that Customer needed for the vehicle. When the selections, user have to double
check ones selected functionalities and after that one can place the order.

1.4.2 Navigation for Customers and Employees

In this system maps and navigations have a vital role. When the Customer places order,
user have to make sure that ones navigation is on. Otherwise cannot work properly and
may result in crash. Because without navigation users location would not be shown to
Customer.

After that system searches for the available Employees in that area. When searching is done
system shows the user the nearest Employee and then the user selects that Employee. User
location is sent to the selected Employee with the profile information. In the same way
Customer can get the location of the Employee along with Employees profile information
who is coming for the help.Likewise, the driver provided by this service is navigated
through the map so one should know the location of your vehicle and belongings. In this
way user can get to know that where ones car is.

1.4.3 Calculations
When all the work done by Customer and Employee click on job complete button in this
application. When the service is provided and the Customer is satisfied with the work.
Employee and Customer can both give feedback according to their satisfaction. Employee
checks the services provided and confirm it from user for satisfaction which finalizes the
total cost Customer has to pay. Hand to payments are done by the Customer to Employee.

1.5 Resource Requirements

Like other systems, this system also needs some resource requirement achieve the goal.
Some software and hardware assets are required to complete the project. The software
platforms and hardware tools and equipment which are needed to develop the project are
being described. Following are the software and hardware requirements,

1.5.1 Software requirements

The programming language used for developing the application is Java with OOP concepts
(For Android application Development).

Following tools and technology are required for development:

4
1.5.1.1 Android Studio
In software engineering android studio is a platform for IDE (integrated development
environment). A base work environment includes for modifying the environment. For the
development of android based application, it is used which applications can be installed
and run on android devices, such as android based smart phones or mobile phones. Android
Studio is basic to software to develop android application. [6]

1.5.1.2 Data Manipulator

To store the users data, Firebase database is used. Firebase frees developers to focus
crafting fantastic user experiences rather than wasting time crafting it. Firebase can help one
manage servers automatically. Firebase is providing built in API so that one does not waste
time to write them. Firebase is not just a database server, it also provides mobile number
and email address verification code for users ease. [6]

1.5.2 Hardware Requirements

We need hardware resources to test this application. For the running and the testing of the
application which hardware resources are required those are as follows.

1.5.2.1 Android Based Smart Phones

An android based smart phone is required with a minimum four GB internal memory and
one GB of RAM. Smartphones having given specification do not get any problems using
this application however phones with less specs face several problems.

1.5.2.2 Desktop Based Systems

A desktop system with an operating system also required for the development of the
application. Developer have used devices (tab, laptop) with built in 4GB RAM and
minimum core-i3 processor to run android studio.

1.6 Structure of the Report

Based on the structure of system the report is separated into some different parts. In the
first chapter introduction of the developed system is given briefly, the next part provides
the concise history of existing systems and how developed system prevail over those
problems with reference to the journalism analysis. It has also incorporated the particular
requirements with complete scope of the system. System modeling techniques are also
available in the report involving the use cases and sequence diagrams of the system.

5
 CHAPTER 2

BACKGROUND AND EXISTING SYSTEM

6
2.0 Introduction
In this chapter background about the vehicle related issue and the detailed outline of the
developed system has been described. Limitations of existing systems are discussed and
existing systems are evaluated in detail. The outline of the developed system gives the
knowledge about features and new techniques of the system.

2.1 Background of Vehicle relief

As everyone is using vehicles now a days and there was no application available on the
android platform to provide help for vehicle related problems. There are some websites
working for this problem so we got this idea from those to create an android application.
But they have some limitation in them. Some of the existing systems and their limitations
are defined in the next phase.

2.2 Existing System

There are several existing systems available in the market with limited functionalities. The
detail of few such systems are mentioned as follows:

2.2.1 CarCrew
Carcrew is Indias first standardized network of workshops-based website to provide car
services. They provide transparent and convenient on-demand car services at your home or
your office. With expert mechanics, state-of-the-art machinery, top quality spares,
standardized processes & pricing, Carcrew provides a uniform service experience to all its
Customers, across its workshops. Everything under one-roof: servicing, repairs,
inspections, denting/painting, roadside assistance and car care. [1]

2.2.1.1 Limitations of Existing Systems

It is not available for android or IOS. Employee does not contact through website rather
they contact through organization. It does not provide services like driver and fuel delivery.

2.2.2 Mr.Right
Mr. Right is and android based Indian application that connects one with the best car wash
services in your locality to make your car spotless and give it a brand-new look all over
again. This car wash professionals use only high-quality products to clean and polish your

7
car - inside and outside. This service includes high pressure cleaning, interior vacuum and
dry clean, Teflon coating, and exterior detailing services that are unparalleled. It is the best
way to make yourself fall in love with your car, all over again. Mr. Right offers a
comprehensive range of car wash services including interior detailing, exterior detailing,
waxing and Teflon coating. [2][3]

2.2.2.1 Limitations of Existing Systems

Motor repair, oil change and other functionalities are not provided by Mr. Right. It only
provides car wash service which is relevant to this system. But their system is lacking in
lacking in providing other functionalities.

2.2.3 TimeSaverz
Timesaverz is an IOS based app that gets curated service providers to your doorstep for
various home services ranging from cleaning, Car wash, pest control, repairs, and
handyman jobs. They do this so that one can spend your time following your passions and
doing things one actually loves rather than running around for mundane tasks. [4]

2.2.3.1 Limitations of Existing Systems

It is not available on web or android. It orders a driver; oil change and other services are
not available. It provides only car wash services.

2.3 Functional Requirements

Following are the functional requirements of the developed system.

2.3.1 Login/Register
The user can Login if one has an account or Register in case of new user. User can
register through ones mobile number and add email address for later logging in.

2.3.2 Selected Options

User is asked to select user type when the application is opened.

User had to select ones user type from the given options (Customer, Employee or
Admin).

User can only select one at a time whether one can select Customer side or Employee side
or Admin side depending upon the user usage purpose.

8
2.3.3 Customer Side Options
If the user selects Customer side then Customer is asked to choose from a vehicle (Bike
or Car) for which one need this service.

Select Features and provide details:

After selecting ones vehicle user is asked to select the needed services that they need.
User is asked to provide relevant details like which part of the vehicle need repairing,
which washing plan would one like, how much fuel do one need, which brand oil would
one prefer and what accessories one need etc. User can also select multiple functionalities
if they need.

Add location
After setting date and time user is asked to set a location where this Employee shall arrive
for help. User must check that ones navigation location is turned on. Otherwise system asks
the permission to do so.

Placing order
Setting the navigation and placing the order redirects the user to map where one is shown
multiple available Employees in that particular area which are available at that point. User
can also see that Employees information and details.

2.3.3 Place Order through Voice

In any case of emergency, the user can place the order through voice. If user is having some
trouble using this application then one can also place the order through voice recognition
or one did not want to waste the time.

2.3.4 Employee Side Options

If user want to be a part of this system than one selects “Employee” option. On selection
of this option one is directed to a new page where one needs to provide ones contact details.
After getting job successfully from the organization. Employee can now register himself in
Employee side through a verification from the Administration.

Registration code
If user want to be an Employee in your organization one has to give an interview on the
given address. If one is accepted by the organization one has to register through mobile
OTP code through which one can start as an Employee after getting verification from the

9
Admin side. That authentication ensures that all the information is authorized by the
organization.

Enter Registration code

After entering the registration code and providing all the details and information about
himself, Employee is directed to a screen with a map where one can receive orders from
the Customers.

Accept or decline order

When a Customer confirms an order it is display on the screen of the relevant Employee
one had the authority to accept the order or leave it for someone else. If one tends to accept
the order one is provided with Customer details.

Finalizing cost
When Employee is finished with work and Customer is satisfied, Employee had to select
the job done and cost is displayed on both ends (Customer and Employee).

Feedback
When both are satisfied with each other they can rate each other and terminate the order.

2.4 Non-Functional Requirements

For making the quality product non-functional requirements are extremely important to
believe. These necessities incorporate an arrangement of qualities which are increasingly
or less integrated into the greater part of the product requirements.

These basics are not clearly provided by the client. Programming engineer process and
judge their nearness and need by the various systems and on the support of understanding.
Increasingly these characteristics are satisfied progressively and the quality is guaranteed.

2.4.1 Reliability
In any requirement the reliability of the system is significant. Dependability is characterized
as indicate time among disappointments. It involves that a system is more solid on the off
chance that it is accessible for a long time and disappointment rate is less.

Developed system is solid since expectation of the developed system are all the meets the
user demand and client can get to the system at any time by utilizing ones android smart
phone.[5]

10
2.4.2 Security
The coding of the developed system is done in such way that comments provided against
each line, so later on new functionalities can be added in the system easily to meet the user
need or on the market demand. The developed system is exceptionally adaptable. [5]

2.4.3 Maintainability
The coding of the proposed system is done in such way that comments provided against
each line, so later on new functionalities can be added in the system easily to meet the user
need or on the market demand. The proposed system is exceptionally adaptable. [5]

2.4.4 Portability
“Vehicle Relief” is compatible with different smartphones. Application is compatible with
latest and older versions of android platforms. It can also be transferred from one device to
another using file transferring software. [5]

2.4.5 Usability
“Vehicle Relief” provides user friendly interface to the user. User can easily understand
functionality of the application. This application is designed for all type of users who
interact with the application. The application is easy to use and understand for a completely
new user of the android. [5]

2.4.6 Testability
“Vehicle Relief” is testable for all cases. The system designs in such a way that tester can
easily develop test cases for the system that implement those test cases on the system to
check the systems efficiency and complete the testing process of system.

The flow of the application is very user friendly that can help a lot in testing process. The
coding style and methodology is kept professional so if the software is tested internally it
can easily be tested. [5]

11
Non functional requiremnts

Non-Functional Requirements
non-functional requirements are extremely important to believe. These necessities
incorporate an arrangement of qualities which are increasingly or less integrated into the
greater part of the product requirements.

These basics are not clearly provided by the client. Programming engineer process and
judge their nearness and need by the various systems and on the support of understanding.
Increasingly these characteristics are satisfied progressively and the quality is guaranteed.

2.4.1 Reliability
In any requirement the reliability of the system is significant. Dependability is characterized
as indicate time among disappointments. It involves that a system is more solid on the off
chance that it is accessible for a long time and disappointment rate is less.

Developed system is solid since expectation of the developed system are all the meets the
user demand and client can get to the system at any time by utilizing ones android smart
phone.[5]

2.4.2 Security
The coding of the developed system is done in such way that comments provided against
each line, so later on new functionalities can be added in the system easily to meet the user
need or on the market demand. The developed system is exceptionally adaptable. [5]

2.4.3 Maintainability
The coding of the proposed system is done in such way that comments provided against
each line, so later on new functionalities can be added in the system easily to meet the user
need or on the market demand. The proposed system is exceptionally adaptable. [5]

12
2.4.4 Portability
“Vehicle Relief” is compatible with different smartphones. Application is compatible with
latest and older versions of android platforms. It can also be transferred from one device to
another using file transferring software. [5]

2.4.5 Usability
“Vehicle Relief” provides user friendly interface to the user. User can easily understand
functionality of the application. This application is designed for all type of users who
interact with the application. The application is easy to use and understand for a completely
new user of the android. [5]

2.4.6 Testability
“Vehicle Relief” is testable for all cases. The system designs in such a way that tester can
easily develop test cases for the system that implement those test cases on the system to
check the systems efficiency and complete the testing process of system.

The flow of the application is very user friendly that can help a lot in testing process. The
coding style and methodology is kept professional so if the software is tested internally it
can easily be tested. [5]

13
 CHAPTER 3

SYSTEM MODELING

3.0 Introduction
A system model which shows the system in an abstract structure is known as the system
modeling. A system compromises numerous prospective for example, requirement
analysis, scheduling, employment, organization, performance, information records, and
yield information perspectives. This shows the graphical representation of the system
development. Many separated demonstrating plans developed to diverse intentions on
software development. These separate modeling strategies are utilized to demonstrate those
system conducts in distinctive routes. A use case diagram may be a standout amongst the
sorts from claiming modeling technique which is used to demonstrate the system in the
haul about client connection with those systems. A sequence diagram is also another
modeling technique utilized to demonstrate the system in terms of techniques for each other
and their succession/ sequence of event. Sequence diagrams indicate the forms within
expression about requesting/processes. Class diagrams are also a modeling technique
which is used to demonstrate the relationship between the classes.

14
3.1 Flow Chart
After opening the application and selection of the user type, the new user can register
himself then user is able to get advantage from application. Employee can register by the
Admin approval and Customer can register by providing mobile number to get OTP code
in application. Then Customer can select vehicle type and then one can select
functionalities and feature they want. User can select the particular location and company
provides one with an Employee to facilitate one. At the end cost is calculated by the system
and then they both can rate each. Another functionality is given for users in emergency that
they can place order through voice message.

Employees first have to get verified by the Admin before using Employee side and getting
orders from the Customers. Employee can view the orders on the application screen and if
one is interested in any order one can accept it by clicking on it. Employee had to complete
the job and then Employee and Customer can see the total amount on their screens.

Both Employee and Customer had to rate each other according to the performance and
behavior. Admin can login through specific code known only to that person. Admin is able
to view and see the Customers and Employee using this application. Admin has another
role to activate the status of Employee so that one can use the application.

Flow chart of the developed system is shown in the figure 3.1 and figure 3.2 respectively

15
Figure 3. 1 System Flow Chart Diagram

16
Figure 3. 2 System Flow Chart Diagram

17
3.2 Use Case
Use case diagram is a demonstration of a users relation with system which shows the
relationship between the users of the system and external users. These relationships can be
included relationship or extended relationship. Use case diagram can identify the types of
the system users and types of the use cases and frequently be come with different types of
diagrams too. Use case is movement or off chance which may be performs towards the
user. Use cases represent all the possible actions or procedures which an actor can execute
to cooperate with the system. It can be utilized to represent such activities / occasion which
an actor can execute on the system attaining an objective. Use cases are the simplest way
to represent the relationships between user and system and between internal and external
entities. Actor could a chance to be a mankind alternately a machine. It is shown in the
figure 3.3.

Figure 3. 3 Use Case Diagram

18
3.2.1 Registration Use Case
If user wants to use application. One must give the personal information to the system. One
can register the application after providing some information.

Table 3. 1 Registration

Use Case ID UC-01

Use Case Name Registration
Actors Employee, Customer, Admin
Purpose To register the Admin and User to the Application
Overview User can create account to update personal information

Type Primary
Pre-Condition Admin and User must fill all mandatory fields
Post-Condition Personal information is saved in database

3.2.2 Accept Order Use Case

When the Customer wants any help about the vehicle, one selects the Employee and then
Employee can give confirmation to accept order.

Table 3. 2 Accept Order

Use Case ID UC-02

Use Case Name Accept Order

Actors Employee

Purpose Confirmation of order from employee

Overview Customer has knowledge about employee that they are

accepting the order
Type Secondary

Pre-Condition Employee should be logged in and

Post-Condition online
Selected employee can response to the customer and
able to do customer work

19
 3.2.3 Job Done Use Case
When Customer the makes the order, an Employee gets there to do the work. Employee
had to press job done after the completion of the work.

Table 3. 3 Job Done

Use Case ID UC-03

Name Job Done

Actor Employee

Purpose To make sure of order completion.

Overview When employee should complete the order, one then had to press Job Done.

Type Primary

Pre-Condition Order must be available.

Post-Condition Order is completed.

3.2.4 Rating Use Case

Customer and Employee can rate the application that tells about the behavior of them with
one another.

Table 3. 4 Rating

Use Case ID UC-04

Name Rating

Actor Employee, Customer

Purpose To knowledge about the advantage of the application

Overview Employee and Customer can rate behaviour of the application.

Type Primary

Pre-Condition Employee must have done the job.

Post-Condition Rating should be done.

20
 3.2.5 Place Order Use Case
If Customer want to place order, one need to select different functionalities and related
features and press submit to place the order.

Table 3. 5 Place Order

Use Case ID UC-05

Name Place Order

Actor Customer

Purpose Customer can select ones order

Overview Customer can select different functionalities and features and confirm ones
order

Type Primary

Pre-Condition Customer should have registered to the application.

Post-Condition Order is confirmed and placed

3.2.6 Activate User Use Case

When a user register yourself to the application, Admin can activate one to be able to use
application. Without activation Employee cannot be able to get orders and one cannot get
advantage from application.

Table 3. 6 Activate User

Use Case ID UC-06

Name Activate User

Actor Admin

Purpose To give permission to user to use Application.

Overview Admin need to give permission to the user when they Register themselves to
the application.

Type Primary

21
Pre-Condition User must submit the registration form.

Post-Condition Users can use the application.

3.2.7 View User Profile Use Case

When the Customer and Employee register yourself, they need to submit their profile,
Admin can view their profile to give them permission to use application.

Table 3. 7 View User Profile

Use Case ID UC-07

Name View User Profile

Actor Admin

Purpose To View the users data for security.

Overview Users had to register; Admin can view their personal data.

Type Secondary

Pre-Condition User must have registered.

Post-Condition Admin is able to see the users profile.

3.2.8 Voice Order Use Case

This feature allows Customer to place order through voice message. This feature specially
provides help to the user in time of emergency.

Table 3. 8 Voice Order

Use Case ID UC-08

Name Voice Order

Actor Customer

Purpose In case of emergency this feature is very useful.

Overview Customer can place order just by sending a voice message.

22
Type Secondary or Optional

Pre-Condition Customer must be registered; Voice button must be pressed and customer
should clarify what they need.

Post-Condition Order placed successfully.

3.3 Sequence Diagram

The sequence diagram is an interaction diagram that shows the operations of a process step
by step. It also shows the relation of the objects with the time space. The sequence diagram
may be utilized principally to demonstrate the interactions between objects in the sequential
order in which those interactions are occurred.

UML grouping charts demonstrate the stream of rationale inside your framework in a visual
way, empowering one both to archive and approve your rationale, and are generally utilized
for both investigation and configuration purposes.

Arrangement outlines are the most mainstream UML relic for dynamic demonstrating,
which concentrates on distinguishing the conduct inside your framework.

Other dynamic displaying procedures incorporate movement graphing, correspondence

outlining, timing charting, and cooperation review outlining.

3.3.1 Customer and Employee Registration

Since a registration process require some user info so for the users of this application, they
also need to provide requested information.

It is compulsory for a Customer to provide mobile number for the verification. One needs
to give their personal info and save it for further use.

Now as for an Employee, one also need to give ones mobile number to gat OTP. Employee
enter the code in registration form and provide relative information and after verification
from Admin side Employee is authorized to use the application.

23
 Figure 3. 4 Vehicle Relief Sequence Diagram for Customer and Employee Registration

3.3.2 Accept Order

Now as far as the order placement is concerned. Whenever a Customer places an order
some nearby Employee gets notification and Employee had a choice to accept or reject
the order. To accept an order Employee needs to click on order showing on ones screen
and to reject an order Employee can leave it without doing anything.

Figure 3. 5 Vehicle Relief Sequence Diagram for Accept Order Use Case

3.3.3 Place Order

Order placement is an essential and most important part of this application. To place an
order a Customer can log in and select the required functionalities and relevant features
then provide further details like location and finally place the order. Placing an order
involves a process which include many steps explained throughout the report at various
places in different ways. Order placement requires no technical skills as the interface of

24
the application is kept quite easy to understand. Images, icons and labels are used to make
it easy for a non-technical or an uneducated user to easily grasp the working of the
developed application.

Figure 3. 6 Vehicle Relief Sequence Diagram for Place Order Use Case

25
 CHAPTER 4

DEVELOPMENT METHODOLOGY

26
4.0 Introduction
This chapter is going to be about the development mythology of Internet Based Android
Application for Vehicle Maintenance and Services with the help of latest and advanced
android development tools on personal computers and laptops. Well this chapter briefly
explains about the working of this android application. Main determination and
functionality of all the modules used in development of the project has been explained in
detail. Working and development methodologies are explained in this chapter using
diagrams and theoretical explanation.

4.1 Development Walkthrough

This application is running on only a single module. Most features of the application depend
upon one another in different ways. To get a good understanding of the developed system
the requirements of the application are analyzed. On the bases of the given requirements of
the stakeholders and users, this application is designed and initially structured. Now for the
development, coding and data storage purpose of the application Android Studio, java
programming and Firebase (database) are used.

The prototyping of the application is designed and evaluated by the supervisor. Prototyping
was done on Balsamiq tool. After evaluation some necessary changes are made in the
system prototype in the form of improvements and then move towards the next step which
is the final development and coding of the system. Well to develop an Android based
application Android Studio is Androids official IDE and that is what we used. It is a well-
organized tool for Android to accelerate your enhancement and it enables one to construct
a quality product for Android. The system user interface is kept user friendly and easily
understandable. To improve the understanding of the system user interface labels, icons
and images are frequently used. It is made so easy to learn and understand that any non-
technical or an uneducated person can also use this system without anyone else help.

It gadget is uniquely customized for Android engineers. It contains ironic code fluctuating,
troubleshooting, testing, and summarizing devices. Functions of the application are
developed separately and then are integrated to form a complete application. Java
programming language is used for coding of the system in Android Studio. As android
studio is the most reliable trusted and authentic source / tool for android development
provided by the Google itself. It is also quite easy to use and work with.

27
4.2 Design of the Application
Application is designed by keeping all the engineering Agendas in the mind. The design of
the application is finished by studying the existing systems, user needs and trending
projects in similar applications. First of all, the prototype of the system is designed and
evaluated by the users and then the related things like database are designed.

The application is developed on Android Studio and user interacts with different screens
while performing the actions in the application. So, dissimilar screens are designed to
advance the interaction between user and application. The application provides support to
the android phones and can be installed on all android based smart phones having android
version greater than Marshmallow 6.0. The interface of the application is kept as any other
typical Android application which is easily understood and used by the users of the
application.

4.3 Employee and Customer Registration

Registration is a process which is done in almost every application or system. The purpose
of registration is to create a unique id of the user to keep record of the activities and other
stuff.

The system verifies the number that user entered for registration by using firebase database
authentication. The user receives an OTP for verification through provided Verification
Code (mobile). Here the Firebase built in mobile number verification method is used. Using
mobile number to authenticate and verify the user is now a days very secure and easy as
user do not need to remember any password every time while logging in. After verification
user need to enter the required information which is saved to firebase database and
information is fetched from user by using fetch Value(auth.getUid()); method. Many other
methods and coding techniques are used in the development process.

4.4 Placing Order

Order placement require a bit of attention as Customer of the system can place order by
two different methods. Each method has its own pros and cons:

Selection Method

Voice Method

28
4.4.1 Selection Method
This method of order placement allow user to make selections in the application for their
required features and functionalities. These features and functionalities are shown in the
application by icons or images to make it easy for the Customer to understand and place
order. Location of the user is fetched by the application using google API. The GPS of the
Customer phone must be on before starting the application and while using it. Customer
location and the selections made by the Customer for placing the order is used to place
order. This order placement method is clearly specifying that what is required by the
Customer because of the distinction of the feature items.

4.4.2 Voice Method

Now for the users who are in any kind of emergency and do not have time to make
selections they can place order just through a voice message. This method is used to place
order through voice message. Customer can click on the mike icon given in the application
which allows one to speak and record message. Message is then converted into text form
through speech to text google support. That text message is then sent by the application to
the nearby Employee. Google speech to text API is used to covert the voice into text and
then read the text to place order. Location is automatically fetched by the application and
provided to the Employee.

4.5 Calculate cost

While selecting the functionalities, Customer is allowed to select multiple options, cost of
each functionality is given in front of every option while placing order. While making
selection user can see total amount on the screen of ones android smart phone. After the
order is done and Employee confirm of order completion final cost is displayed to the
Customer and Employee which is calculated by the application using calculation functions.
At the time being hard coded values are set in the system.

4.6 Component Diagram

Figure 4.1 illustrates the components of the developed system with the help of component
diagram. Components of the developed system include Authentication database, users
database, images storage data base are used by the system server. The utility component
performs all the processing of the system. Vehicle relief component is the main system
component which communicate with app the other components through system server.

29
Final is the user interface component of the developed system from where the user can
interact with the Application component.

Figure 4. 1 Vehicle Relief Component Diagram

4.7 Activity Diagram

Activity diagram show the activity flow of the developed system. As the developed system
has three user sides so to explain it in detail three diagrams are drawn. The diamond shape
is used of decision and merger.

Solid filled circle is the starting node of the activity. In an activity diagram the rounded
corner rectangle shows the activity of the developed system. Arrows with the pointing
direction show the flow of the application activities. The filled within an empty circle
illustrate the ending node of the activity flow.

4.7.1 Customer Activity Diagram

To explain the activity flow of the Customer side figure 4.2 is mentioned below. After the
selection of the customer from the user selection menu.

Customer need to provide it is contact number through which one should receive an OTP
to register. After providing the OTP Customer needs to fill the profile information form
with all the personal details required by the application and click save.

30
The Customer is now on the home screen of the application where one need to make a
selection for the type of vehicle or place the order through a voice message. If the Customer
select the voice button then application records the message and ask the Customer if the
order is oaky to be placed or it needs to be canceled.

Canceling the order directs the Customer to the main screen. Accepting the order leads to
order placing. On the other hand, making a selection from one of the vehicle types leads to
manually placing the order and making selection through different activities.

At the very end when the order is placed and the order has been accepted and completed
Customer can see the total amount of the work done and the payment is done by hand one
final activity id left to be completed.

The final activity that needs to be performed by the Customer side is to give the feedback
for the performance of the Employee. The Feedback action in the application is performed
through starts rating method. Customer need to rate the Employee by marking the number
of starts that meet ones satisfaction level and press submit. The submit button action
terminates the order process of the application.

31
Figure 4. 2 Vehicle Relief Activity Diagram for Customer

32
4.7.2 Employee Activity Diagram
For the explanation of the activity flow of the Employee side figure 4.3 is cited below. All
the activities that can be performed by the Employee using the developed system are
clarified in the given diagram.

The user needs to select the employee option at first, then the application requires the
mobile number. When the mobile number is provided the next activity is to wait for OTP
and as soon as the OTP arrives it can automatically be detected by the application if the sim
is in the same cellphone Employee just need to press the okay button but if the sim is in
some other phone then Employee needs to enter the OTP manually to precede from this
activity.

Then Employee needs to wait as the application cannot move to perform any activity until
Admin activates the status of that particular Employee. After the activation the next activity
is to wait for the Customer to place an order. If the order is placed Employee needs of select
it and if one do not want to accept it one can just leave it there.

Once the order is selected there can be two possibilities. That Customer had placed the
order through voice, in that case Employee needs to enter the price and complete the job
when it is done otherwise one just need to complete the job.

Well after the job is complete Employee needs to rate the Customer for behavior. As soon
as the rating is submitted the order is terminated and Application returns to the accept order
activity.

The diagram only displays the activities performed by the Employee, as some of the
activities may interlink with the other but those activities are mentioned in the relevant
diagrams.

Some of these activates include order placement from the Customer side and Status
activation form the Admin side both the activities are mentioned in the figure 4.2 and figure
4.4 respectively.

33
 Figure 4. 3 Vehicle Relief Activity Diagram for Employee

4.7.3 Admin Activity Diagram

In order to illustrate the Administration side activities, figure 4.4 is provided below. Well
the Admin of the application can perform the following activates as described below and
in the mentioned diagram.

User needs to select Admin option as the first activity then Admin had to enter the specific
code known only to Admin. The next activity for the admin is to select the user type for
whom one needs to check profile of activate status.

Admin can select either of the types and then one can see all the users of that particular
type. If Amin any of the Employee certified from the organization Admin can activate ones
status thus allowing one to use the features of the application.

34
 Figure 4. 4 Vehicle Relief Activity Diagram for Admin

4.8 Deployment Diagram

Figure 4.5 describes the deployment diagram of the developed system.

Deployment diagram shows the hardware aspects of the developed system. Main data
storage of the application is the Firebase server which holds all the records and data of the
system.

Then there is an Application server which performs the tasks given the User devices with
the help of Android application server. All the systems are connected through internet and
communicate through it to perform different tasks.

35
 Figure 4. 5 Vehicle Relief Deployment Diagram

4.9 State Machine Diagram

To explain the changing states of the developed system state machine diagram is used. To
elaborate the details furthermore, state machine diagram is divided into three sub parts as
per the system user types.

4.9.1 Customer State Machine Diagram

For the elaboration of the changing states on the Customer side of the application figure
4.6 is given below. The basic flow of the state machine diagram is same as the flow chart
diagram or activity diagram but here a much more detailed flow is given through changing
states of the developed system.Application starts with the state of selecting the user type in
present state user needs to select the Customer option. The next state is shown by the arrow
as registration form in that state mobile number is provided which triggers the next state
i.e. OTP form. If the provided OTP is correct then application proceeds to next state
otherwise Customer needs to reenter the OTP. In next state Customer had to fill in the
complete personal information in order to move to next state. Now the Home screen provide
Customer with two basic choices for order placement. One is to place order manually and
other is voice order placement. In order to place order using voice command, voice message
is recorded by the Customer which is them interpreted and converted into text form now in
this state Customer had to make a choice to place order using this voice message or to delete
it and replace order. If the Customer want to place order using manual selections Customer

36
had to go through many different order selection states to finally confirm order. Now
Customer needs to select the Employee to move on to next state i.e. when the Employee is
done with the order Customer will receive a message showing the total amount. Last state
of the Customer order is to rate the Employee performance.

Figure 4. 6 Vehicle Relief State Machine Diagram for Customer

4.9.2 Employee State Machine Diagram

To show the flow of the application from the Employee sides changing states figure 4.7 is
provided. The user of the application has selected the Employee as the user type at first
state of the application. After registration through mobile number same as the Customer
state diagram the next state for Employee is to wait for the Admin to activate Employee
status. After the activation of the Employee status from the Admin side Employee needs to
press Continue to move from present to next state. Then Employee needs to provide the
profile info and save to wait on the main screen for the Customer to place an order. Now if
the order is placed through voice command then Employee had to give in the price of the
work one needs to perform otherwise one just click on complete job after the job is done.
Next state of the application shows the total amount calculated and ends the employee state
with the rating of the Customer behavior.

37
 Figure 4. 7 Vehicle Relief State Machine Diagram for Employee

4.9.3 Admin State Machine Diagram

Figure 4.8 demonstrates the idea of the changing states of the Admin side. In this case user
needs to make a selection for the Admin state. Which then moves the application to the
next state of logging in through the specific code known only to Admin. The home screen
of the admin side allows Admin to view either of the users profile at a time from Customer
and Employee. Not only can Admin view their profiles also Admin can activate the status
of the users. Thus, allowing Employee to use the application.

Figure 4. 8 Vehicle Relief State Machine Diagram for Admin

38
 CHAPTER 5

RESULT/TESTING, ANALYSIS AND

VALIDATION

39
5.0 Introduction
Software testing plays a significant role in software development as it removes the errors
and bugs, improves the quality of the software eventually which leads to user satisfaction.
Testing is the procedure to evaluate the system by removing the errors and bugs from the
system in order to enhance the system creditability and performance. Software testing is a
tool to increase the quality of the system and to make it error free to meet the functional
and non-functional requirements of the software. So, a quality ensured system meet all the
requirements of the stakeholders. Errors cannot be totally removed from the system
however their effects can be minimized by evaluating or measuring the performance of the
system through some testing tools. Testing guaranteed the smooth running, increase
availability and creditability of the system.

5.1 Test Cases

An absolute system cannot be tried for every last single information and yield. Their are
numbers of modules which are included in a system, so test cases are planned for every
single module to check the success rate of each module. Each and every module is tested
independently and furthermore be tried when integration of the modules is done in order to
make it a complete system. Expected outputs of the system are defined already and
consequences of system behavior are noted and investigated with the experiments. A test
case comprises of the accompanying essential data inside the table. A test case ID is a sole
number for each of the individual test case. Use case reference is taken from the now built
use case, name of tester, results and comments are included in the table.

5.1.1 Registration in Application

To use the application first user have to Sign Up using mobile number. If user is a Customer
then one can Sign Up by providing number without first 0 and OTP (One Time Password)
is sent on the provided number. If the sim is in the same phone then application
automatically detects the OTP and proceed to profile form user had to type the OTP in the
option space. If the user is Employee one had to first Sign Up through OTP and then through
email.

Table 5.1 shows the details about Sign Up application. After getting Signed Up users are
shown a profile form which they have to fill and save the form to further use the application.

40
 Table 5. 1 Registration of Application Test Case

Test Case ID Use Case Reference QA Test Engineer Name of Personnel

TC-1 UC-01 Programmer M.Ziaullah

Test Date 17-04-2019

Revision History None

Objective To Sign Up and enter the application.

Environment User Mode

Assumptions User provide the number, receive OTP, get Signed Up and save
profile info.

Pre-Requisite User already downloads and installs the Internet Based Android
Application for Vehicle Maintenance and Services.

Step# Execution Description Procedure Result

1. Application is installed on the Application correctly installed on the

smart phone. users smart phone, user successfully
get Signed Up in the application and
User provide mobile number
2. profile info gets uploaded.
and enter OTP to get Sign
Up.

3. Employee provide first OTP

and then email to get Sign
Up.
4,
Provide profile info and press
save.

Comments User must enter the application to use it. User must enter phone
number without first 0 to get OTP code.

Status  Pass  Fail Not Executed

41
5.1.2 Admin Sign In
While if Admin want to check status of Customer or Employee one can Sign In suing
specific code which is only known by the Admin. Table 5.2 shows details about Admin
Sign In. One can manage and see Customer and Employee Info.

Table 5. 2 Admin Sign in Test Case

Test Case ID Use Case Reference QA Test Engineer Name of Personnel

TC-2 UC-02 Programmer M.Ziaullah

Test Date 17-04-2019

Revision History None

Objective To get Admin Signed In and manage Info.

Environment User Mode

Assumptions User write specific code known only to get one Signed In and
manage info.

Pre-Requisite User launches the application and has selected Admin mode.

Step# Execution Description Procedure Result

1. User select the Admin Admin is successfully Signed In and

Application mode. one is able to manage Customer and
Employee info.
User write the specific code
2.
in text are and proceed to
Sign In.

Admin manages the info of

Customer and Employee.
3.

Comments User must know the specific code to Sign In.

42
Status  Pass  Fail Not Executed

5.1.3 Place Order

If Customer want to place an order, one can select different functionalities and their
relevant features and then confirm to place order. Table 5.3 shows Place Order phase test
case.

Table 5. 3 Place Order Test Case

Test Case ID Use Case Reference QA Test Engineer Name of Personnel

TC-3 UC-06 Programmer M.Ziaullah

Test Date 17-04-2019

Revision History None

Objective To place order.

Environment User Mode

Assumptions User is already on the application; application is running and GPS

location is on.

Pre-Requisite User must select functionalities and their relevant features.

Step# Execution Description Procedure Result

1. User select functionalities and Order is successfully placed.

their relevant features.

User confirm selection to

2.
place order.

Comments User must select functionalities and their relevant features.

Status  Pass  Fail Not Executed

43
5.1.4 Accept Order or Reject Order
When user has placed order, nearest Employee gets the notification of the order. Employee
is having two options either to select order and complete it or to reject the order. Table 5.4
show the details of Accept or Reject order test case.

Table 5. 4 Accept or Reject Order Test Case

Test Case ID Use Case Reference QA Test Engineer Name of Personnel

TC-2 UC-03 UC-04 Programmer M.Ziaullah

Test Date 17-04-2019

Revision History None

Objective To accept or reject order.

Environment User Mode

Assumptions Customer has placed order and Employees application is running.

Pre-Requisite Order is placed by the customer.

Step# Execution Description Procedure Result

1. Employee select accept order. Order is selected by the employee.

Employee select reject order.

2. Order not selected by the employee.

Comments Customer must place order.

Status  Pass  Fail Not Executed

5.1.5 Check History

Admin of the application can check history of Customer and Employee. Table 5.5
demonstrate the test case for check history.

44
 Table 5. 5 Check History Test Case

Test Case ID Use Case Reference QA Test Engineer Name of Personnel

TC-2 UC-10 Programmer M.Ziaullah

Test Date 17-04-2019

Revision History None

Objective To check history of employee and customer.

Environment User Mode

Assumptions There is some record saved by the application.

Pre-Requisite Admin must be Signed In.

Step# Execution Description Procedure Result

1. Admin check records saved in Admin is able to access history

the application. records of customer and employee.

Comments Admin must be Sign In to access history.

Status  Pass  Fail Not Executed

5.1.6 Voice Order

Customer of the application can place order through voice command. Table 5.6
demonstrate the test case for check history.

Table 5. 6 Voice Order Test Case

Test Case ID Use Case Reference QA Test Engineer Name of Personnel

TC-2 UC-11 Programmer M.Ziaullah

Test Date 17-04-2019

Revision History None

45
Objective To place order through voice message.

Environment User Mode

Assumptions Customer speak English language.

Pre-Requisite Customer must be signed in

Step# Execution Description Procedure Result

1. Customer select the voice Order has been placed successfully.

button and record order.

Comments Admin must be Sign In to access history.

Status  Pass  Fail Not Executed

5.2 Difficulties during Testing and Implementation

Android version is updated quite often and new features are released frequently. Now a
days Android Q (10.0) Bata version is running on Google Pixel smartphones but most of
the android user are using android version from 6.0 - 8.0. So, development of the
application is swapping between new and old Android version. Installing Android Studio
with all the requirements is quite a time-consuming activity.

After installation of Android Studio to make it work with this project bulk of updates are
necessary to install. These updates are very important for better performance but new
updates bring new libraries which are not required, so platform becomes heavy and loading
time increases.

If these updates are not installed perfectly because of any reason application can fail to run.
Sometimes application fail due to mismatch of the updating of APIs. So, that was the
difficulty take occurs so many times during Testing and implementation.

For testing process test cases are generated and tested by running application on a
smartphone. While using emulator for testing, the map on the emulator do not show the
exact location and sometimes show known errors which take lot of time to identify and
correct error.

46
There were some issues in application while running it on a smartphone i.e. some of the
features were not responding properly because of the different android versions. Errors and
problems were discussed with experts and searched on web to find solutions. Sometimes
we need to update the APIs to get the application working smoothly.

Some of the buttons and links to upload profile pic were not working properly, it took lot
of time to get us out of that problems and finally run the application correctly. Some of the
issues occurred because of the slow internet connection which led the application to crash.
After lot of hard work and determination finally we were able to run the application
correctly without any major issues.

47
 CHAPTER 6

CONCLUSION AND FUTURE WORK

48
6.0 Introduction
In this chapter were going to discuss the deduction and the future work which can be done
in the future. Developed system is momentarily described according to the established
goals. Limitations of developed system are conversed and future recommendations for the
system are recommended for the future development in the project. This system still needs
some improvements in it. All the future approvals are described in the later phase.

6.1 System Overview

Internet Based Android Application for Vehicle Maintenance and Services is developed in
order to fulfill the needs of people (having vehicles). User can get vehicle related benefits
using android phone. User must have to install the application to get the assistances from
the application.

After the installation user has to click in application icon and have to select a user type. The
user has to register himself through ones mobile number. After providing ones mobile
number user receives an OTP which is used as a verification code for registration. In case
of Admin, one need to enter the specific code given to one (by developers) at the time of
deployment.

After verification, user need to provide ones profile information required by the application
then press save to upload the information into the database. There are three types of user in
this application as shown below:

Customer

Employee

Administration

For a user being a Customer, then one had to select vehicle type (car, bike). Then one has
to select some features and functionalities given in the application and save order by
clicking on confirm order. Then user is navigated to the google maps where one has to
provide ones location. Then the order is placed and the notification is sent to nearest
Employee available in that area. If the order is accepted then the Customer had the
information of the Employee how accepted the order. At the end after giving payment to
the Employee the Customer can also give feedback about that Employee who completed
ones order.
49
If user is an Employee, after logging into ones account one can get the notification
whenever an order is placed in ones area. If the Employee wants to accept the order, one
can get the location and information of the Customer who placed the order or else one can
reject the order.

If user is an Admin, one is given access to see the information regarding Customer or
Employee in the database. One can also change the status of the Employee according to the
rating.

In case of emergency user can also place ones order through voice message.

6.2 Limitation
Limitation are that the developed system must have an internet connection to install the
application on the android mobile phone. User must have smart phone having android
version greater than 6.0. GPS location must be on before starting the application. Otherwise
system may not work properly or crash in worst case scenario. System also redirects one to
that position where one gives the application the permission of navigation. Application may
crash or not work properly if the GPS location is not turned on. System accomplishes the
80-85% of desired result in the test cases.

6.3 Future Work

Because of time and economical limitations some of the features are not added now but can
be a part of this application in future. This system still needs improvements in many phases.
Following features can be involved as mentioned below:

6.3.1 Payment Method

Like other similar android applications, one can pay from the application wallet or through
online-bank, similar method can also be implemented in this system. Online banking is now
a days changing the whole money system. As now one can only pay by hand which is more
secure and reliable but changing needs of users online payment option is a good change to
be implemented in future.

6.3.2 Including More Vehicles

In future, we can also add more vehicles (Truck, Buses etc.) so that they can also get benefit
from the developed application. As till now only bikes and cars related features are
available. This feature will eventually increase the use of application. More vehicles mean

50
more users involvement that will also increase the employment process and give more
unemployed people a purpose in life to serve others through their services.

6.3.3 Order Scheduling

In future, Customer can set time and date of the order to be placed. When that time occurs,
the order is placed automatically. So basically, this feature is helpful if user know that one
is busy at a certain time and would not have time to place order so user can schedule the
order for that time. One can also call advance booking for the service. This system will
automatically schedule your maintenance date from the previous orders.

6.3.4 Voice auto place order

As till now application is only capable of listening to the Customer and convert the voice
message into text to send the message to the Employee. In future application can be capable
enough to interpret that text message and place the order accordingly. Up till now there are
some difficulties in directly placing the order through voice. Voice recognition is improved
in the future.

6.3.5 Language Option

As the application is being developed in Pakistan and Pakistan native language is Urdu,
so for the ease of users language of application is customizable. Users which cannot read
or understand English can switch to Urdu mode of application. This feature will also
increase the number of users. We will provide Urdu Pakistan for the ease of the
Customers.

6.3.6 Cost Custom Setting

As until now the cost of the features is hard coded in the system but for the future concern
Admin will be allowed to change the cost of the features. As the economy of the states is
not stable and the rates of petroleum products are changing day to day so hard coded vale
is not an option. As in the future updates of the application hopefully this method will be
implemented.

6.3.7 Contacting with a greater firm

As for now the idea of this application is to run individually but in order to expand the
business and make a mark in the market management can contact with the grater working
businesses like Cream or Uber. It is highly noted that to survive in the fast growing

51
market one must keep up with the speed and use efficient techniques to expand the
business. Now a days including a shareholder who has a strong hold of the business
market strengthen ones business.

6.3.8 Transection Record

For now Admin can only see the Users of the application and can change their status. For
future reference Admin will be allowed to see the transection records of the users.
Transection records includes Order placement date, time and what the order was their cost
and rating for each other.

6.3.9 Complaints
For the time being users can only rate each other but in future a complaint method will be
introduced for Customer and Employee in case they have any query or problem related to
each other or with the systems services. These complaints will be seen and manages by
the Admin of the application. This is a very important implementation for the application
as it will improve the value of it in the eyes of the users.

6.3.10 Area Increase

Currently this application is working for few/ limited areas. In future more cities can be
added as the business expands. If the idea goes beyond charts then this same application
can be internationally used with further updates in the current software. This indicates the
success of the application and the great idea of a large scale business industry. As for now
this software is only in its binging stages and had a very long journey ahead of it.

6.3.11 Car Rental

Another feature that can drastically increase the use of application will be adding Car
Rental option. In this scenario one person can add a vehicle as of available of renting.
Now other person looking for an available vehicle can view the description and contact
the renting person. If both made their agreement customer will accept the order from the
application so the Employer who gave the car can track the vehicle through application.
The tracking process will also count the total number of miles vehicle had traveled and
time in hours to finalize the payment. The application will finalize the amount after the
car owner had received the car and confirmed through the application confirmation
process. This is very vast idea and it will drastically increase the use of application
alongside the business of the product.

52
APPENDCIES

Appendix I User Manual

Android Application Launch

As user installs the application, user needs to launch the application by clicking on the
application icon and launch the application to use it. As shown in Fig A.I.1

Figure A.I.1 Android Application Launch

Select User Type to Login or register

Select one of the following user types by clicking on it to further proceed in the
application. As shown in Fig A.I.2

Figure A.I.2 Android Login or register

53
Registration/ Logging In

Provide mobile number and further required information to start application. As shown in
Fig A.I.3 and 4

Figure A.I.3 Provide Phone Number Figure A.I.4 Provide Personal Info.

Select vehicle type

Select one of the vehicle types or the voice icon to place order. As shown in Fig A.I.5

Figure A.I.5 Select Vehicle Type

54
Select Functionality

Select the required to further proceed in the order placement process. As shown in Fig
A.I.6 and 7

Figure A.I.6 Select functionality Figure A.I.7 Select functionality

After that make selections for the features provided by the application. As shown in Fig
A.I.8

Figure A.I.8 Select feature

Confirm to place the order using application.

55
References

[1] India's Car Servicing, "CarCrew," CarCrew India's Online Car Washing, Repairing
Services, [Online]. Available: https://www.carcrew.in/. [Accessed November 2018].

[2] "Mr.Rght," [Online]. Available: https://www.mrright.in/. [Accessed 3 November

2018].

[3] "IOS App Store," TimeSaverz, [Online]. Available:

https://itunes.apple.com/us/app/timesaverz-home-services/id966863452?mt=8.

[4] "Mr.Right," Android Application, [Online]. Available:

https://play.google.com/store/apps/details?id=in.kaaryaa.mrright.customer&hl=en.
[Accessed 4 November 2018].

[5] "Guru99," Guru99 Production, [Online]. Available:

https://www.guru99.com/functional-vs-non-functional-requirements.html. [Accessed
2 November 2018].

[6] S. Paradkar, Mastering Non Functional Requirements, Birmingham: Packt Publishing

Ltd., 2017.

[7] J. DiMarzio, Android A Programmer's Guide, New Delhi: Teta McGraw Hill
Education Prvate Limited, 2010.

56