RESTREADOR

By

MUAZ IFTIKHAR 13051519-019

KHADEEJA SARFRAZ GUNDRA 13051519-114
QURRAT-UL-AIN 13051519-027
BS Computer Science

Department of Computer Science

Degree of Computing & Information Technology

University of Gujrat
Session 2013-17

© Project Management Office Revised Version 2.4.14

Faculty of Computing& Information Technology, University of Gujrat. I
 ACKNOWLEDGEMENTS

First of all, all praise of Almighty Allah, the most beneficent, the most

merciful. Without His great blessings, we could not have been able to achieve our goal.

After that the praise of Holy Prophet (PBUH), the last messenger of Allah

Almighty, whose spiritual guidance always guided us in every moment of life.

We remain indebted to our parents, family members for providing us f or the

moral support in completion of our project.

We would also like to pay our heartiest gratitude to our respected teachers: Mam

Shakra Mehak, Sir Talha Arshad and beloved brother Anas Iftikhar Mir; who gave us a

continuous moral support through out this project.

Lastly, we want to thank all the people who helped us in any way to complete

our project.

Muaz Iftikhar
____________________
Khadeeja Sarfraz Gundra
____________________
Qurrat-ul-ain
___________________

II
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 DEDICATION

We dedicate this project to God Almighty our creator, our strong pillar, our source of
inspiration, wisdom, knowledge and understanding. He has been the source of our
strength throughout this program and on His wings only have we soared. We also
dedicate this work to our parents who have encouraged us all the way and whose
encouragement has made sure that we gave it all it takes to finish that which we have
started. To our teachers: Mam Farzana Younas, Mam Shakra Mehak, Sir Talha Arshad
and brother: Anas Iftikhar Mir.

Thank you for you all can never be quantified. God bless you.

III
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 DECLARATION

We Muaz Iftikhar S/o Iftikhar Ahmad, roll # 13051519-019, Khadeeja Sarfraz Gundra

D/o Sarfraz Hussain Gundra, roll #13051519-114, Qurrat-ul-ain D/o Abid Hussain Butt,

roll # 13051519-027 students of Bachelor of Science (Computer Science), Department of

Computing & Information Technology, University of Gujrat, Sialkot Sub Campus,

Pakistan, hereby solemnly declare that the data quoted in this thesis titled “Restreador”

is based on our original work, and has not yet been submitted or published elsewhere.

Muaz Iftikhar________________

Khadeeja Sarfraz Gundra________________

Qurrat-ul-ain________________

I certify that Muaz Iftikhar S/o Iftikhar Ahmad, roll # 13051519-019, Khadeeja Sarfraz

Gundra D/o Sarfraz Hussain Gundra, roll # 13051519-114, Qurrat-ul-ain D/o Abid

Hussain Butt, roll # 13051519-027, student of Bachelor of Science(Computer Science),

Department of Computing & Information Technology, University of Gujrat, Pakistan,

worked under my supervision and the above stated declaration is true to the best of my

knowledge.

FarzanaYounas________________
Department of Information & Technology
University of Gujrat, Punjab, Pakistan.
Email: farzana.younas@uogsialkot.edu.pk

Dated: ________________________________

IV
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 PROJECTCOMPLETION CERTIFICATE

It is verified that this thesis titled “Restreador” by Muaz Iftikhar S/o Iftikhar Ahmad,
roll # 13051519-019, Khadeeja Sarfraz Gundra D/o Sarfraz Hussain Gundra, roll #
13051519-114, Qurrat-ul-ain D/o Abid Hussain Butt, roll # 13051519-027, student of
Bachelor of Science (Computer Science), Department of Computing & Information
Technology, University of Gujrat, Pakistan, contains sufficient material required for the
award of above said degree.

FarzanaYounas
Department of Information & Technology
University of Gujrat, Punjab, Pakistan.
Email: farzana.younas@uogsialkot.edu.pk
______________

____________________________________________
Head of Department,
University of Gujrat, Punjab, Pakistan.
Dated: ------------------------------------------

V
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 TABLE OF CONTENTS
CONTENTS PAGE
CHAPTER-1 ....................................................................................................... 3
1.1 Introduction ................................................................................................................... 3
1.2 Background and Existing System ................................................................................. 3
1.2.1 Problems in Existing System ................................................................................. 4
1.3 Proposed System ........................................................................................................... 4
1.3.1 Main Modules ........................................................................................................ 4
1.4 Expected Outcome ........................................................................................................ 4
1.5 Tools & Technology ..................................................................................................... 5
1.6 Activity Index ............................................................................................................... 5
CHAPTER-2 ....................................................................................................... 7
2.1 Requirement Analysis ................................................................................................... 7
2.1.1 Functional Requirements ....................................................................................... 7
2.1.2 Non- Functional Requirements .............................................................................. 7
2.1.2.1 Accessibility: .......................................................................................... 7
2.1.2.2 Availability: ........................................................................................... 8
2.1.2.3 Maintainability:..................................................................................... 8
2.1.2.4 Performance: ......................................................................................... 8
2.1.2.5 Reliability: ............................................................................................. 8
2.1.2.6 Security: ................................................................................................. 8
2.1.2.7 Integrity: ................................................................................................ 8
2.2. Use Case Diagram........................................................................................................ 9
2.2.1 System Use Case:...................................................................................... 9
2.2.1.1 System View: ......................................................................................... 9
1. User Application ......................................................................................................... 9
2.2.1.2 Registration: .......................................................................................... 9
2.2.1.3 Get Information: ................................................................................. 10
2. Admin Panel.............................................................................................................. 10
2.2.1.4 Main Modules: .................................................................................... 10
2.2.1.5 Management Module: ......................................................................... 11
2.2.1.6 History Module: .................................................................................. 12

VI
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
2.3. Use Cases ................................................................................................................... 13
1. User Application ........................................................................................................... 13
2.3.1 Registration .......................................................................................................... 13
2.3.2 Get Information .................................................................................................... 14
a. Login............................................................................................................. 14
b.Get Location ................................................................................................. 14
c. Map ............................................................................................................... 15
d. History ......................................................................................................... 15
2.3.3Bus/Route Information ........................................................................... 16
2. Admin Panel.................................................................................................................. 16
2.3.4Management Module ............................................................................................ 16
a. Login............................................................................................................. 16
b. Add User ...................................................................................................... 17
c. Edit User ...................................................................................................... 17
d. Delete User ................................................................................................... 18
e. Add Stop....................................................................................................... 18
f. Edit Stop ....................................................................................................... 19
g. Delete Stop ................................................................................................... 19
h. Add Route .................................................................................................... 20
i. Edit Route ..................................................................................................... 20
j. Delete Route ................................................................................................. 21
k. Add Bus........................................................................................................ 21
l. Edit Bus......................................................................................................... 22
m. Delete Bus ................................................................................................... 22
n. Add Driver................................................................................................... 23
o. Edit Driver ................................................................................................... 23
p. Delete Driver ............................................................................................... 24
q. Registration Requests ................................................................................. 24
2.3.5 History.................................................................................................................. 25
a. Login............................................................................................................. 25
b. User History ................................................................................................ 25
2.3.6 Admin Logout ...................................................................................................... 26
a. Login............................................................................................................. 26

VII
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 b. Logout .......................................................................................................... 26
CHAPTER-3 ..................................................................................................... 28
3.1 UML Diagram ............................................................................................................. 28
3.1.1 Class Diagram: ..................................................................................................... 28
Circuit Diagram ................................................................................................................ 29
3.1.2 Circuit Diagram ................................................................................................... 29
Block Diagram .................................................................................................................. 30
3.1.3 Block Diagram ..................................................................................................... 30
3.1.4 Sequence Diagrams .............................................................................................. 31
1. User Application ....................................................................................................... 31
3.1.4.1 Sequence diagram for Registration ................................................... 31
3.1.4.2 Sequence diagram for Location Information: .................................. 31
3.1.4.3 Sequence diagram for History: .......................................................... 32
3.1.4.4 Sequence diagram for Bus/Route Information: ............................... 32
2. Admin Panel.............................................................................................................. 33
3.1.4.5 Management Module: ....................................................................................... 33
a. Admin Login: .............................................................................................. 33
b. Add User: ..................................................................................................... 33
c. Edit User: ..................................................................................................... 34
d. Delete User: ................................................................................................. 34
e. Add Stop: ..................................................................................................... 35
f. Edit Stop: ...................................................................................................... 35
g. Delete Stop: .................................................................................................. 36
h. Add Route: .................................................................................................. 36
i.Edit Route:..................................................................................................... 37
j. Delete Route: ............................................................................................... 37
k. Add Bus: ...................................................................................................... 38
l. Edit Bus: ....................................................................................................... 38
m. Delete Bus: .................................................................................................. 39
n. Add Driver: ................................................................................................. 39
o. Edit Driver:.................................................................................................. 40
p. Delete Driver: .............................................................................................. 40
q. Approval Requests: .................................................................................... 41

VIII
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 3.1.4.6 History Module: ................................................................................................ 41
a. History.......................................................................................................... 41
3.1.5 Domain Model ..................................................................................................... 42
CHAPTER-4 ..................................................................................................... 44
TESTING .......................................................................................................................... 44
4.1 Testing..................................................................................................................... 44
4.1.1 Get Registered. ....................................................................................... 44
REGISTRATION ............................................................................................... 44
4.1.2 Get Registered. ....................................................................................... 45
REGISTRATION ............................................................................................... 45
4.1.3 Login........................................................................................................ 46
LOGIN ................................................................................................................. 46
4.1.4 Bus/Route Information .......................................................................... 47
BUS/ROUTE INFORMATION......................................................................... 47
4.1.5 Registration ............................................................................................ 48
REGISTRATION ............................................................................................... 48
4.1.6 Login........................................................................................................ 49
LOGIN ................................................................................................................. 49
4.1.7 Bus/Route Information .......................................................................... 50
BUS/ROUTE INFORMATION......................................................................... 50
4.1.8 Registration ............................................................................................ 51
REGISTRATION ............................................................................................... 51
4.1.9 Login........................................................................................................ 52
LOGIN ................................................................................................................. 52
4.1.10 Bus/Route Information ........................................................................ 53
BUS/ROUTE INFORMATION......................................................................... 53
CHAPTER-5 ..................................................................................................... 55
Conclusion ........................................................................................................................ 55
Future Work ...................................................................................................................... 56
USER MANUAL .............................................................................................................. 58
1. User Manual for Application User ............................................................................ 58
a. Start Application ................................................................................... 58
b. Main Activity ......................................................................................... 59

IX
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 c. User Register .......................................................................................... 59
d. User Login .............................................................................................. 60
e. Get Location........................................................................................... 60
f. Location Information ............................................................................ 61
g. Maps ....................................................................................................... 61
h. Bus/Route Information ......................................................................... 62
2. User Manual for Admin Panel ................................................................................... 62
a. Admin Login .......................................................................................... 62
b. Admin Home Page ................................................................................. 62
c. Add New User ........................................................................................ 63
d. Edit User................................................................................................. 64
e. Delete User ............................................................................................. 64
f. Add Stop ................................................................................................. 64
g. Edit Stop ................................................................................................. 65
h. Delete Stop ............................................................................................. 65
i. Add Route .................................................................................................. 67
j. Edit Route .............................................................................................. 67
k. Delete Route ........................................................................................... 68
l. Add Bus ...................................................................................................... 68
m. Edit Bus .................................................................................................. 69
n. Delete Bus ............................................................................................... 69
o. Add Driver ............................................................................................. 70
p. Edit Driver ............................................................................................. 70
q. Delete Driver .......................................................................................... 71
r. History .................................................................................................... 71
s. Approval Requests ................................................................................ 72
t. Logout..................................................................................................... 72
REFERENCES ................................................................................................................. 74

X
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 LIST OF TABLES, FIGURES AND APPENDIXES

CONTENTS PAGE
Table 1.1 - Activity Index ............................................................................................... 5
Figure 2.1.1 - Use Case Diagram for System View ...................................................... 9
Figure 2.1.2 - Use Case Diagram for User Registration .............................................. 9
Figure 2.1.3 - Use Case Diagram for Getting Information ....................................... 10
Figure 2.1.4 - Use Case Diagram for Main Modules ................................................. 10
Figure 2.1.5 - Use Case Diagram for Management Module ...................................... 11
Figure 2.1.6 - Use Case Diagram for History Module ............................................... 12
Figure 3.1.1 – Class Diagram ....................................................................................... 28
Figure 3.1.1.1 – Circuit Diagram ................................................................................. 29
Figure 3.1.1.2 – Block Diagram ................................................................................... 30
Figure 3.1.2 – Sequence Diagram for User Registration ........................................... 31
Figure 3.1.3 – Sequence Diagram for Location Information .................................... 31
Figure 3.1.4 – Sequence Diagram for User History ................................................... 32
Figure 3.1.5 – Sequence Diagram for Bus/Route Information ................................. 32
Figure 3.1.6 – Sequence Diagram for Admin Login .................................................. 33
Figure 3.1.7 – Sequence Diagram for Add User ......................................................... 33
Figure 3.1.8 – Sequence Diagram for Edit User ......................................................... 34
Figure 3.1.9 – Sequence Diagram for Delete User ..................................................... 34
Figure 3.2.0 – Sequence Diagram for Add Stop ......................................................... 35
Figure 3.2.1 – Sequence Diagram for Edit Stop ......................................................... 35
Figure 3.2.2 – Sequence Diagram for Delete Stop...................................................... 36
Figure 3.2.3 – Sequence Diagram for Add Route ...................................................... 36
Figure 3.2.4 – Sequence Diagram for Edit Route ...................................................... 37
Figure 3.2.5 – Sequence Diagram for Delete Route ................................................... 37
Figure 3.2.6 – Sequence Diagram for Add Bus .......................................................... 38
Figure 3.2.7 – Sequence Diagram for Edit Bus .......................................................... 38
Figure 3.2.8 – Sequence Diagram for Delete Bus ....................................................... 39
Figure 3.2.9 – Sequence Diagram for Add Driver ..................................................... 39
Figure 3.3.0 – Sequence Diagram for Edit Driver ..................................................... 40

XI
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
Figure 3.3.1 – Sequence Diagram for Delete Driver .................................................. 40
Figure 3.3.2 – Sequence Diagram for Approval Requests ........................................ 41
Figure 3.3.3 – Sequence Diagram for History ............................................................ 41
Figure 3.3.4 – Domain Model ....................................................................................... 42
Figure 6.1.1 – User Manual of Application Start ....................................................... 58
Figure 6.1.2 – User Manual of Application Main Page ............................................. 58
Figure 6.1.3 – User Manual of User Register ............................................................. 59
Figure 6.1.4 – User Manual of User Login.................................................................. 59
Figure 6.1.5 – User Manual of Get Location .............................................................. 60
Figure 6.1.6 – User Manual of Location Information................................................ 60
Figure 6.1.7 – User Manual of Maps ........................................................................... 61
Figure 6.1.8 – User Manual of Bus/Route Information ............................................. 61
Figure 6.2.1 – User Manual of Admin Login .............................................................. 62
Figure 6.2.2 – User Manual of Admin Home Page .................................................... 62
Figure 6.2.3 – User Manual of Add User .................................................................... 63
Figure 6.2.4 – User Manual of Edit User .................................................................... 63
Figure 6.2.5 – User Manual of Delete User ................................................................. 64
Figure 6.2.6 – User Manual of Add Stop .................................................................... 64
Figure 6.2.7 – User Manual of Edit Stop .................................................................... 65
Figure 6.2.8 – User Manual of Delete Stop ................................................................. 65
Figure 6.2.9 – User Manual of Add Route .................................................................. 66
Figure 6.2.9 – User Manual of Edit Route .................................................................. 66
Figure 6.3.0 – User Manual of Delete Route ............................................................... 67
Figure 6.3.1 – User Manual of Add Bus ...................................................................... 67
Figure 6.3.2 – User Manual of Edit Bus ...................................................................... 68
Figure 6.3.3 – User Manual of Delete Bus .................................................................. 68
Figure 6.3.4 – User Manual of Add Driver ................................................................. 69
Figure 6.3.5 – User Manual of Edit Driver ................................................................. 69
Figure 6.3.6 – User Manual of Delete Driver.............................................................. 70
Figure 6.3.7 – User Manual of History........................................................................ 70
Figure 6.3.8 – User Manual of Approval Requests .................................................... 71
Figure 6.3.9 – User Manual of Logout ........................................................................ 71

XII
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 ABSTRACT

We have studied different tracking systems, which are being used by different
universities. Most of the universities have same features installed in their tracking
application. Register, Login, Real time location etc. but there is no such product which
covers multiple information about transport like bus/route info, history.

For the fulfillment of this need an application has to be developed which covers these
requirements in which no invalid or non-registered user could track the bus so that
privacy and efficiency should be increased.

We have developed such an application which cover these requirements. Our target
audience is every user which is an authorized transport user whether it may be a student
or faculty member. It is way easy to use this application which will be handled by any
authorized transport managing person as an admin.

© Project Management Office Revised Version 2.4.14

Faculty of Computing& Information Technology, University of Gujrat. 1
 CHAPTER 1
INTRODUCTION

2
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 CHAPTER-1

INTRODUCTION

1.1 Introduction

“Restreador”: A University Bus Tracking System: Tracking buses of university over

different routes.
Student first has to register over the application for once. Student id will be saved in
database working in the server behind which will help him/her in continuous tracking.
GPS trackers will be used in buses which will help to track them, these trackers will
be linked up with server of this android application, any student availing university
transport will be able to locate the current position of the specific bus on request.
Google Map will help to locate direction and location of bus. Routes of buses will
also be available for the Students to get information of bus stop. This route information
will help students to get register on exact route bus.

1.2 Background and Existing System

Bus System is totally manual; students have to get to transport head to get
information about the relevant bus, in case of his absence, leads to much difficulty. Buses
are not tracked whether it is on exact route or not. The only way management can know,
the bus location is by calling the driver which will, may be affected if sim card service is
not available.
Students often miss their bus because of the time issue. Mismatch of time between
students and transport lead to great loss in their studies and also they had to wait at off
time for the arrival of bus. Unexpected delays could happen: any traffic problem or
accidents may result in late arrival of the bus, in case, students have no idea where the
bus is.
Sometimes due to bad weather the time allocated for the bus arrival was disturbed, which
ultimately lead to a total chaos in overall management of transport system. Therefore to
3
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
overcome such mishaps there should be trackers installed in each bus, so that students
could communicate and reduce their headache.

1.2.1 Problems in Existing System

 Buses are not tracked whether where they are.

 Students often miss their bus because of timing issue.
 Late arrival of bus due to traffic congestion.
 Unexpected delays of buses.

1.3 Proposed System

“Restreador” is an application for smart phones that works on Android Operating

System.
This system will provide more convenience bus schedule to students as at specific
pickup point it will send the location of the bus to students when they request. Integrated
Google maps will help to track the location of the bus using GPS.
This system will also provide routes of the buses by which student would be able to
catch the exact bus.

1.3.1 Main Modules

 Registration of student for specific bus number.

 Location information
 Maps
 Bus/Route information

1.4 Expected Outcome

An Android application which will be able to provide location of buses, schedules for
the buses. It will provide current location to the student.
4
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
1.5 Tools & Technology

Tools: Android Studio (Android 4.1 Minimum), SQLite Database, Android SDK, Visual
Studio 2015, SQL Server Management Studio, Notepad++, Sublime Text 2, Adobe
Photoshop
Technologies: GPS, Google Map API (Maps Android API), Static IP
Languages: Java, SQL, XML, C#, MS SQL, JavaScript
Hardware: GPS Tracker, Server (Minimum Requirement: Core 2 duo, RAM: 4 GB,
Hard Disk 250GB)

1.6 Activity Index

No. Activity Duration Deliverables

1. System 3 weeks Requirement gathered and

requirement documentation
and gathering

2. Proposal 2 weeks Proposed System

Writing

3. System design 3 weeks Data organized logically and

systematically

4. Layout And 6 weeks Layout and interface designed

Design

5. Developing 7 weeks Properly functional app

6. Testing 2 weeks Code test

7. Documentation 3 weeks Project And Documentation

Total Weeks 26 weeks

Table 1.1 - Activity Index

5
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 CHAPTER 2
REQUIREMENT ANALYSIS

6
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 CHAPTER-2

REQUIREMENT ANALYSIS

2.1 Requirement Analysis

In this chapter, the emphasis will be to investigate different types of requirement of

Restreador. Instead of looking at the possible solutions, we will try to elicit functional
and non-functional requirements of Restreador. Here in this chapter, we will try to find
‘WHAT’ not ‘HOW’. We will find what will be the requirement of Restreador and write
those requirements in separate sections according to their types. Now, few requirements
are critical or functional, they will define the basic user goals and their objectives in
Restreador. Beside functional requirements, there are other types of requirements which
are also quite important for the system with some aspect. Let’s take a look of them.

2.1.1 Functional Requirements

Functional requirement is refer to the functionalities must be apply to a system.

The functional requirements of bus tracking system are stated below.
1. The system must be able to allow users to register themselves.
2. The system must be able to allow user retrieve information from mobile
device.
3. The system must be able to show bus route information to the registered user.
4. The system must be able to show real time bus location to the user.
5. The system must be able to do mapping with the position data retrieved from
bus positioning module and show the bus position in a map view to user.

2.1.2 Non- Functional Requirements

2.1.2.1 Accessibility:
Every valid user can access system quite easily, fast and
effectively. Since Restreador will be hosted on web so for
accessibility, Local Area Network is the key.
7
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 2.1.2.2 Availability:
Restreador will be available to every valid and authentic user. It
should be available to users over LAN and World Wide Web. The
system shall achieve 100 per cent availability at all times.

2.1.2.3 Maintainability:
The system will be optimized for supportability or ease of
maintenance as far as possible. This may be achieved through the use
and documentation of coding standards.
2.1.2.4 Performance:
It refers to three properties,
 Response time: The system should not take much time to load
the application, screen open and refresh time should also be
minimum.
 Processing time: It should not take much time in retrieving
information.
 Query and Reporting Time: The system should not take
much time to response a query.
2.1.2.5 Reliability:
The system should be reliable that it should not get failure; if it
fails then it must not take much time to back up again.
2.1.2.6 Security:
The system shall provide secure client to server communication.
The database and application should be secure and authentic. It also refers
to login requirements and password requirements.
2.1.2.7 Integrity:
The system should tell how to support the referential integrity in
database tables and interfaces.

8
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
2.2. Use Case Diagram

2.2.1 System Use Case:

2.2.1.1 System View:

Figure 2.1.1 - Use Case Diagram for System View

1. User Application
2.2.1.2 Registration:

Figure 2.1.2 - Use Case Diagram for User Registration

9
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
2.2.1.3 Get Information:

Figure 2.1.3 - Use Case Diagram for Getting Information

2. Admin Panel
2.2.1.4 Main Modules:

Figure 2.1.4 - Use Case Diagram for Main Modules

10
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
2.2.1.5 Management Module:

Figure 2.1.5 - Use Case Diagram for Management Module

11
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
2.2.1.6 History Module:

Figure 2.1.6 - Use Case Diagram for History Module

12
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 2.3. Use Cases

1. User Application

2.3.1 Registration

Use Case Name Registration

Scope User-Level
Level User-goal
Primary Actor User
Description User will register to use the system
Preconditions Application must be running. Whenever an user wants to register to
use the application
Main Success Actor System
Scenario 1: User will have a page where 1: System will send the
he can register himself to use registration request to server.
the application.

Post Condition If successful, User will register to the system.

13
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 2.3.2 Get Information

a. Login
Use Case Name Location Information
Scope User-Level
Level User-goal
Primary Actor User
Description Actors will login by roll number and password to locate bus.
Preconditions Application must be running. Whenever an Actor wants to locate a bus
by logging in.
Main Success Actor System
Scenario 1: User enters data to login to 1: Systemchecksdata and let
application. user logged in.

Post Condition If successful, User will logininto the system.

b.Get Location

Use Case Name Get Location

Scope User-Level
Level User-goal
Primary Actor User
Description Actors will select to see location information.
Preconditions Application must be running and actor must be logged in whenever an
Actor wants to see location information.
Main Success Actor System
Scenario 1: User see the location 1: System shows the real time
information of bus on which user location information of the bus.
is registered.

Post Condition If successful, User will get the real time location information of the bus.

14
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 c. Map
Use Case Name Map
Scope User-Level
Level User-goal
Primary Actor User
Description Actors will select to see location information on map.
Preconditions Application must be running and actor must be logged in whenever an
Actor wants to see location information on map.
Main Success Actor System
Scenario 1: User can see the location of 1: System shows the real time
bus on map. location of the bus on map.

Post Condition If successful, Userwill get the real time location of bus on map.

d. History
Use Case Name History
Scope User-Level
Level User-goal
Primary Actor User
Description Actors will select to see history of their locations.
Preconditions Application must be running and actor must be logged in whenever an
Actor wants to see history.
Main Success Actor System
Scenario 1: User see the history of the 1: System shows a user the
locations user had received. history of the locations user had
requested.

Post Condition If successful, User will get the history of the requested locations.

15
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 2.3.3Bus/Route Information
Use Case Name Bus/Route Information
Scope User-Level
Level User-goal
Primary Actor User
Description Actors will see the details about bus no and its route.
Preconditions Application must be running. Whenever an Actor wants to get bus/route
information.
Main Success Actor System
Scenario 1: Usercan see detailed 1: System providesuserwith
information about buses and thedetailedinformation about
routes. buses and routes.

Post Condition Ifsuccessful, Userwill get the buses and routes information.

2. Admin Panel

2.3.4Management Module

a. Login
Use Case Name Admin Login
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Admin will login to the admin panel.
Preconditions Server Must be running.

Main Success Actor System

Scenario 1: Admin enter required data to 1: System provide Admin with a
log in. login page to access to admin
panel.

Post Condition Admin successfully logged in to admin panel.

16
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 b. Add User
Use Case Name Add User
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Allows an admin to add new user
Preconditions Admin must be logged in to admin panel.

Main Success Actor System

Scenario 1: Adminperform work to add 1: System stores the data of user
new user. in database.

Post Condition If successful, system will add new user in database.

c. Edit User
Use Case Name Edit User
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Allows an admin to edit user profile
Preconditions Admin must be logged in to admin panel and user profile must exists in
database.
Main Success Actor System
Scenario 1: Admin selects the user. 1: System shows the profile of
user.
2: Admin edits the user profile. 2: System stores it in database.

Post Condition If successful, system will editexisting user profile.

17
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 d. Delete User
Use Case Name Delete User
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Allows an admin to delete user profile
Preconditions Admin must be logged in to admin panel and user profile must exists in
database.
Main Success Actor System
Scenario 1: Admin selects the user. 1: System shows the profile of
user.
2: Admin deletes the user 2: System asks for confirmation
profile. (Yes/No).
3: System deletes the user
profile from database.

Post Condition If successful, system will delete user profile from database.

e. Add Stop
Use Case Name Add Stop
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Allows an admin to add new stop
Preconditions Admin must be logged in to admin panel.

Main Success Actor System

Scenario 1: Admin perform work to add 1: System stores the data ofstop
new stop. in database.

Post Condition If successful, system will add new stop in database.

18
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 f. Edit Stop
Use Case Name Edit Stop
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Allows an admin to edit stop
Preconditions Admin must be logged in to admin panel and stop record must exists in
database.
Main Success Actor System
Scenario 1: Admin selects the stop. 1: System shows the record of
stop.
2: Admin edits the stop record. 2: System stores it in database.

Post Condition If successful, system will edit existing stop record.

g. Delete Stop
Use Case Name Delete Stop
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Allows an admin to delete stop record
Preconditions Admin must be logged in to admin panel and stop record must exists in
database.
Main Success Actor System
Scenario 1: Admin selects the stop. 1: System shows the stop record.
2: System asks for confirmation
2: Admin deletes the stop (Yes/No).
record. 3: System deletes the stop
record from database.

Post Condition If successful, system will delete stop record from database.

19
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 h. Add Route
Use Case Name Add Route
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Allows an admin to add new route
Preconditions Admin must be logged in to admin panel.

Main Success Actor System

Scenario 1: Admin perform work to add 1: System stores the data of
new route. route in database.

Post Condition If successful, system will add new route in database.

i. Edit Route
Use Case Name Edit Route
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Allows an admin to edit route record
Preconditions Admin must be logged in to admin panel and route record must exists in
database.
Main Success Actor System
Scenario 1: Admin selects the route. 1: System shows the record of
route.
2: Admin edits the route record. 2: System stores it in database.

Post Condition If successful, system will edit existing route record.

20
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 j. Delete Route
Use Case Name Delete Route
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Allows an admin to delete route record
Preconditions Admin must be logged in to admin panel and route record must exists in
database.
Main Success Actor System
Scenario 1: Admin selects the route. 1: System shows the route
record.
2: Admin deletes the route 2: System asks for confirmation
record. (Yes/No).
3: System deletes the route
record from database.

Post Condition If successful, system will delete route record from database.

k. Add Bus
Use Case Name Add Bus
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Allows an admin to add new bus
Preconditions Admin must be logged in to admin panel.

Main Success Actor System

Scenario 1: Admin perform work to add 1: System stores the data of bus
new bus record. in database.

Post Condition If successful, system will add new bus in database.

21
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 l. Edit Bus
Use Case Name Edit Bus
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Allows an admin to edit bus record
Preconditions Admin must be logged in to admin panel and bus record must exists in
database.
Main Success Actor System
Scenario 1: Admin selects the bus. 1: System shows the record of
bus.
2: Admin edits the bus record. 2: System stores it in database.

Post Condition If successful, system will edit existing bus record.

m. Delete Bus
Use Case Name Delete Bus
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Allows an admin to delete bus record
Preconditions Admin must be logged in to admin panel and bus record must exists in
database.
Main Success Actor System
Scenario 1: Admin selects the bus. 1: System shows the bus record.
2: System asks for confirmation
2: Admin deletes the bus record. (Yes/No).
3: System deletes the bus record
from database.

Post Condition If successful, system will delete bus record from database.

22
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 n. Add Driver
Use Case Name Add Driver
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Allows an admin to add new driver profile
Preconditions Admin must be logged in to admin panel.

Main Success Actor System

Scenario 1: Admin perform work to add 1: System stores the driver
new driver profile. profile in database.

Post Condition If successful, system will add driver profile in database.

o. Edit Driver
Use Case Name Edit Driver
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Allows an admin to edit driver profile
Preconditions Admin must be logged in to admin panel and driver profile must exists in
database.
Main Success Actor System
Scenario 1: Admin selects the driver. 1: System shows the driver
profile.
2: Admin edits the driver profile. 2: System stores it in database.

Post Condition If successful, system will edit existing driver profile.

23
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 p. Delete Driver
Use Case Name Delete Driver
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Allows an admin to delete driver profile
Preconditions Admin must be logged in to admin panel and driver profile must exists in
database.
Main Success Actor System
Scenario 1: Admin selects the driver. 1: System shows the driver
profile.
2: Admin deletes the driver 2: System asks for confirmation
profile. (Yes/No).
3: System deletes the driver
profile from database.

Post Condition If successful, system will delete bus record from database.

q. Registration Requests
Use Case Name Registration Requests
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Admin can manage registration requests.
Preconditions Admin must be logged in and requests should be pending.

Main Success Actor System

Scenario 1: Admin selects to manage
registration requests.
2: Admin accepts or reject the
requests
1: System will provide admin
with all the pending registration
requests.
2: If accepts, system stores the
data in database and vice versa.

Post Condition Manager managed the Registrations.

24
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 2.3.5 History

a. Login
Use Case Name Admin Login
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Admin will login to the admin panel.
Preconditions None

Main Success Actor System

Scenario 1: Admin enter required data to 1: System provide Admin with a
log in. login page to access to admin
panel.

Post Condition Admin successfully logged in to admin panel.

b. User History
Use Case Name User History
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Admin can see Users History.
Preconditions Admin must be logged in and user must have requested for location at
least one time.
Main Success Actor System
Scenario 1: Admin can see users History. 1: System will provide admin
with the users History.

Post Condition Manager could see Users History.

25
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 2.3.6 Admin Logout

a. Login
Use Case Name Admin Login
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Admin will login to the admin panel.
Preconditions None

Main Success Actor System

Scenario 1: Admin enter required data to 1: System provide Admin with a
log in. login page to access to admin
panel.

Post Condition Admin successfully logged in to admin panel.

b. Logout
Use Case Name Logout
Scope Admin-Level
Level Admin-goal
Primary Actor Admin
Description Admin can logout from the admin panel.
Preconditions Admin must be logged in.

Main Success Actor System

Scenario 1: Admin can Logout from admin 1: System will provide admin
panel. with options for Logging out and
2: Admin selects logout option. Cancel.
2: If admin selects logout,
system get it out from the
session and vice versa.

Post Condition Manager successfully Logged out.

26
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 CHAPTER 3
DESIGN

27
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 CHAPTER-3
DESIGN

3.1UML Diagram

3.1.1 Class Diagram:

Figure 3.1.1 – Class Diagram

28
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 Circuit Diagram

3.1.2 Circuit Diagram

Figure 3.1.1.1 Block Diagram

29
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 Block Diagram

3.1.3 Block Diagram

Figure 3.1.1.2 Block Diagram

30
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
Circuit Diagram

3.1.4 Sequence Diagrams

1. User Application

3.1.4.1Sequence diagram for Registration

Figure 3.1.2 – Sequence Diagram for User Registration

3.1.4.2 Sequence diagram for Location Information:

Figure 3.1.3 – Sequence Diagram for Location Information

31
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
3.1.4.3 Sequence diagram for History:

Figure 3.1.4 – Sequence Diagram for User History

3.1.4.4 Sequence diagram for Bus/Route Information:

Figure 3.1.5 – Sequence Diagram for Bus/Route Information

32
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
2. Admin Panel

3.1.4.5 Management Module:

a. Admin Login:

Figure 3.1.6 – Sequence Diagram for Admin Login

b. Add User:

Figure 3.1.7 – Sequence Diagram for Add User

33
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 c. Edit User:

Figure 3.1.8 – Sequence Diagram for Edit User

d. Delete User:

Figure 3.1.9 – Sequence Diagram for Delete User

34
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
e. Add Stop:

Figure 3.2.0 – Sequence Diagram for Add Stop

f. Edit Stop:

Figure 3.2.1 – Sequence Diagram for Edit Stop

35
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
g. Delete Stop:

Figure 3.2.2 – Sequence Diagram for Delete Stop

h. Add Route:

Figure 3.2.3 – Sequence Diagram for Add Route

36
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 i. Edit Route:

Figure 3.2.4 – Sequence Diagram for Edit Route

j. Delete Route:

Figure 3.2.5 – Sequence Diagram for Delete Route

37
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
k. Add Bus:

Figure 3.2.6 – Sequence Diagram for Add Bus

l. Edit Bus:

Figure 3.2.7 – Sequence Diagram for Edit Bus

38
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
m. Delete Bus:

Figure 3.2.8 – Sequence Diagram for Delete Bus

n. Add Driver:

Figure 3.2.9 – Sequence Diagram for Add Driver

39
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 o. Edit Driver:

Figure 3.3.0 – Sequence Diagram for Edit Driver

p. Delete Driver:

Figure 3.3.1 – Sequence Diagram for Delete Driver

40
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 q. Approval Requests:

Figure 3.3.2 – Sequence Diagram for Approval Requests

3.1.4.6 History Module:

a. History

Figure 3.3.3 – Sequence Diagram for History

41
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
3.1.5 Domain Model

Figure 3.3.4 – Domain Model

42
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 CHAPTER 4
TESTING

43
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 CHAPTER-4
TESTING

4.1 Testing

We had tested various modules of application. Test Engineers were Muaz Iftikhar,
Qurrat-ul-ain Abid and Kadeeja Sarfraz Gundra. Some of the test cases also failed
because of certain reasons.

4.1.1 Get Registered.

REGISTRATION
Test Engineer: Mr. Muaz Iftikhar
Test Case ID: TC1
Related UC/FR/NFR UC 2.3.1
Date: July 31st, 2017
Purpose: To get registered as a user.
Pre-Req: Get registered and check location.
Test Data: Bus Information, Register.

Steps: Steps to carry out the test.

1. Open application.
2. Enter Data
3. Register

Status: Fail.

44
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
4.1.2 Get Registered.

REGISTRATION
Test Engineer: Mr. Muaz Iftikhar
Test Case ID: TC1
Related UC/FR/NFR UC 2.3.1
Date: July 31st, 2017
Purpose: To get registered as a user.
Pre-Req: Get registered and check location.
Test Data: Bus Information, Register.

Steps: Steps to carry out the test.

1. Open application.
2. Enter Data
3. Register

Status: Pass

45
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
4.1.3 Login

LOGIN
Test Engineer: Mr. Muaz Iftikhar
Test Case ID: TC2
Related UC/FR/NFR UC 2.3.2
Date: August 1st, 2017
Purpose: Check location of the bus.
Pre-Req: Login and check information.
Test Data: LOGIN, Bus No. ,Map. ,

Steps: Steps to carry out the test.

1. Open application.
2. Login.
3. Map

Status: Pass.

46
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
4.1.4 Bus/Route Information

BUS/ROUTE INFORMATION
Test Engineer: Mr. Muaz Iftikhar
Test Case ID: TC3
Related UC/FR/NFR UC 2.3.3
Date: August 4th, 2017
Purpose: To check the route of the selected bus.
Pre-Req: Locate the selected bus.
Test Data: Get Information, Bus No., Login.. ,

Steps: Steps to carry out the test.

1. Open application.
2. Enter Data
3. View Details

Status: Pass.

47
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
4.1.5 Registration

REGISTRATION
Test Engineer: Ms Khadeeja Gundra
Test Case ID: TC 4
Related UC/FR/NFR UC 2.3.1
Date: August 7th, 2017
Purpose: To get registered as a user.
Pre-Req: Get registered and check location.
Test Data: Bus Information, Register.

Steps: Steps to carry out the test.

1. Open application.
2. Enter Data
3. Register

Status: Pass

48
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
4.1.6 Login

LOGIN
Test Engineer: Ms Khadeeja Gundra
Test Case ID: TC 5
Related UC/FR/NFR UC 2.3.2
Date: August 7th, 2017
Purpose: Check location of the bus.
Pre-Req: Login and check information.
Test Data: LOGIN, Bus No. ,Map. ,

Steps: Steps to carry out the test.

1. Open application.
2. Login.
3. Map

Status: Pass.

49
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
4.1.7 Bus/Route Information

BUS/ROUTE INFORMATION
Test Engineer: Ms Khadeeja Gundra
Test Case ID: TC 6
Related UC/FR/NFR UC 2.3.3
Date: August 7th, 2017
Purpose: To check the route of the selected bus.
Pre-Req: Locate the selected bus.
Test Data: Get Information, Bus No., Login.. ,

Steps: Steps to carry out the test.

4. Open application.
5. Enter Data
6. View Details

Status: Pass.

50
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
4.1.8 Registration

REGISTRATION
Test Engineer: Ms. Qurrat-ul-Ain
Test Case ID: TC 7
Related UC/FR/NFR UC 2.3.1
Date: August 10th, 2017
Purpose: To get registered as a user.
Pre-Req: Get registered and check location.
Test Data: Bus Information, Register.

Steps: Steps to carry out the test.

1. Open application.
2. Enter Data
3. Register

Status: Pass

51
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
4.1.9 Login

LOGIN
Test Engineer: Ms. Qurrat-ul-Ain
Test Case ID: TC 8
Related UC/FR/NFR UC 2.3.2
Date: August 10th, 2017
Purpose: Check location of the bus.
Pre-Req: Login and check information.
Test Data: LOGIN, Bus No. ,Map. ,

Steps: Steps to carry out the test.

4. Open application.
5. Login.
6. Bus No.
7. Map

Status: Pass.

52
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
4.1.10 Bus/Route Information

BUS/ROUTE INFORMATION
Test Engineer: Miss Qurrat-ul-Ain
Test Case ID: TC 9
Related UC/FR/NFR UC 2.3.3
Date: August 10th, 2017
Purpose: To check the route of the selected bus.
Pre-Req: Locate the selected bus.
Test Data: Get Information, Bus No., Login.. ,

Steps: Steps to carry out the test.

1. Open application.
2. Enter Data
3. View Details

Status: Pass.

53
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 CHAPTER 5
CONCLUSION &
FUTURE WORK

54
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 CHAPTER-5
CONCLUSION & FUTURE WORK

Conclusion

The conclusions of this study suggest that knowledge of specific domain improves the

results. This Project has been implemented on Android platform. Also, different attributes

have been added to the project which will prove to be advantageous to the system. The

requirements and specifications have been listed above. This project is implemented

using Android and the SQL domain. Using the GPS system, the application will

automatically display routes to the different destinations and also track the real time bus

location using client-server technology and forward it to the client device. Specific

location details are provided to the user w.r.t the bus no. so that the person can identify

the bus location correctly. This application also creates history of every user which can

also be viewed by the user itself.

55
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 Future Work

In near future, we are intended to add certain more modules in order to make it more

efficient and user friendly.

1. Speed

Current speed of the vehicle will also be shown so that the estimated arrival time

of the bus could be known.

2. Fuel

Fuel quantity in the vehicle will be shown on application.

3. Distance Limit

Distance limitations could be settled for more privacy and to avoid vehicle theft.

4. Ignition

Ignition alert message would be sent on sim card number.

5. Heat up Alert

Car heating up alert message would be sent to user.

56
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 USER MANUAL

57
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 USER MANUAL

1. User Manual for Application User

a. Start Application

Figure 6.1.1– User Manual of Application Start

It is the startup activity of “Restreador” which will lead to main page

automatically after 5 seconds of progress bar working.

58
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 b. Main Activity

Figure 6.1.2– User Manual of Application Main Page

Main page have different modules to be used, some can be used without Login while
others need a login.

c. User Register

Figure 6.1.3– User Manual of User Register

New Users (Students/Faculty) can register them by entering the registration button in
order to use the main function of application

59
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 d. User Login

Figure 6.1.4– User Manual of User Login

Registered users can log in by adding valid their Register number of university and
password in order to use the main function of the application.

e. Get Location

Figure 6.1.5– User Manual of Get Location

User can get Location of their bus and History of the previous locations which user had
requested.

60
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 f. Location Information

Figure 6.1.6– User Manual of Location Information

Coordinates (Latitudes and Longitudes) are shown in boxes which are the real time
location coordinates of the bus.

g. Maps

Figure 6.1.7– User Manual of Maps

User can see the real time location of the bus on map so that the exact location can be
known.

61
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 h. Bus/Route Information

Figure 6.1.8– User Manual of Bus/Route Information

2. User Manual for Admin Panel

a. Admin Login

Figure 6.2.1– User Manual of Admin Login

This is the admin login page of Restreador. Admin access to Restreador admin panel
must have username and password. If the username and password are authenticated then
system will be accessible to admin otherwise access is denied and invalid
username/password message is displayed.

b. Admin Home Page

62
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 Figure 6.2.2– User Manual of Admin Home Page

This is the main page for the admin user. Administrator must have a username and
password to access the system. Administrator can do multiple tasks. The tasks will be
explained later in document.

c. Add New User

Figure 6.2.3– User Manual of Add User

On this page you have to give some basic info of the user to be added. This is the basic
page to enter a user into your record.

63
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 d. Edit User

Figure 6.2.4– User Manual of Edit User

This page is for editing in user profile. Admin can edit user info here simply by searching
the user first.
e. Delete User

Figure 6.2.5– User Manual of Delete User

This page is for deleting user profile. Admin can delete user here simply by searching the
user first.

f. Add Stop

64
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 Figure 6.2.6– User Manual of Add Stop

On this page you have to give some basic info of the stop to be added. This is the basic
page to enter a stop into your record.
g. Edit Stop

Figure 6.2.7– User Manual of Edit Stop

This page is for editing in stop information. Admin can edit stop info here simply by
searching the stop first.

h. Delete Stop

65
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 Figure 6.2.8– User Manual of Delete Stop

This page is for deleting stop information. Admin can delete stop here simply by
searching the stop first.

66
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 i. Add Route

Figure 6.2.9– User Manual of Add Route

On this page you have to give some basic info of the route to be added. This is the basic
page to enter a route into your record.

j. Edit Route

Figure 6.2.9– User Manual of Edit Route

This page is for editing in route information. Admin can edit route info here simply by
searching the route first.

67
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 k. Delete Route

Figure 6.3.0– User Manual of Delete Route

This page is for deleting route information. Admin can delete route here simply by
searching the route first.

l. Add Bus

Figure 6.3.1– User Manual of Add Bus

On this page you have to give some basic info of the bus to be added. This is the basic
page to enter a bus into your record.
68
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 m. Edit Bus

Figure 6.3.2– User Manual of Edit Bus

This page is for editing in bus information. Admin can edit bus info here simply by
searching the bus first.

n. Delete Bus

Figure 6.3.3– User Manual of Delete Bus

This page is for deleting bus information. Admin can delete bus info here simply by
searching the bus first.

69
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 o. Add Driver

Figure 6.3.4– User Manual of Add Driver

On this page you have to give some basic info of the driver to be added. This is the basic
page to enter driver into your record.

p. Edit Driver

Figure 6.3.5– User Manual of Edit Driver

This page is for editing in driver information. Admin can edit driver info here simply by
searching the driver first.

70
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 q. Delete Driver

Figure 6.3.6– User Manual of Delete Driver

This page is for deleting driver information. Admin can delete driver info here simply by
searching the driver first.

r. History

Figure 6.3.7– User Manual of History

71
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
Admin can see the history of all the requests done by users.

s. Approval Requests

Figure 6.3.8– User Manual of Approval Requests

Admin can see and then accept/reject the approval requests of the new users.

t. Logout

Figure 6.3.9– User Manual of Logout

Admin can logout of the admin panel simply by clicking yes.

72
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 REFERENCES

73
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.
 REFERENCES

[1] https://www.liveviewgps.com/bus+tracking.htmlData accessed: [12th June, 2017]

[2] http://www.applane.com/track/Data accessed: [12th June, 2017]

[3] http://www.opengpstracker.org/build.htmlData accessed: [17th June, 2017]

[4] http://www.etratech.com/portfolio/gps-tracking-circuit-board-assembly/Data

accessed: [25th June, 2017]

[5] http://electronicsforu.com/electronics-projects/build-gps-trackerData accessed:

[29th June, 2017]

[6] https://www.componentsource.com/product/visual-webguiData accessed: [7th

July, 2017]

[7] https://www.w3schools.com/sql/sql_view.aspData accessed: [15th July, 2017]

[8] https://docs.microsoft.com/en-us/sql/t-sql/statements/create-view-transact-sqlData

accessed: [17th July, 2017]

[9] https://www.smartdraw.com/circuit-diagram/circuit-diagram-maker.htmData

accessed: [1st August, 2017]

[10] https://www.pinterest.com/explore/circuit-diagram/?lp=trueData accessed: [5th

August, 2017]

74
© Project Management Office Revised Version 2.4.14
Faculty of Computing& Information Technology, University of Gujrat.