Online Cab Booking (Documentation)
Online Cab Booking (Documentation)
1|Page
Table of Contents
CHAPTER 1: FINAL PROJECT PROPOSAL...........................................................................................5
1.1 INTRODUCTION:..........................................................................................................................6
1.2. Project Title:...............................................................................................................................6
1.3.Project Overview:........................................................................................................................6
1.3.Problem Statement.....................................................................................................................8
1.4. Project Goal:...............................................................................................................................8
1.5. Objectives:..................................................................................................................................8
1.6. Functional Requirements:...........................................................................................................9
1.6.1 ManageClient:......................................................................................................................9
1.6.2. Manage Fare:.......................................................................................................................9
1.6.3. Manage Employees:..........................................................................................................10
1.6.4.Manage Reports:................................................................................................................10
1.6.5. Manage Vehicles:..............................................................................................................10
1.6.6. Manage Booking or Reservation........................................................................................11
1.6.7. Manage Users:...................................................................................................................11
1.7Non Functional Requirement:.....................................................................................................11
1.7.1. Usability:............................................................................................................................11
1.7.2. Security:.............................................................................................................................12
1.7.3. Performance:.....................................................................................................................12
1.7.4. Availability:........................................................................................................................12
1.7.5. Error handling:...................................................................................................................12
1.7.6. Ease of use:........................................................................................................................12
1.8.Division of work:........................................................................................................................12
1.9.Gantt chart:...............................................................................................................................13
1.10. Software and Hardware Requirements...................................................................................14
System Interfaces.......................................................................................................................14
Hardware Interfaces:.................................................................................................................14
Hardware Interfaces:.................................................................................................................14
Software Interface:....................................................................................................................14
Third Party Software Interfaces:..............................................................................................15
Communication Protocol...........................................................................................................15
1.11. Tools / Methodology:.............................................................................................................15
2|Page
CHAPTER 2: FIRST DELIVERABLE.....................................................................................................16
2.1. INTRODUCTION:.......................................................................................................................17
2.2. Project/Product Feasibility Report:...........................................................................................17
2.2.1Technical Feasibility:...........................................................................................................17
2.2.2Operational Feasibility:.......................................................................................................17
2.2.3 Economic Feasibility:..........................................................................................................18
2.2.4 Schedule Feasibility:...........................................................................................................18
2.2.5 Information Feasibility:.......................................................................................................18
2.2.6 Motivational Feasibility:.....................................................................................................19
2.2.7 Legal & Ethical Feasibility:..................................................................................................19
CHAPTER 3: SECOND DELIVERABLE FOR OBJECT ORIENTED APPROACH.......................................20
3.1 Scope:........................................................................................................................................21
3.2Entities and Attributes:...............................................................................................................21
3.3 Capture "shall" Statements:......................................................................................................21
3.4 Allocate Requirements:.............................................................................................................22
3.5Priorities Requirements:.............................................................................................................23
3.6 Use case diagrams:....................................................................................................................24
3.6.1 User use case diagram:.......................................................................................................24
3.6.2 Admin Use case diagram:...................................................................................................25
3.6.3 Employee use case diagram:..............................................................................................26
3.6.4 Use case diagram:...............................................................................................................27
3.7.Use case:...................................................................................................................................28
CHAPTER 4:THIRD DELIVERABLE FOR OBJECTORIENTED APPROACH............................................34
4.1.User sequence diagram:............................................................................................................35
4.2.Employee sequence diagram:....................................................................................................36
4.3Admin sequence diagram:..........................................................................................................37
4.4.Activity diagram for Employee:.................................................................................................38
4.5.Activity diagram for employee:.................................................................................................39
4.6.Class Diagram :..........................................................................................................................39
CHAPTER 5:DELIEVERABLE (SOFTWARE TESTING).........................................................................40
5.1 Introduction:..............................................................................................................................41
5.2 Test Plane:.................................................................................................................................41
5.3 Test Case:..................................................................................................................................41
5.3.1 Login:..................................................................................................................................41
5.3.2 Cab booking:.......................................................................................................................42
3|Page
5.3.3 Manage profile:..................................................................................................................42
5.3.4 Manage categories:............................................................................................................42
5.3.5 View customer record:.......................................................................................................43
5.3.6 View history:.......................................................................................................................43
4|Page
CHAPTER 1:
5|Page
1.1 INTRODUCTION:
The Online Cab Booking System is all about providing the facilities of
travelling one place to another place. Online Cab Booking System resolves
the problem of clients and provides the vehicles at any place or any time.
This web based system is an open source system and will be user friendly,
and must be support to the technical feasibility. This project will be easy
to use for the users.
The cab service includes all categories of cars from luxury to budget. Further,
this project’s utmost priority is quality. To achieve this, vehicles are well
maintained and tested for delivering optimum and uninterrupted
performance. Team of professionals in the travel business enables this
system to design trips that suits to all budgets and preferences of the
travelers. In addition, workforce including drivers and administrative staff
are well trained to discharge their duties with a lot of efficiency.
6|Page
Title: ONLINE CAB BOOKING
Project Manager: Mam Amna Ikram
Task Members:
Project Goal: Our aim of online cab booking is that it will help you to get taxi at your
own door. It will provide quick service at your own place at any time. It aims to provide
relief to people tracing this issue by providing easy to book cheap and pleasant for
everyone.
Objectives:
# Objective of the project is to develop online cab booking system
1 Manage client
2 Manage employee
3 Manage fare
4 Manage vehicles
5 Manage booking and reservation
7|Page
1.3. Problem Statement
In the present system, organizations handling cab / taxi services employs
personnel for the allocating and proper functioning and movement of cabs.
The personnel appointed needs to look after the assigning and movement in
papers, which is a tedious task if any update or changes need to be done.
The old manual system was suffering from a series of drawbacks. Since
whole of the system was to be maintained with hands the process of
keeping, maintaining and retrieving the information was very tedious and
lengthy. The records were never used to be in a systematic order. There used
to be lots of difficulties in associating any particular transaction with a
particular context. If any information was to be found it was required to go
through the different registers, documents there would never exist anything
like report generation. There would always be unnecessary consumption of
time while entering records and retrieving records. One more problem was
that it was very difficult to find errors while entering the records. Once the
records were entered it was very difficult to update these records.
The main goal of the system is to automate the process carried out in the
organization with improved performance and realize the vision of online
booking.
1.5. Objectives:
The aim of the proposed system is to address the limitations of the current
system. The requirements for the system have been gathered from the
defects recorded in the past and also based on the feedback from users of
previous metrics tools. Following are the objectives of the proposed system:
Manage Client
Manage Fare
Manage Employees
8|Page
Manage Reports
Manage Vehicles
Manage Booking or Reservation
Manage Users
9|Page
1.6.3. Manage Employees:
Employee name, employee father name, employee cnic, employee user
name, employee password, employee address. The system should allow
employees to register through authentic data like name, mobile, username
and password. The system should allow to the employees to login system
using their username and password. Employees have access or authority to
register or manage record of new users. The account of employee will be
registered by the admin of system. The system shall allow to the employee
or admin to change the record of account like change username and
password. Any employee has option to delete account or logout from the
system. The system must store account information about employees of
entire system.
10 | P a g e
must store the record of online reserved vehicle and their routine. Mainly
system stores the record of vehicle into database and display to the
authorized users online as per their access restriction.
1.6.6. Manage Booking or Reservation
As Cab Booking System get fare from their clients it’s very important to
manage record of fare and store it on database as centralize. The Online Cab
Booking System will ensure to calculation of fare on lowest and reliable
budget rate with accuracy. Any user can place an order or reservation on
system site where he/she provide valid data like valid name, father name,
address, contact number and total number of days to reserve a vehicle into
reservation form.
1.6.7. Manage Users:
As we know every system has their users that interact with the system. In
Online Cab Booking System user must register their account through their
valid name, contact number, username, password and their type. Online Cab
Booking Management system will store the record of users display online,
any user can be login within system through their valid username and
password. When a user login within system, the system will redirect to the
user on their accessed or authorized
11 | P a g e
1.7.2. Security:
The system provides username and password to prevent the system from
unauthorized access.
The staffs’ password must be greater than eight characters. The subsystem
should provide a high level of security and integrity of the data held by the
system, only authorized personnel of the company can gain access to the
company’s secured page on the system; and only users with valid password
and username can login to view user’s page.
1.7.3. Performance:
The system response time for every instruction conducted by the user must
not exceed more than a minimum of 10 seconds. The system should have
high performance rate when executing user’s input and should be able to
provide response within a short time span usually
50 second for highly complicated task and 20 to 25 seconds for less
complicated task.
1.7.4. Availability:
The system should always be available for access at 24 hours, 7 days a week.
Also in the occurrence of any major system malfunctioning, the system
should be available in 1 to 2 working days, so that business process is not
severely affected.
1.7.5. Error handling:
Error should be considerably minimized and an appropriate error message
that guides the user to recover from an error should be provided. Validation
of user’s input is highly essential.
Also the standard time taken to recover from an error should be 15 to 20
seconds.
1.7.6. Ease of use:
Considered the level of knowledge possessed by the users of this system, a
simple but quality user interface should be developed to make it easy to
understand and required less training.
Division of work
12 | P a g e
1.9. Gantt chart:
Based on the Work Breakdown Structure (WBS), a timeline or Gantt chart
showing the allocation of time to the project phases or iterations should be
developed. This Gantt chart would identify major milestones with their
achievement criteria. It must contain duration estimation of all the necessary
activities to be carried out during the project development along with the
human resources responsible for the respective tasks. Activity dependencies
are also required to be mentioned in it.
13 | P a g e
1.10. Software and Hardware Requirements
System Interfaces
Client on Internet:
◦ Web Browser, Operating System (any)
Client on Intranet:
◦ Client Software, Web Browser, Operating System (any)
Web Server:
◦ Apache, Operating System (any)
Data Base Server:
◦ MySQL, Operating System (any)
Development End:
Hardware Interfaces:
Communication Interface
Client on Internet will be using HTTP/HTTPS Protocol.
Client on intranet will be using TCP/IP protocol.
Hardware Interfaces:
Server side hardware
Hardware recommended by all the software needed.
Communication hardware to serve client requests
Client side hardware
Hardware recommended by respective client’s operating system and
web browser.
Communication hardware to communicate the server.
Software Interface:
Server side software
Web server software, Apache
Server side scripting tools: PHP
Database tools: My SQL
Compatible operating system: Linux, Windows
Client side software
Web browser supporting JavaScript, refer Browser Compatibility
14 | P a g e
Third Party Software Interfaces:
None
Communication Protocol
Following protocols are required to be permitted on the server side
HTTP incoming request
HTTPS incoming request if secure gateway is implemented
Following protocols are required to be permitted on the client side
HTTP outgoing request
HTTPS outgoing request if secure gateway is implemented
15 | P a g e
CHAPTER 2:
FIRST DELIVERABLE
16 | P a g e
2.1. INTRODUCTION:
The Online Cab Booking System is all about providing the facilities of travelling one place
to another place. Online Cab Booking System resolves the problem of clients and
provides the vehicles at any place or any time. This web based system is an open source
system and will be user friendly, and must be support to the technical feasibility. This
project will be easy to use for the users.
Technical Feasibility
Operational Feasibility
Economic Feasibility
Schedule Feasibility
Specification Feasibility
Information Feasibility
Motivational Feasibility
Legal and Ethical Feasibility
2.2.1Technical Feasibility:
The tools for Online Cab Booking System will be used totally free and open source. All
the tools or application purchased easily from the market within minimum cost. We
thankful to the Microsoft team that offer full free and easy available tools like Microsoft
Word, Microsoft Excel and Power Point. In Online Cab Booking System all the front end
development HTML / HTML5, CSS / CSS3, JavaScript and Bootstrap tools will be open
source that are easily available. In this system we need a server for the back end
development process APACHE server My SQL lite these features provided by XAMPP or
WAMPP control panel
2.2.2Operational Feasibility:
The Online Cab Booking System must provide result to the users with quickly and
correctly. All the appliances within system will be used update to date, So that the
system ensures quality for their users. When a user registers their account he/she can
place online reservation on system site on front end, otherwise user can place query,
complaint and feedback, and all the back end activities will be handle by the site admin.
Admin of this system can view / add / delete and update any record of from the back
end.
Some operation will be performed in system are as follows
17 | P a g e
Manage Client
Manage Employee
Manage Vehicles
Manage Booking or Reservation
Manage user
User (Name, Father Name, CNIC, Mobile no, user id, Address)
Cab (Model/Type, Name, Route, Driver, No of seats)
Employee (Name, Email, Address, Contact no)
Admin (Name, Email, Contact information)
18 | P a g e
2.2.6 Motivational Feasibility:
The online cab booking system must have the ability to motivate its users. It also
describes the concept of motivation how a user can interact with the site. The online cab
booking system provides the services of online vehicle.
When the system will be completed, the system will be connected to work in a secure
environment, in addition to working in an integrated manner with the users or clients
confidentially and securely. In this modern world, people don’t want to place orders
physically, so using this system site an amazing way to travel from one place to another.
The user interface of the site is suitable for all users and their client because the system
provides user-friendly environment.
19 | P a g e
CHAPTER 3:
20 | P a g e
3.1 Scope:
The online cab booking system has a great interaction with users due to this site we can
finish manual paper and pencil work. This system is designed for all operating system
and every user can use it at any browser or any platform without any problem. every
user can get any service at anywhere on their recommended time. our management
must verify record of arrival users and confirm reservation for the vehicle.
21 | P a g e
3.0 Admin shall manage suggestion
2.0 Employee shall login to the website as employee UC_ Employee_ Login
22 | P a g e
3.5Priorities Requirements:
HIGHEST uc_11
Admin shall manage UC_ Employee_
3.0
employee profile profile
HIGHEST uc_12
Admin shall manage user UC_ User_
3.0
information information
uc_15
3.0 Admin shall manage reports UC_ reports
23 | P a g e
3.6 Use case diagrams:
User
Admin
Employee
3.6.1 User use case diagram:
Description:
Actor: USER
In cab booking system user login, register himself, manage profile, place order and pay
payment
24 | P a g e
3.6.2 Admin Use case diagram:
Description
Actor: Admin
In cab booking system admin login, manage employee profile, manage information, manage
feedback, manage suggestion, and manage reports
25 | P a g e
3.6.3 Employee use case diagram:
Description:
Actor: Employee
In online cab booking system employee can login, can manage vehicles, manage booking
and manage payment
26 | P a g e
3.6.4 Use case diagram:
Description:
In which diagram actors will can be login with in a system. In online cab booking system
employee can login, can manage vehicles, manage booking and manage payment. In cab
booking system user login, register himself, manage profile, place order and pay payment. In
cab booking system admin login, manage employee profile, manage information, manage
feedback, manage suggestion, and manage reports
27 | P a g e
3.7. Use case:
Use Case ID US-01
Use Case Name User Registration
Actor User
Description User shall register within system
Pre-Condition User provide data for registration
Primary Scenario User Action System Response
1. User provide their 1. System display registration
details for registration form and then the System
within system check user details
IF Details Valid
System register
account and redirect at
user dashboard
IF Not Valid
Display Error Message
Secondary Scenario If user provide invalid details for Registration Account
Expectations User provide invalid data during registration of account
Post Condition User must get the required information from the system
IF Not Valid
Display Error Message
Secondary Scenario If user provide invalid username and password for login
Expectations User provide invalid data during place order
Post Condition User must get the required information from the system
28 | P a g e
details for update then user put valid record
profile for update profile details
IF Details Valid
System will update
profile
IF Not Valid
Display Error Message
Secondary Scenario If user provide invalid details during Manage Profile
Expectations User provide invalid data during registration of account
Post Condition User must get the required information from the system
IF Details Valid
System will accept
order from the user
and redirect at valid
page
IF Not Valid
Display Error Message
Secondary Scenario If user provide invalid details during the place order
Expectations User provide invalid data during the place order
Post Condition User must get the required information from the system
IF Order Confirm
System will generate
auto paid payment slip
for user and user will
receive a notification
at email
29 | P a g e
IF Not Confirm
User will receive a
notification at email
why order not confirm
Secondary Scenario If authorized person can’t confirm order
Expectations If vehicle were not available and user have placed order
Post Condition System will generate a notification at email for information
IF Not Valid
Display Error Message
30 | P a g e
Use Case ID US-8
Use Case Name Employee Booking
Actor Employee
Description Manage booking
Pre-Condition
Primary Scenario User Action System Response
IF Not Valid
Display Error Message
Secondary Scenario If admin provide wrong email and password for login
Expectations admin provide invalid data for login
Post Condition Admin must get the required information from the system
31 | P a g e
Pre-Condition Open the dashboard and check details
Primary Scenario User Action System Response
1. Go the admin page check 1 system check the credential
the credential
2. If system response valid 2.if not provide valid credential than
credential then redirect to generate an error message
the dashboard
Secondary Scenario With valid input update the changes
Expectations If employee work in the organization and admin remove detail
Post Condition System will generate a notification for confirm deletion
32 | P a g e
Description Admin shall manage the reports
Pre-Condition
Primary Scenario User Action System Response
33 | P a g e
CHAPTER 4:
34 | P a g e
4.1. User sequence diagram:
35 | P a g e
4.3Admin sequence diagram:
36 | P a g e
4.4. Activity diagram for Employee:
37 | P a g e
4.5. Activity diagram for employee:
CHAPTER 5:
38 | P a g e
5.1 Introduction:
The designing phase is completed in previous chapters now here software testing is done.
Application name is “Online Cab booking system” Basically my application make user able to
book cab for ride. The Online Cab Booking System is all about providing the facilities of
travelling one place to another place. Online Cab Booking System resolves the problem of
clients and provides the vehicles at any place or any time.
39 | P a g e
Purpose To make sure that the system be developed
successfully
5.3.1 Login:
40 | P a g e
2. Provide valid information such as name phone number
address
3. Choose cab type
4. Book ride
5. Confirm booking can generate a notification to the user
Expected result Cab book successfully
Result Now user successfully book cab
41 | P a g e
Requirement Must have the customer record
Pre –condition Must store the history of customer record
Step 1. Open customer file
2. View the customer record
3. View the cab booking of the customer
4. View the total booking of cab
Expected result View customer record successfully
Result Now Successfully view the customer record
Chapter 6:
43 | P a g e
Our services section:
Our vehicles:
44 | P a g e
How system work:
Footer:
45 | P a g e
Vehicle detail:
Contact us section:
46 | P a g e
Admin login page:
Admin dashboard:
47 | P a g e
Admin booking corner:
48 | P a g e
Admin employee register corner:
49 | P a g e
Admin account detail:
50 | P a g e
User login page:
51 | P a g e
User booking record confirmation detail:
User testimonials:
52 | P a g e
Online cab booking system database:
Admin table:
Booking table :
Company table:
53 | P a g e
Contact us table:
Employee table:
Register:
54 | P a g e
Testimoials :
Vehicles table:
55 | P a g e