Mobile Application For University Transportation

Mobile Application for University Transportation
Syed Azeem Hassan

(UW-18-CS-BS-046)
Ghulam Modih-ud-Din
(UW-18-CS-BS-054)
Aleena Sajid
(UW-18-CS-BS-059)
Department of Computer Science

University of Wah
Wah Cantt
2018-22
Mobile Application for University Transportation
Undertaken By
Syed Azeem Hassan

(UW-18-CS-BS-046)
Ghulam Modih-ud-Din
(UW-18-CS-BS-054)
Aleena Sajid
(UW-18-CS-BS-059)
Supervised By
Sir Asim Ali
A dissertation submitted as a partial fulfillment of the requirements for the degree of

Bachelor of Science in Computer Science
Department of Computer Science

University of Wah
Wah Cantt
Session 2018-22
Undertaken
We certify that this is our own work. The work has not, in whole or in part, been
presented elsewhere for assessment. The sources are properly referenced and
acknowledged where required. If the above statements are false, we acknowledge that
we will have committed an assessment offence and shall be liable to punishable action
under the plagiarism rules of HEC.
Syed Azeem Hassan

Reg. No (UW-18-CS-BS-046)
Dated:
Ghulam Modih-ud-Din
Dated:
Aleena Sajid
Dated:
i
Certificate
It is certified that the contents and the form of the report submitted by Syed Azeem
Hassan, Ghulam Modih-ud-Din, Aleena Sajid have been found satisfactory for the
requirement of the degree of Bachelor of Science in Computer Science.
Supervised By Sir Asim Ali

Assistant Professor
Department of Computer
Science
University of Wah, Wah Cantt
Approved By
Examiner: Dr. Uzma
Assistant Professor
Science
Examiner: Ms.Marium Azhar

Lecturer
Science
Examiner: Ms. Isra Naz

Lecturer
Science
Chairperson of Dr. Wazir Zada Khan

Department: Associate Professor
/Chairperson
Science
ii
Dedication
We would like to dedicate this project to Allah Almighty, our beloved presents and
teachers. Without their support noting would be possible, they taught us that best
knowledge to have that which is learn for its own sake. They taught us that largest
task can be accomplished if its done one step at a time. Thanks to all for their valuable
cooperation with us.
iii
Acknowledgements
We would like to thank everyone who had contributed to the successful completion of
this project. We would like to express our gratitude to our project supervisor, Ms.
Rukhsana Kousar for her valuable advice, guidance and her enormous patience
throughout the development of the project. In addition, we would also like to express
my gratitude to our loving parent and friends who had helped and given us
encouragement.
Syed Azeem
Hassan Ghulam
Modih-ud-Din
Aleena Sajid
iv
Abstract
Mobile application for university transport is related to transport issue which student
face on daily basis in university of Wah. Lack of proper management and timing
problem sometimes becomes irritating and it affects the transport services as well as
students. Our aim is to bring the physically control transportation network via mobile
application. It would be easy for administrator, drivers as well as for students. If all of
the things are balanced and well controlled on digital devices leads to minimize
occurrence of error. Transport Administrator would be doing the major work in this
application like setting the pickup points, confirming students for buses, keeping track
of all the buses etc.
v
Table of Contents
Undertaken......................................................................................................................i
Certificate.......................................................................................................................ii
Dedication.....................................................................................................................iii
Acknowledgements.......................................................................................................iv
Abstract..........................................................................................................................v
Table of Contents..........................................................................................................vi
List of Figures..............................................................................................................vii
List of Tables..............................................................................................................viii
1. Introduction..............................................................................................................1
1.1 Introduction...........................................................................................................1
1.2 Problem Statement................................................................................................4
1.3 Aims and Objectives.............................................................................................5
1.4 Scope of the Project...............................................................................................6
1.5 Tools and Techniques............................................................................................7
2. Literature Review....................................................................................................9
2.1 Comparative Analysis.........................................................................................10
3. Design and Methodology.......................................................................................15
3.1 Functional Requirements....................................................................................17
3.1.1 Non-Functional Requirements...........................................................................18
3.2.2 Sequence Diagram...........................................................................................16
3.2 Data Flow Diagram............................................................................................11
3.3 ERD.....................................................................................................................22
3.2.1 Use Case Diagram...........................................................................................22
3.2.3 Languages and Tools.......................................................................................17
4. Implementation….....................................................................................................22
4.1 Software Deployment Model................................................................................23
4.1.1 Languages and Tools........................................................................................23
4.2 Database Design.....................................................................................................24
4.3 GUI........................................................................................................................25
References..................................................................................................................35
vi
List of Figure
Figure 1 Students have been facing severe transport proble............................2

Figure 2 More students in the van than its capacity.........................................3
Figure 1.3 University Student died in road accident…....................................4
Figure 2.1 Uber Application Interface............................................................10
Figure 2.2 Ola cab Application Interface.......................................................11
Figure 2.3 Bykea Application Interface..........................................................12
Figure 2.4 Careem Application Interface........................................................13
Figure 2.5 inDriver Application Interface.......................................................14
Figure 2.6 Swvl Application Interface...........................................................15
Figure 3.1 Use Case for User and Admin......................................................21
Figure 2.2 Use Case for Driver and Admin...................................................21

Figure 3.3 Flow Chart....................................................................................20
Figure3.4 ERD Diagram................................................................................22
Figure 3.5 Database Design...........................................................................25
Figure 3.6 Use Case Diagram for Main Application....................................25
Figure 3.7 Use Case Diagram for Passenger Interface..................................26
Figure 3.8 Use Case for Admin Interface......................................................27
Figure 3.9 Use Case for Driver interface.......................................................28
Figure 3.10 Passenger Reservation...............................................................29
Figure 3.11 Request Approval......................................................................29
Figure 3.12 Adding Drivers..........................................................................30
Figure3.13 Picking up Students....................................................................30

Figure 4.2: Database Design….....................................................................32
Figure 4.3: Login Screen..............................................................................33
Figure 4.4: Admin Interface........................................................................34
vii
List of Tables
Table 3.1 Use Case for Main Application…........................................................25

Table 3.2 Use Case for Passenger Interface........................................................26
Table 3.3 Use Case for Admin Interface..............................................................27
Table 3.4 Use Case for Driver Interface..............................................................28
viii
1. Introduction
Introduction
1.1 Introduction
Students in UOW face a lot of problems like academic problems and management
issues etc. Transportation is one of the major problems that they are facing during
academic timing. Suppose if a student gets admission in a UOW which is located far
from his home then transportation becomes a major issue for that particular student.
Similarly, if an employee is working in a UOW and lives far away from it, then
transportation is an issue for that particular employee as well. They are not allowed by
the bus-conductor to have a seat, so they are seen on the roofs of the buses.
There are always more students in the buses than its capacity which is dangerous and
has often caused major road accidents. In the absence of an effective transport system,
majority of the students have to make personal travel arrangements, which means
using either private conveyance or public transport. Some students who get
motorbikes, they get involved in one wheeling and over speeding.
Our aims to provide innovative services relating to different modes of transport and
traffic management and enable users to be better informed and make safer, more
coordinated and smarter use of transport networks.
We are going to automate existing transport system that will be very helpful for
transport management. They can manage the information like namely the number of
buses that go to required destination, bus numbers, bus timings, the routes through
which the bus would pass, time taken for the vehicle to reach its destination location
would assist the passengers with various routes, track the current location of the bus
and give the correct time for the bus to reach its destination. The existing system faces
the aforementioned problems.
The proposed system platform is android, reason being Android Operating System has
come up on a very large scale and is owned by almost every second person. As more
applications of android operating system is developed day by day on large scale ever
since it is arrival.
The application can run only on android devices. It would inform the students about
the exact time of arrival and departure of buses on route. Any change in the scheduled
movement of the buses would be updated in the software. Regular alerts would be
sent in case of delays or cancelation of buses. Bus locations and routes are shown on
app using Google map application programming interface (API).
Mobile Application for University Transport

2
Introduction
The proposed mobile application will be useful to know next stops and students can
monitor the location of the bus on the map. The chance of missing the bus by students
will be reduced. This application will save the time and iterations of bus wait will
definitely lessen by this app. This system will stores all operations done in a day and
helps the student and management of transport services. This proposed app will
provide better management and quick transport services for student.

3
Introduction
1.2 Problem Statement
Transportation is the one of the major issues when it comes to going from one place to
another place. It does not matter if you are an employee in an organization or you are
a student in some school, college or university, the problem of transportation will
always be there. There are some people running pick and drop services privately.
Moreover, there are whole networks of pick and drop services running at different
places all over the country. The problem that these service providers face is the
difficulty to maintain the whole network. When it comes to managing all the vehicles,
drivers and customers, the job becomes a little tougher than usual.
Figure 1.3 University Student died in road accident
The road traffic accident is the one of most preventable cause of mortality and non-
fatal disability among young-adults and teens in Pakistan. There are many Pakistani
students

4
Introduction
dying and injuring because of road traffic accidents and crashes, and many of them
incurring with a disability as a result of their injury as Figure 1.3 shows that a
university student died in a road accident.
Having analyzing the manual system, we have identified many weaknesses and
problems. The problems we identify are mentioned below
i) Inefficient and time consuming

The existing system is time consuming and it also leads to many problems
such as manual mismanagement, irregular vehicle scheduling, unexpected
delays.
ii) The excessive use of paperwork
The use of paperwork in the existing system is time consuming and it also
leads to many problems. The probability of losing is high. If a document is
lost, there’s no way to recover the lost data. It also requires more physical
storage space to store increasing paper works. Finding a specific information
is hard.
iii) Communication weaknesses
There is a lake of communication between student, driver and transport
administration in the existing system. There is no proper system for
communication to inform the student about unexpected delays etc.
Maintaining all the vehicles is very hectic job so we proposed a system which could
maintain all the important details so that we can provide the live location of each
vehicle and finding their path. As all the systems are moving from physical to digital,
it was time for people of university transport networks to do the same.
1.3 Aims and Objectives
The proposed mobile application is used for solving many problems starting from the
students waiting for the bus. The mobile application will be useful to know next stops
and students can monitor the location of the bus on the map. The chance of missing
the bus by students will be reduced. The application provides the live location of the
bus to the user.
The objectives of the Report are shown as following:
i) Our main objective is to design a transport system to facilitate student.
ii) To digitalize the university transport networks, in this way it would be easier to
5
Introduction
carry out the related tasks for the bus drivers and also for admin.

6
Introduction
iii) Keeping track of all the drivers, find out which vehicle is on route and which is
not, find out whether the student have been picked up at specific timing or not
iv) Automating the university transport networks that are already in place but are
running on manual functions.
v) To give the user the exact location of the selected bus with respect to the user
location.
vi) To give approximate distance and time of the bus from the user location using
google map API.
vii) It will automate tasks for administrator like keeping track of all the users that
use their service, keeping record of payments by customers.
In everyday life, many students will be affected by the movement of the bus by
different unsure conditions so instead of using an alternate transportation a message
showing the arrival time of the bus will help the student to reduce their stress. A real
time trance bus tracking system can help to solve this problem by providing
opportunity to track the bus location in real time and use the information for future
predictions of bus arrivals at the stops along the entire route. When this information is
shared with students they can spend their time efficiently and reach the bus stop
before the bus arrives.
1.4 Scope of the Project
The proposed application will provide services to both types of users that is the people
managing the transport network and the students who use the services provided by
people of transport network. It will help the administrator like keeping track of all the
users that use their service, keeping record of fee submission, keeping track of all the
drivers, find out which vehicle is on route and which is not, find out whether the
student have been picked up at specific timing or not. Find out what is the estimated
time of arrival of driver and the details of that particular driver etc. Each activity will
be monitored by administrator. The application will be reliable for users.
The main goal of the proposed work is to improve the Bus Tracking system by adding
the necessary features to our project, like projecting accurate bus timings, presenting
correct bus numbers and by using google map API for accurate locations.
By using google map API the map will be updated automatically for students and
drivers which will facilitate the students to find out the exact positions and also

7
Introduction
determine each bus stop.

8
Introduction
1.5 Tools and Techniques
The proposed application is developed in Android Studio, using Java as the

programming language with XML being responsible for designing the interfaces, that
create the front end. The front end consists of multiple activities each activity
consisting of a java file and its corresponding xml file.
The back end developed in firebase that provides authentication, real time storage,
crash reports, whose dependencies are to be loaded into the Android Studio. It
provides complete details of application and analytics regarding it, like the daily and
monthly active users, the change in them is also represented along with the number of
crashes
Here we provide a brief description of technologies that we use while developing our
application:
i) Android Studio
Android Studio is a working environment where we can develop android
applications using JAVA, XML and by connecting with databases through the
coding techniques. It provides ease with its drag and drop feature and live
view of the application that is being developed.
ii) Google maps Application Programming Interface
Google Maps is a web mapping service developed by Google. It offers satellite
imagery, aerial photography, street maps, panoramic views of streets, real-time
traffic conditions, and route planning for traveling by foot, car, bicycle and air,
or public transportation.
iii) Firebase database
The Firebase Realtime Database is a cloud-hosted database. Data is stored as
JavaScript Object Notation (JSON) and synchronized in real time to every
connected client. When you build cross-platform apps with our iOS, Android,
and JavaScript software development kit (SDKs), all of your clients share one
Realtime Database instance and automatically receive updates with the newest
data.

9
Introduction

1
0
2. Literature Review
Literature Review
2.1 Literature Review
In this literature review an effort made to critically evaluate the earlier systems work and
methodologies related with our project to study, analyze and evaluate its relevance.
Here, some similar technologies are discussed
i) Uber
Uber [3] is an application which is used by general public to call cabs and drop off at their
destinations. It is widely used in the world. It uses multiple technologies for picking up,
dropping off, real time tracking and getting accurate locations on map. It uses geolocation
for getting position of user and driver. It uses Google Maps for map services. Moreover,
there is a system for notification upon arrival of driver or completion of a ride. Uber is not
available in major cities of Pakistan. The price could be double or more during rush hour.
Drivers have to pay the cost of fuel, maintenance, and repairs from their own pocket.
Figure
2.1 shows the Interface of uber application.
Figure 2.1 Uber Application Interface

9
Literature Review
ii) Ola
Ola Cabs[4] is an Indian application developed to provide transportation services to the
users. It is an online alternative to taxis with more services as compared to taxis . First of
all, like all the other applications, it uses Global Positioning System (GPS) is a system of
satellites that circle the earth and send a flag to GPS recipients and Navigation gadgets,
giving them the exact area, speed, and on the off chance that you are in an air ship or up a
mountain, elevation. The working of Ola is similar to other transportation applications.
When client opens up the application, its location becomes available to central server.
Once the location is available, the job of server is to find the closest cabs. It also has
system for real time tracking [5]. Drivers have payment issues, the main issue in this
application is the lack of communication with the drivers. There are also payment issues in
this cab service. Figure 2.2 shows Interface of Ola application.
Figure 2.2 Ola cab Application Interface
iii) Bykea
Bykea is a Pakistan-based mobility app, it offers ride-hailing, parcel delivery, payment
services, and more through its motorbike network. Bykea is to empower people in
Pakistan's gridlocked cities to get their lives moving. There are some safety issues in
bykea app, and
10
Literature Review
is not suitable for women in Pakistan. Inability to Carry Passengers. Figure 2.3 shows
Interface of Bykea application.
Figure 2.3 Bykea Application Interface

iv) Careem
Careem[3] is a vehicle for hire company which is a subsidiary of American company
Uber. Careem is also used by general public to hire cabs. The working of Careem is
similar to other transportation applications. When client opens up the application, its
location becomes available to central server. Figure 2.4 shows Interface of Careem
application.

11
Literature Review
Figure 2.4 Careem Application Interface
v) InDriver
inDriver is a ride-hailing app that promotes mobility in the emerging world by helping
customers and drivers to negotiate a fair price. Launched in Siberia in 2013, the platform
has grown into the world's second-largest and fastest-growing ride-hailing app in February
2020. inDriver promotes driver safety with its “GPS location sharing” feature. Riders can
share their GPS location and ride details in real-time from the app with their trusted
contacts. Figure 2.5 shows Interface of inDrive Application.
Figure 2.5 inDriver Application Interface

12
Literature Review
vi) SWVL
Swvl is Dubai-based ridesharing company that produces an app for hailing buses. Swvl
also uses multiple technologies for picking up, dropping off, real time tracking and getting
accurate locations on map. It uses geolocation for getting position of user and driver. It
uses Google Maps for map services. Figure 2.6 shows interface of swvl application
.
Figure 2.6 Swvl Application Interface

13
Methodology
3. Design and Methodology

14
Methodology
3.1 Methodology
The proposed application consists of three interfaces Transport Admin, Student and Driver user as
described below.
3.1.1 Transport Admin Interface
This one is for the person who controls all the drivers or have all the record of the system. The
admin manages the drivers, the routes from which bus will go and one of the important works that
he will decide the route payment, he is also responsible for any mishap.
The admin logs into the system with user name and password, the admin manages routes, students
and drivers add and delete student and drivers, also the first thing the admin does is add routes
that are stored in the database, also the user’s data is stored into the database in the users table,
while adding students the admin assigns routes to student.
Admin can add routes to the system by clicking manage routes where routes screen will appear
and add information about route by stating its name and bus number, adding the departure and
arrival times; departure is the time the student going route to the university and arrival is the
retuning route from the University.
Finally, through the route tab the admin states the start and end point of the route by taping on the
map to select location A then tapping to select location B. Admin also can delete a student name.
Student's information can be viewed by admin. Admin also can add and delete drivers' names.
3.1.2 Student
The student can login to the system with username and password provided by the administrator,
students can view the route in real time and can locate the driver’s location on the map when the
driver clicks start route, the student will be able to locate the driver on the route and the speed will
be displayed too.
Now the question arises how the student came to know where the drivers are or on which bus,
they go, these all details are shown on map, the driver the one that will be available on map for
them. The students will get notifications for particular bus five minutes before bus leaves.

15
Methodology
3.1.3 Driver
The driver logs into the system by providing the username and password, driver can start the
route by clicking start route on his home page, as soon as the driver clicks start route button the
route starts and real time tracking starts on the driver and student mobiles, the driver can view the
route where the students’ locations (pickup points) are shown. The driver can choose to report a
situation if an accident occurs or the bus is out of service and this will appear on the admin’s
home page immediately to take the ultimate solution to solve the problem
This interface will also contain a Google maps which is going to help the driver in navigation the
driver will know the locations to pick up student [1].
3.2 System Architecture
The Figure 3.1 show how many components are going to be and how will they function in overall
performance of the system
Figure 3.1 Use Case for User and Admin

16
Methodology
Below is the diagram which represents the data flow of the application.
Figure 3.2 Use Case for Driver and Admin
3.3 Functional Requirements
These are the functional requirements of our system.

Registration
The first step will be the step of registration. For those users who need pick and drop service, they
will have to register for the service that they are going to use. They will have to select the
particular university transport network and then register themselves for that network. Once it is
done, a request for approval will be sent to admin in the form of notification. The administrator
will be registered once by the development team and there will be only one admin. All the
required drivers will be registered by the admin himself.
Map and Location
The application is going to use the functionality of Google Maps. The map will be able to provide
live location of users. The user’s location will be visible to the map of driver which is on route or
which is supposed to pick up the people at particular timing. Similarly, when driver is close to
pick up location of any user, the driver’s location will be visible to that particular user as well.
When it comes to admin panel, he can check the location of driver on route and can find out

17
Methodology
which route is

18
Methodology
the driver taking. In short, admin will be able to track the drivers.
Admin Panel
Admin is the type of user which will be responsible for the management of whole pick and drop
network. Admin will be provided with various options like confirming the pickup points, keeping
track of location of drivers, checking whether the users have been picked up or not, marking the
students upon the receiving the fees. More features will be made available once the application is
launched.
Notifications
The application will be able to send notifications but notifications will be different for different
types of users. For instance, if a request for registration is made by some user, the request will be
sent to admin in form of notification. When the driver is close to pick up location, a notification
will be sent to the user stating that the driver is few minutes away.
Driver Panel
This panel is for the drivers who will drive vehicles and who will be responsible for picking up
people. This panel will consist of a map which will feature locations of pickup points. If the
driver is not available for some reason, then he can contact and tell the admin to arrange another
driver. The drivers will be added by the admin. Once the admin registers a driver, a user name
and password will be generated for the particular driver.
3.3.1 Non-Functional Requirements
These are the non-functional requirements of our system.

 Usability
The application is developed in such a way that it will be easier to use even for novice user.
Before usage, a little training session for users can easily teach them how to use the application.
Upon opening the application for the very first time by any user, there will be a training session
which will describe the features of application and how they can be used. This will help users in
understanding how to properly use the application. The training session could take place in any
form i.e., it could be a video demonstrating all the function or the simple text.

19
Methodology
 Reliability
In order to access and properly use features of application, an internet connection will be
required. Reason for this is that the features in this application require internet connection in order
to work and it is not possible to use them without any internet or data connection.
 Compatibility
The application will be able to run on all android devices. It would be better if users use latest
version of android as older versions may create some problems when it comes to running the
applications.
 Performance
All of the working of application will be real time, meaning when any request is made, the
notification will be sent immediately. If some kind of error takes place during the whole process,
an error message will be displayed. If the admin does not have required features to respond to any
request, then after few minutes, a notification will be sent to the user stating that the admin is not
available.
 Design Constraints
One of the objectives is to integrate services of Google maps and GPS with the proposed system.
The constraint is that sometimes, these services fail to integrate and as a result, system crashes.
To avoid such scenarios, precautionary steps will be taken. Other constraints include regulatory
policies, parallel operations and high order language requirements.
The figure shows how many components are going to be and how will they function
inoverall performance of the system.
3.3.2 Data Flow Diagram
First of all, user will enter his/her login details, if login detail is correct then it will login to the
app and dashboard screen will displayed. If login detail is incorrect then it will show invalid login
message and user will enter login details again. If login details is of student then student
dashboard will be appear, if login id matched with driver then driver dashboard screen will be
displayed and if login detail is of admin the admin dashboard will be displayed. Driver screen has
following options; pick-up points, view routes on map, send live location and reach destination.
Admin modules have following options; add bus, add student/driver, view location of students
and driver and update all information. Student modules have following options; view us, driver on
map, and reach destination. And all modules can logout from the app.

20
Methodology
Figure 3.3 Flow Chart

21
Methodology
3.3.3 ERD
Entity Relationship Diagram of the system is presented in figure 3.4. The admin has a login
username and password to log to the dashboard to carry out his tasks. The admin can control
all the tasks from his screen. The driver can set the availability of the bus weather the bus is
available or not, if the bus is not available a notification will be sent to the concerned students.
The timetable of each student will be entered, a notification will be sent and route will be
updated accordingly if there are any changes in the presented schedule
Figure 3.4 ERD Diagram
In figure 3.4, there are 6 relations in the database: Student, Driver, Schedule, Admin, Fees and
Bus. The admin manages all the tables in the ERD. The student is related to Bus and Schedule
tables.
22
Methodology
3.3.4 Use Case
Use cases represent overall functions and features available and how users are going to interact
with them. It shows the actions between the actor and the system. The actors are basically users of
the system. Below are the use cases for the application.
 Use Case diagram for Main Application
Use Case Diagram for Main Application Figure 3.6 shows the use cases for the main application
which show the work flow between components. User diagram specifies the actor and
communication between the actor and the processes.
Figure 3.6 Use Case Diagram for Main Application

23
Methodology
Use case ID 01
Title Main Application.
Description Both users will be able to
perform actions after
registration.
Actor Student and Admin.
Pre-Condition Registration.
Post-Condition Usage of application.
Alternative None
 Use Case diagram for Passenger Interface
Use Case Diagram for Passenger interface Figure 3.7 shows the use cases for the application
which show the work flow between components. User diagram specifies the actor and
communication between the actor and the processes.
Figure 3.7 Use Case Diagram for Passenger Interface

24
Methodology
Table 3.2 Use Case for Passenger Interface
Use case ID 02
Title Passenger interface.
Description Passenger will be able to register ride and
perform other functions.
Actor Student
Pre-Condition Sign in.
Post-Condition Usage of features available in passenger
interface.
Alternative None.
 Use Case diagram for Admin Interface

Use Case Diagram for Admin Interface Figure 3.8 shows the use cases for the application which
show the work flow between components. User diagram specifies the actor and communication
between the actor and the processes.
Figure 3.8 Use Case for Admin Interface

25
Methodology
Table 3.3 Use Case for Admin Interface
Use case ID 03
Title Admin interface
Description Admin will perform tasks related to the
management of network.
Actor Admin.
Pre-Condition Sign in.
Post-Condition Usage of features available in admin
interface.
Alternative If the data is not available for the city, user
can add trees at his own.
Use Case diagram for Driver Interface
Use Case Diagram Figure 3.9 for Driver Interface shows the use cases for the application which
show the work flow between components. User diagram specifies the actor and communication
between the actor and the processes.
Figure 3.9 Use Case for Driver interface

26
Methodology
Table 3.4 Use Case for Driver Interface
Use case ID 04
Title Driver interface.
Description Driver will be able to view pick up
locations and destination.
Actor Driver
Pre-Condition Sign in..
Post-Condition Usage of features available in driver
interface.
Alternative Feature will be only limited to the
android version greater that 8.0 that
supports AR Core.
3.3.5 Sequence Diagram
These diagrams show in what order the components of system work. Sequence diagrams for this
application are shown in Figure 3.10.
Figure 3.10 Passenger Reservation
Request Approval
The Figure 3.11 shown below is how the components of system works.

27
Methodology
Figure 3.11 Request Approval
Adding Driver
The Figure 3.12 shown is how the components of system works.
Figure 3.12 Adding Drivers

28
Methodology
Picking up passenger
The Figure3.13 shown is how the components of system works.
Figure3.13 Picking up Students
3.3.6 Languages and Tools
There are many technologies use such as:
 Android Studio
Android Studio is a working environment where we can develop android applications using
JAVA, XML and by connecting with databases through the coding techniques. It provides ease
with its drag and drop feature and live view of the application that is being developed.
 Firebase
The Firebase Realtime Database is a cloud-hosted database. Data is stored as JSON
and synchronized in real time to every connected client. When you build cross-platform
apps with our iOS, Android, and JavaScript SDKs, all of your clients share one Real time
Database instance and automatically receive updates with the newest data[7]
 Google maps
Google Maps is a web mapping service developed by Google. It offers satellite

imagery, aerial photography, street maps, panoramic views of streets, real-time
traffic conditions, and route planning for traveling by foot, car, bicycle and air, or
public transportation.

29
4. Implementation
Implementation
4.1 Software Deployment Model
The application is going to be designed using Agile methodology. In agile methodology, we

leave gaps so we can make changes even during the development. In long run, this methodology
is useful because it is not limited to some features only but we can make changes anywhere at
any time. Its stages are:
4.1.1 Plan
In this stage, the idea of application is presented and discussed. The requirements are
gathered and it isunderstood what needs to be developed and what does the user at the
end.
4.1.2 Design
The development procedures are brought to light during this stage. Decision is made
about how the application is going to be developed and how will features become
available. What services are feasibleand what are not, how will the services integrate
with one another
4.1.3 Develop
The actual work of making a software or application is done here. The conceptual ideas
are brought tolife in this stage. It is the job of developers to deliver what is required by
user.
4.1.4 Test
Once the software or application is developed, it is then tested to ensure that it what was
required in thefirst place. There are different types of testing to ensure this. Main thing
that matters is the user satisfaction.
4.1.5 Deploy
Once the user is satisfied with application or software, it is then deployed in market.
Upon receiving feedback from users, changes can be made to the project
4.1.1 Languages and Tools
The proposed application is developed in Android Studio, using Java as the programming
language with XML being responsible for designing the interfaces, that create the front end. The
front end consists of multiple activities each activity consisting of a java file and its
corresponding xml file.
The back end developed in firebase that provides authentication, real time storage, crash reports,
whose dependencies are to be loaded into the Android Studio. It provides complete details of
application and analytics regarding it, like the daily and monthly active users, the change in them
is also represented along with the number of crashes
Here we provide a brief description of technologies that we use while developing our application:

30
Implementation
Android Studio
Android Studio is a working environment where we can develop android applications using
JAVA, XML and by connecting with databases through the coding techniques. It provides ease
with its drag and drop feature and live view of the application that is being developed.
Google maps Application Programming Interface

Google Maps is a web mapping service developed by Google. It offers satellite imagery, aerial
photography, street maps, panoramic views of streets, real-time traffic conditions, and route
planningfor traveling by foot, car, bicycle and air, or public transportation.
Firebase database
The Firebase Realtime Database is a cloud-hosted database. Data is stored as JavaScript Object
Notation (JSON) and synchronized in real time to every connected client. When you build cross-
platform apps with our iOS, Android, and JavaScript software development kit (SDKs), all of
your clients share one Realtime Database instance and automatically receive updates with the
newest data.

31
Implementation
4.2 Database Design
Following Entity diagram shows tables, their attributes and their relationships with other tables.
Figure 4.2: Database Design
4.3 GUI
While developing an application, the interface and its design is one of most important part. While
developing this application, the aim main aim was to keep everything simple, because the
simpler the interface, the easier the usage becomes by a user. Following are some screenshots of
the application:

32
Implementation
Login Screen
The login screen of application. There are different fieldsfor username and password. The
background is set to blue and the register button is in pink color, the combination of blue and pink
color makes it easier to identify all the options thatare available.
Figure 4.3: Login Screen

33
Implementation
Admin Interface
The interface of admin. Each option has been shown in big block, in addition to that, the color of
each block is different so that it would be easier todistinguish between option.
Figure 4.4: Admin Interface

34
Passenger Interface
The interface of passenger. The selections are placedin different lines and a little further from
each other, so that users would not get confused among them. The background is blue so it
would not be too bright for eyes.
Figure 4.3: Passenger

Interfaces

35
TESTING

36
System Testing and Evaluation
This section covers the framework assessment and execution. Testing a framework guar-
antees that the modules of a framework work appropriately as per the normal outcomes.
First modules are tried independently a short time later the whole application is tried.
This is essentially the primary piece of a framework as it inspects whether the
application fulfills the guidelines which are required or not. The testing strategies are
referenced in this section which we’ve connected on our framework.
6.1 Interface testing
Interface testing is a mechanism to test a product’s user interface in order to ensure that
whether it meets the requirements or not..
6.1.1 Test Case for User Sign-up Form
This is the test case for signup to the web application. Signup test case was performed in
order to check if the user can sign-up into the android app properly.
Expected
Steps Task Actual
Outcomes
1 Sign-up screen/form Pass/Fail Pass
2 User name, emails/ password Pass/Fail Pass
Verify that the above mentioned success-
3 Pass/Fail Pass
fully
Verify that the signup button is displayed
4 Pass/Fail Pass
and work properly

37
Testing 35
Table 6.1: Test Case for user signup
6.1.2 Test Case for Log-in Screen Form
This test case is to test the log-in screen of the application. Test case was performed to
check if the user and a manager are logging into the android application properly or not.
Expected
Steps Task Actual
Outcomes
1 Open Log-in screen/form Pass/Fail Pass
Input the user username and password at
2 the same time for manager, emails and Pass/Fail Pass
password are used.
3 Pass/Fail Pass
fully
Verify that the sig-in button is displayed
4 Pass/Fail Pass
and work properly
Verify that each field of login screen is
5 Pass/Fail Pass
working properly
Table 6.2: Test Case for Log-in Screen
6.1.3 Test Case for Home Page Form
Test case for the home page of android application will verify that all the links on this page
are connected and are working properly.
Expected
Steps Task Actual
Outcomes
1 Open the home page Pass/Fail Pass
2 Verify that each menu items work properly Pass/Fail Pass
3 Pass/Fail Pass
fully
Verify that each menu link redirects to the
4 Pass/Fail Pass
desired main panel
Table 6.3: Test Case for Home Page
6.1.4 Test Case for user Portal/Interface
Test case for the user portal screen of android application will verify that all the links on
this page are connected and are working properly.

34
Testing 35
Expected
Steps Task Actual
Outcomes
1 Check the application register panel Pass/Fail Pass
Verfiy all the menu items are work prop-
2 Pass/Fail Pass
erly
3 Verify that all the items work properly Pass/Fail Pass
Verify that each menu item link redirects
4 Pass/Fail Pass
to the desired main application
Table 6.4: Test Case for user Portal/Interface
6.1.5 Test Case for manager Portal/Interface Form
Test case for the Manager portal screen of android application will verify that all the
links on this page are connected and are working properly.
Expected
Steps Task Actual
Outcomes
1 Open the application startup Pass/Fail Pass
Verify that the items of a menu are dis-
2 Pass/Fail Pass
played properly
Verify that all the menu items work prop-
3 Pass/Fail Pass
erly
Verify that each menu item link redirects
4 Pass/Fail Pass
to the desired main application
Verify that registration is done success-
5 Pass/Fail Pass
fully
6 Verify that admin can view data Pass/Fail Pass
7 Verify that admin can update record Pass/Fail Pass
Verify that admin receive the
8 Pass/Fail Pass
user/passenger information
Table 6.5: Test Case for Manager Interface
6.2 Usability Testing
Ease of use testing is performed so as to ensure that the application or programming is

anything but difficult to utilize. It very well may be accomplished by choosing a few clients
all together to utilize the framework and based on their input the issues are recognized
so as to determine them.

35
Testing 35
6.2.1 Usability Test Case for User Sign-up Screen Form
This test case will check if the button works properly while sign-up and signup process is
executing properly or not.
Expected
Steps Task Actual
Outcomes
1 Execute the android application Pass/Fail Pass
Verify that the register button working
2 Pass/Fail Pass
properly
Verify that submit button in passenger
3 Pass/Fail Pass
panel work properly
Table 6.6: Usability Test Case for User Sign-up Screen Form
6.2.2 Usability Test Case for log-in Screen Form
This test case will check if the button works properly while log-in and log-in process is
executing properly or not.
Expected
Steps Task Actual
Outcomes
1 Execute the android application Pass/Fail Pass
Verify that the register button working
2 properly in both passenger/admin/driver Pass/Fail Pass
work properly
Verify that user and admin login panel
3 Pass/Fail Pass
work properly
Table 6.7: Usability Test Case for log-in Screen
6.2.3 Usability Test Case for Insert / Update / Delete Record Form
Test case for inserting, deleting and updating records is going to verify that user records are
shown properly to the manager and the users who are registered in activity and users
those are going to add their own activities have separate records and they are saved
properly.

36
6.3 Exception Handling Testing 37
Expected
Steps Task Actual
Outcomes
Open the view student (admin panel) to
1 Pass/Fail Pass
view record
Verify the records which are store in
2 Pass/Fail Pass
database
Verify the reservation is done by passenger
3 Pass/Fail Pass
is completed
Verify that the user records are stored prop-
4 Pass/Fail Pass
erly
Table 6.8: Usability Test Case for Insertion/view
6.3 Exception Handling Testing
Special case dealing with test is utilized to foresee and distinguish the blunders in the
application and settling those mistakes which are left uncertain amid the improvement
stage.
6.3.1 Test Case for Log-in Exception Handling Form
This test case is for log-in form/ screen which will verify that the input fields will only
consider the right input. For user it will check that if the username and password match
properly. On the other hand for manager it will verify that if the email and password
match properly.
Expected
Steps Task Actual
Outcomes
1 Open the application Pass/Fail Pass
2 Open admin panel Pass/Fail Pass
Verify that all fields are accepting correct
3 Pass/Fail Pass
inputs, for both user/ and passengers
Verify that all username and password
4 Pass/Fail Pass
work perfectly
Table 6.9: Test Case for Log-in Exception Handling

37
6.4 Performance Testing
Application execution test is done so as to check the productivity too as the speed of the
web application. Fundamentally this procedure can be considered as a quantitative testing.
6.4.1 Test Case for Application Performance Form
This test case is going to verify the application’s overall performance that all
components or modules are responding properly.
Expected
Steps Task Actual
Outcomes
1 Open all the panels off applications Pass/Fail Pass
Select options from the van time or van
2 Pass/Fail Pass
NO
Verify that all fields are accepting correct
3 Pass/Fail Pass
inputs, for both user/ and passengers
Verify that all the data is storing in
4 Pass/Fail Pass
database
Table 6.10: Test Case for Application Performance

38
Conclusions
The project is designed to help students with their transport problems when it comes to
going to or coming from university. It is also designed to help the owner of van network
take control of whole network digitally. With its completion, it will be beneficial for all
the stakeholders involved in this whole scenario. Students will be able to select time to
pick them up. Drivers will be able to get student’s location and pick them up. Admin
will be able to keep track of all vans and will be notified whenever student makes a
request. Some people confuse our application with existing ones like Careem or Uber,
but the real difference between our application and those applications is that other
applications are designed for any type of user and our application is focused on
specific customers
e.g. people who already have pick and drop networks. We are focused to digitalize their
network operations. Our application will be good and beneficial for these type of people, it
will help them and students a great deal.
7.0.1 Assessment
The project helped us understand what challenges developers usually face when it comes
to making a proper application. In addition to that, implementing new technologies with
existing application is not a child’s play, it takes a lot of thinking and hard work to properly
implement the required technology. Our application is not that hard to use. Users will need
just one session of training and they will be good to go regarding the application’s usage.
We have learned how to properly test the system before it is implemented. With a lot of
hard work and research, we were able to accomplish the goals that we had in our minds.
39

39
40 Conclusions
7.0.2 Future
In future, it is expected that this application will not just be running in twin cities but in
other major countries of Pakistan. Moreover, other features will be added according to the
changing demands of customers. When it comes to using Google maps in the application,
it is going to be implemented at once, the application will be deployed in the areas of
concern, in this way it would be possible to pay the charges that Google requires when its
maps are used and implemented.

40
References
References
1 What Is Uber Exactly? Accessed on: Sep. 15, 2021. [Online].

Available:https://www.pocket-lint.com/apps/news/uber/139559-what-is-uber-
and-how-does-it-work.
2 Transportation Modes, Modal Competition and Modal Shift. Accessed on: Sep.
15, 2021. [Online].
Available:https://transportgeography.org/contents/chapter5/transportation-modes-
modal-competition-modal-shift/
3 Careem Alternatives and Competitors. Accessed on: Sep. 15, 2021. [Online].
Available:https://www.g2.com/products/careem/competitors/alternatives
4 Literature Searches and Literature Reviews for Transportation Research.
Accessed on: Sep. 15, 2021. [Online].
Available:https://onlinepubs.trb.org/onlinepubs/circulars/ec194.pdf
5 Examples of Effective Transportation Reviews. Accessed on: Sep. 15, 2021.
[Online].
6 Available:https://libguides.northwestern.edu/c.php?g=749215&p=5370469
7 RIDE-SHARING APPS AND PRIVACY IN PAKISTAN. Accessed on: Sep. 15,
2021. [Online]. Available:https://pk.mashable.com/tech/3594/ride-sharing-apps-
and-privacy-in-pakistan-drf-highlights-pakistans-legal-landscape-with-regards-
to-o
8 A Case study of Careem in Pakistan. Accessed on: Sep. 15, 2021. [Online].
Available:https://www.mdpi.com/2071-1050/11/15/3996.
9 Uber, Public Transit, and Urban Transportation Equity. Accessed
onSep.15,2021.[Online].Available:https://www.tandfonline.com/doi/abs/10.1080/
00330124.2018.1531038?journalCode=rtpg20&

Mobile Application For University Transportation

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mobile Application For University Transportation

Uploaded by

Copyright:

Available Formats

Mobile Application for University Transportation

Syed Azeem Hassan

Department of Computer Science

Syed Azeem Hassan

A dissertation submitted as a partial fulfillment of the requirements for the degree of

Department of Computer Science

Syed Azeem Hassan

Supervised By Sir Asim Ali

Examiner: Ms.Marium Azhar

Examiner: Ms. Isra Naz

Chairperson of Dr. Wazir Zada Khan

4.1.1 Languages and Tools........................................................................................23

4.2 Database Design.....................................................................................................24

Figure 1 Students have been facing severe transport proble............................2

Figure 3.1 Use Case for User and Admin......................................................21

Figure 2.2 Use Case for Driver and Admin...................................................21

Figure3.13 Picking up Students....................................................................30

Table 3.1 Use Case for Main Application…........................................................25

Mobile Application for University Transport

Mobile Application for University Transport

1.2 Problem Statement

Figure 1.3 University Student died in road accident

Mobile Application for University Transport

i) Inefficient and time consuming

1.3 Aims and Objectives

Mobile Application for University Transport

1.4 Scope of the Project

Mobile Application for University Transport

determine each bus stop.

Mobile Application for University Transport

1.5 Tools and Techniques

The proposed application is developed in Android Studio, using Java as the

Mobile Application for University Transport

Mobile Application for University Transport

2.1 Literature Review

Here, some similar technologies are discussed

Figure 2.1 Uber Application Interface

Mobile Application for University Transport

Figure 2.2 Ola cab Application Interface

Figure 2.3 Bykea Application Interface

Mobile Application for University Transport

Figure 2.4 Careem Application Interface

Figure 2.5 inDriver Application Interface

Mobile Application for University Transport

Figure 2.6 Swvl Application Interface

Mobile Application for University Transport

3. Design and Methodology

Mobile Application for University Transport

3.1.1 Transport Admin Interface

Mobile Application for University Transport

3.2 System Architecture

Figure 3.1 Use Case for User and Admin

Mobile Application for University Transport

Figure 3.2 Use Case for Driver and Admin

3.3 Functional Requirements

These are the functional requirements of our system.

Mobile Application for University Transport

Mobile Application for University Transport

3.3.1 Non-Functional Requirements

These are the non-functional requirements of our system.

Mobile Application for University Transport

3.3.2 Data Flow Diagram

Mobile Application for University Transport