Bus Ticketing and Management System
Bus Ticketing and Management System
On
Submitted by:
Amna Ali
In
DECEMBER 2018
PAKISTAN
CERTIFICATE
Done by
AMNA ALI
ACKNOWLEDGEMENT
First of all I would like to thank our lecturer who taught us the basic of communication and technology
and helped us to learn about different types of technologies along with benefits. Lastly, I am very
glad that I have successfully able to complete our assignment on time. I appreciate all the helpers for
helping out along the way of this development. I thank all of them cordially for their helpful attitude.
TABLE OF CONTENTS
ABSTRACT
1. CHAPTER 1(INTRODUCTION)
1.1 PROJECTS AIMS AND OBJECTIVES.
1.2 BACKGROUND OF PROJECT.
1.3 OPERATION ENVIORNMENT.
ABSTRACT
Bus Ticketing and Management System is a project which aims in developing a computerized system to
maintain all the daily work of Bus Ticketing System .This project has many features which are generally
not available in normal Bus Ticketing and Management systems like facility of user login .It also has a
facility of admin login through which the admin can monitor the whole system. It has also a facility
where passengers after logging in their accounts can see list of reservations they had booked and its
reservation date. The librarian after logging into his account i.e. admin account can generate various
reports such as passenger report, reservation report, bus report.
Overall this project of ours is being developed to help the passengers as well as staff of buses to
maintain the system in the best way possible and also reduce the human efforts.
CHAPTER 1
INTRODUCTION
This chapter gives an overview about the aim, objectives, background and operation
environment of the system.
The project aims and objectives that will be achieved after completion of this project are
discussed in this subchapter. The aims and objectives are as follows:
Bus Ticketing and Management System is an application which refers to ticketing systems which are
generally small or medium in size. It is used by reservation offices to manage the bus system using a
computerized system where he/she can record various transactions like issue of tickets, return of tickets,
variety of bus routes, addition of different buses etc.
Tickets and passenger maintenance modules are also included in this system which would keep track of
the passengers using the system and also a detailed description about the variety of buses. With this
computerized system there will be no loss of ticket record or member record which generally happens
when a non-computerized system is used.
In addition, report module is also included in Bus Ticketing and Management System. If user’s position is
admin, the user is able to generate different kinds of reports like lists of reservations registered, list of
buses, issue and return tickets.
All these modules are able to help system user to manage the whole management system with
more convenience and in a more efficient way as compared to ticketing systems which are not
computerized.
CHAPTER 2
SYSTEM ANALYSIS
In this chapter, we will discuss and analyze about the developing process Bus Ticketing and
Management System including software requirement specification (SRS) and comparison between
existing and proposed system. The functional and non functional requirements are included in SRS part
to provide complete description and overview of system requirement before the developing process is
carried out. Besides that, existing vs. proposed provides a view of how the proposed system will be more
efficient than the existing one.
Bus Ticketing and Management System is a computerized system which helps user (Reservation office)
to manage the ticketing office daily activity in electronic format. It reduces the risk of paper work such as
file lost, file damaged and time consuming
It can help user to manage the transaction or record more effectively and timesaving.
File lost
When computerized system is not implemented file is always lost because of human
environment. Sometimes due to some human error there may be a loss of records.
File damaged when a computerized system is not there file is always lost due to some
accident like spilling of water by some member on file accidentally. Besides some
natural disaster like floods or fires may also damage the files.
Difficult to search record
When there is no computerized system there is always a difficulty in searching of
records if the records are large in number.
Space consuming
After the number of records becomes large the space for physical storage of file and
records also increases if no computerized system is implemented.
Cost consuming
As there is no computerized system to add each record paper will be needed which
will increase the cost for the management of library.
ii. Existing system does not have any facility of variety of buses for city to city.
iii. Existing system does not has any option of more than five cities.
iv. Existing system does not have any facility to generate passengers reports as
well ticket issue reports whereas proposed system provides admin with a tool
to generate reports
Existing system does not has any facility for ticket request and suggestions where as in proposed
system after logging in to their accounts passenger can request tickets as well as provide
suggestions to improve management system.
In simple terms, C++ is a sophisticated, efficient and a general-purpose programming language based on
C. It was developed by Bjarne Stroustrup in 1979.
Many of today’s operating systems, system drivers, browsers and games use C++ as their core language.
This makes C++ one of the most popular languages today.
Since it is an enhanced/extended version of C programming language, C and C++ are often denoted
together as C/C++.
It is bundled with, and uses, the MinGW or TDM-GCC 64bit port of the GCC as its compiler. Dev-C++
can also be used in combination with Cygwin or any other GCC-based compiler.
Dev-C++ is generally considered a Windows-only program, but there are attempts to create a Linux
version: header files and path delimiters are switchable between platforms.
CHAPTER 3
SYSTEM DESIGN
CHAPTER 5
SYSTEM TESTING
The aim of the system testing process was to determine all defects in our project .The program was
subjected to a set of test inputs and various observations were made and based on these observations it
will be decided whether the program behaves as expected or not. Our Project went through two levels
of testing
1. Unit testing.
2. Integration testing.
UNIT TESTING:
Unit testing is undertaken when a module has been created and successfully reviewed .In order to test a
single module we need to provide a complete environment i.e. besides the module we would require
The procedures belonging to other modules that the module under test calls
Non local data structures that module accesses
A procedure to call the functions of the module under test with appropriate
parameters
Unit testing was done on each and every module that is described under module description of chapter
4
Testing admin login form-This form is used for log in of administrator of the
system. In this we enter the username and password if both are correct
administration page will open otherwise if any of data is wrong it will get
redirected back to the login page and again ask for username and password
Passenger account addition- In this section the admin can verify passenger
details from passenger reservation history info and then only add passenger
details to main reservation database it contains add and delete buttons if user
click add button data will be added to passenger database and if he clicks delete
button the passenger data will be deleted
Ticket Addition- Admin can enter details of tickets and can add the details to the
main ticket table also he can view the tickets requests.
Test for passenger login Form-This form is used for log in of passenger. In this we
enter thepassenger, username and password if all these are correct passenger login page
will open otherwise if any of data is wrong it will get redirected back to the login page
and again ask for thepassenger, username and password.
Test for account creation- This form is used for new account creation when passenger
does not fill the form completely it asks again to fill the whole form when he fill the
form fully it gets redirected to page which show waiting for conformation message as
his data will be only added by administrator after verification.
INTEGRATION TESTING:
In this type of testing we test various integration of the project module by providing the input. The
primary objective is to test the module interfaces in order to ensure that no errors are occurring when one
module invokes the other module.
CHAPTER 6
CHAPTER 7
REFRENCES