An Independent project report 

submitted in partial fulfilment 
of the regulations governing 
the award of the 
B.Sc. (Hons) Computing, 2020

GOMOTOR

URMILA SHAHI THAKURI

1001849620
Faculty of Business & Information Science (School of IT)
UCSI University

February, 2020

Authorship Declaration
Except where reference is made in the references, this report contains no material published
elsewhere or extracted in whole or in part from a dissertation or report presented by me for
another degree or diploma.

No other person’s work has been used without due acknowledgement in the content of the report.

Signature: ______________ Date:_______________

                  Urmila Shahi Thakuri
GOMOTOR

- Urmila Shahi Thakuri

Table of Contents

1. Project Title......................................................................................................................................- 1 -
2. Background......................................................................................................................................- 1 -
3. Problem Statement..........................................................................................................................- 2 -
4. Aim.....................................................................................................................................................- 3 -
5. Objectives..........................................................................................................................................- 3 -
6. Justification......................................................................................................................................- 4 -
7. Scope..................................................................................................................................................- 5 -
8. Approach and Deliverables...........................................................................................................- 7 -
9. Major Milestone..............................................................................................................................- 9 -
10. Constraints and Assumption..................................................................................................- 11 -
Constraints:............................................................................................................................................... - 11 -
Assumption:.............................................................................................................................................. - 11 -
11. Resources...................................................................................................................................- 12 -
Software Requirements........................................................................................................................... - 12 -
Hardware Requirements........................................................................................................................ - 12 -
12. External Bodies Involved........................................................................................................- 13 -
13. Project Plan...............................................................................................................................- 13 -
Reference................................................................................................................................................- 14 -

TABLE OF FIGURE
Figure 1: Use case diagram of admin and Vendor for GOMOTOR...........................................................10
Figure 2: Use case diagram of customer for GOMOTOR..........................................................................11
Figure 3: Gantt chart..................................................................................................................................15
1. Project Title
GOMOTOR is a two-wheeler booking servicing platform that connects two-wheeler
owners and service centers through a seamless app-based technology. The GOMOTOR have
feature of booking for servicing two wheelers in selected centers. The customers can book
for servicing through GOMOTOR official website or their smartphone application. All the
service centers will be tracked by GOMOTOR app to handle the servicing for two wheelers.

2. Background
In the present context of Nepal, many people have two-wheeler vehicles and they
have to repair or service their motorbikes on time. There are so many servicing centers
which helps to maintain the bike and scooter. Currently, servicing center doesn’t use any
system or app for storing the information.
Every day, thousands of two-wheeler owners go through the same problem – either
we don’t find the time or we are too busy with our day jobs to make time for our bike. In
addition to this, we all have trust issues leaving our prized possessions in a random service
Centers. Also, in manual booking system it is difficult to search for particular data of
customers from this system and it is also difficult to store the information for long periods of
time. People have to visit or call the service center for to check their servicing status.
[ CITATION kau17 \l 1033 ]
To overcome the customer problems, I am developing the GOMOTOR progressive
web app. In this app, people can find a service center near them and then can book in that
particular servicing center through the app. After booking, the customers will get the
notification from the app for the booking date and time. And after their two wheelers get
serviced, they will get notification of servicing is done with bill. Customer can add more than
one two wheelers while booking for the servicing. Also, the app helps to track the
information of motorbikes serviced so that, customer will know the servicing time of their
vehicles.
3. Problem Statement

All the Motorcycle Servicing Center uses traditional file-based system to keep
records of customers and their bills. Due to this there is complication in keeping the records
of the transactions. As I mention above, customers are facing problems while standing in
queue. Furthermore, there are some other issues which have been listed below:
 Inconsistency
After doing the servicing one-time people forget their servicing time of motorbikes
and they have to call up the service center continually to check the status. There is high
chance of being damaged or may loss of bills.
 Lack of Security
The system is not secured which may lead to failure or loss of information of the
system. As a traditional file based system there are chances for misplacing the
information
in the system.

2
4. Aim
People are so busy with their day to day activities. They are not getting enough time to
service their own vehicles(bike/scooter). By considering the people’s problems, the main
aim of my project is to make easier for people to get their bike/scooter serviced on time and
helps to manage the details of bikes and scooter. It helps to save the people’s time for
booking.

5. Objectives
The main objective of my project is:
 Able to provide the list of servicing center with their locations
 To provide booking facility to the customers
 To be able to send notification before and after the servicing is done
 To send bill of servicing with details while sending notification
 To add more than one bikes/scooter for one customer
 To manage the details of added bikes/scooter
 To track the details of added motors
 An expert to consult to for all customers queries
 Timely maintenance reminders
 A complete track of your bike service history

3
6. Justification
Technology, science and knowledge are important in modern contemporary society.
People are using gadgets in day to day activities so they prefer to update their daily activities
online. Likewise, GOMOTOR is also a progressive web app that helps to find service
centers nearby people's location.
The proposed system will be a progressive web application capable of handling all booking
and customers. In this app, Customers need to visit the site and add app in their mobiles.
After downloading the app, they should login to booked for service if the customer is new
then they need to register. While booking, the user needs to enlist motorcycle full
information and details and after the booking they will be notified about the confirmation of
their motorbike servicing. After the servicing is done, they will again be notified that their
servicing is done with bill after that they can take their bikes home. Real-time tracking is a
boon. Don’t have to call up the service center continually to check the status. In addition to
that, get regular updates and reminders about the next bike service.

4
7. Scope
This software is mainly developed for the people who ride bikes and scooters. The
proposed system is to provide new way of dealing problems in managing the booking for
servicing system. Overall new proposed system is based on computerized and mobile
system. The reason for choosing computerized and mobile system is that it beats the old
ways of file-based system and has many advantages in most sector compared to traditional
file-based system.
System User
In the system there are three users which play specific roles in the system.
 Admin
One of the most important roles is admin. Admin manages the vendors,
customers, motor details and notifications. Admin manages the overall system.
 Customer
Customers can login, sign up and booking for servicing. Also, can manage added
two wheelers in this system.
 Vendor
Vendor are the servicing center which is added by the admin. Vendor should
provide the details to the admin.
some functional requirements are not included in this software which are enlisted below:
● It doesn’t include an emergency option. If the customer has an emergency to
repair their two wheelers.
● Not links with other social media accounts. Customer cannot sign up through
other social media accounts
● There are no rewards points for the customers.
● Not useful for four wheelers.
● Customers should visit the service center for payment i.e. it doesn’t include online
payment

5
 Figure 1: Use case diagram of admin and Vendor for GOMOTOR

6
 Figure 2: Use case diagram of customer for GOMOTOR

7
8. Approach and Deliverables
In the development of this project, Rapid Application Development (RAD) approach
will be used. In this approach, the useful modules are created in parallel as prototypes and
are coordinated to make the complete product for quicker product delivery. As this approach
has no detailed preplanning, it is easier to incorporate the changes within the development
process. So, this approach is best suited for project development since this system should be
developed in a limited time frame. As a result, information gained from the improvement
procedure itself can feedback to the prerequisites and plan of the arrangement. The major
four phases of Rapid Application Development approaches are:
i. Define the Requirements:
Firstly, rapid application development itself separated from traditional software
development models. The wide idea of the prerequisites causes you give explicit
necessities at various purposes of the improvement cycle.
ii. Prototype:
In this phase, actual development takes place. In this process, developers create
prototypes with different quality and functions as fast as they can instead of following
a strict set of requirements. These prototypes are then appeared to the customers who
choose what they like and what they don't. Usually, these models are immediately
made to work, just to flaunt certain highlights, without legitimate clean. This is
ordinary, and the last item is just made during the finish organize where the customer
and engineer agree on the final product.
iii. Receive Feedback:
In this phase, feedback is given about the product and its functionality. This step
helps to know whether the system is ready or feasible to fit the requirement. These
steps are also repeated continuously so that we know its visuals and interfaces.
a. Finalize Software:
In this phase, the characteristics, usability and interface of the system is
finalized between the developer and the client. Whether the system will be functioning
well or stable is the paramount importance before delivering the system to the client.

8
 Zoho Creator tool will be used for this approach which automate everyday tasks, and
streamline data management[ CITATION Sou20 \l 1033 ]. Get rid of tedious work and focus
on building your business. From collecting data to converting information into insights,
Zoho Creator does it all[ CITATION Sou20 \l 1033 ]. Automating any processes, giving your
colleagues the access, they need, visualizing information through reports, and doing it all
from anywhere[ CITATION Sou20 \l 1033 ].

The achievement of the project will be as following:

RAD PHASES DELIVERABLES
Define the Requirements Collecting the requirements for software
Prototype Coding and development of the software
Receive Feedback Collecting developers’ and client’s
requirements
Finalize Software Software are Finalized

9
9. Major Milestone
The major milestone to deliver software is given below:

Milestones Start date End date Duratio

n

● Selecting Project Title 10/01/2020 18/01/2020 8

● Writing the Proposal 30/01/2020 08/02/2020 9

● Evaluating the final proposal 09/02/2020 16/02/2020 8

● Submitting the final proposal 16/02/2020 19/02/2020 3

● Proposal Presentation 28/02/2020 01/03/2020 4

● Requirement Gathering 09/03/2020 22/03/2020 13

● Planning 24/03/2020 04/04/2020 8

● UX Design 06/04/2020 13/04/2020 7

● Coding 13/04/2020 29/05/2020 46

● Testing 01/06/2020 06/06/2020 5

● Deployment 06/06/2020 15/06/2020 9

● Maintenance 16/06/2020 24/06/2020 7

● Report Writing 13/04/2020 28/04/2020 15

10
 Figure 3: Gantt chart

11
10. Constraints and Assumption
Constraints:
The foremost constraints for the system will be controlled by human. It will be
made on the basis that the users entering the data enter correct data and in the correct
way. The other constraints of the system are:
● It was quite difficult to search and read multiple research papers.
● There is limited time for the development so all the required features might not be
incorporated
● Internet will always require for booking
● Limited use of resources due to lack of budget.

Assumption:
● the technical context of the project such as platform and environments that will be
used.
● Services that will be available to a project such as offices or a data center
● Infrastructure that will be available to a project such as networks and
communication tools

12
11. Resources
Software Requirements
 Operating system: Windows 7, 8, 10
 Browser: Mozilla, Chrome, Opera, Safari
 Frontend: HTML & CSS, Bootstrap, Angular 8, Android Studio
 Software: Node JS, Android Studio
 Framework: Angular 8
 Text editor: Visual Studio Code (version 1.42)

Hardware Requirements
 Processor: Pentium
 RAM: 500 MB
 Keyboard, Mouse
 Monitor

13
12. External Bodies Involved
This project is not being carried out in collaboration with the external bodies or any
other parties. This project will be developed by myself for learning purpose which helps to
develop my skills in the process of leaning Angular.

13. Project Plan

Milestones Start date End date Duratio

n

● Selecting Project Title 10/01/2020 18/01/2020 8

● Writing the Proposal 30/01/2020 08/02/2020 9

● Evaluating the final proposal 09/02/2020 16/02/2020 8

● Submitting the final proposal 16/02/2020 19/02/2020 3

● Proposal Presentation 28/02/2020 01/03/2020 4

● Requirement Gathering 09/03/2020 22/03/2020 13

● Planning 24/03/2020 04/04/2020 8

● UX Design 06/04/2020 13/04/2020 7

● Coding 13/04/2020 29/05/2020 46

● Testing 01/06/2020 06/06/2020 5

● Deployment 06/06/2020 15/06/2020 9

● Maintenance 16/06/2020 24/06/2020 7

● Report Writing 13/04/2020 28/04/2020 15

Reference
14
[1] kaush666, "Default Car & Bike Service: GoBumpr.com (Chennai)," Team BHP, 2017.
[2] S. Nagar, "Top 10 Custom Software Development Methodologies," Promotion World, 2020.
[3] "ZOHO Creator," Zoho Corporation Pvt. Ltd. , 2020. [Online]. Available:
https://www.zoho.com/creator/.
[4] M.-Y. H. Y.-B. C. J.-G. D. Hua Yi Lin, "An Implementation of Vehicle Management System
on the Cloud Computing Platform," ICAICTE, vol. 30, pp. 171-176, 2014.
[5] D. B. ,. T. ,. Y. P. Hanamant B. Sale, "Online Management System for Automobile
Services," IJESC, 2018.
[6] C. C. H. M. a. D. T. P Beynon-Davies, "Rapid application development (RAD): an empirical
review," European Journal of Information Systems , p. 211–223, 1999.

15