This section of
the software requirement specification (SRS) provides a complete description of
the scope and overview of everything included in this SRS. This section of SRS also provides description
of the purpose of this document and list of abbreviations and definition is
The purpose of
this document is to provide detailed description of the requirement for the
“online bus ticket reservation system”. It will provide description of the
system functional and nonfunctional requirements of the system. It will also
explain system interface, constraints and interactions with other external
reservation system is aimed at reducing paper work and hence improving its
efficiency and speeding up of all processes. This system provides the facility
to reserve seats, cancellation of seats and to make online payment. It also
maintains returning of money after the cancellation of seat. It maintains all
data of user, bus details, reservation details and booking details. Thus, this
system saves the entire user’s long queue and hassle.
Cancellation of ticket
Update Bus Fare
Update Bus schedule
Login as Admin
Signup/login as user
Manually ticket Booking
Online Ticket booking
Check Passenger information
Update Route Details
Check Ticket Availability
Select Number of Tickets
Select Seat Number
Pay fare amount
Login over Email/number
Sample IN/OUT List
document follows MLA Format. Bold-faced text has been used to emphasize section
and sub-section headings.
In this document Times New Roman font has been used and font size is 18 for
heading, 14 for sub-headings and 12 for description.
Audience and Reading Suggestions
document is written for the software developers, domain expert, project
managers and for stack holders like user, clerk. The developers and project
managers need to become intimately familiar with the SRS.
This section gives
a detailed description of the interaction of the system with other systems. It
also gives description about the functionality of the system, interaction of
the stack holders with the system and constraints of the system.
The work is done
manually. Those who are interested in inquiring about the Bus Type, its Tickets
Price, available seats, facility of the bus etc. has walk to the Booking
office. This creates a huge Relief for the Customer of the Office on weekends
to save their time. A new system is helpful to both employees as well as the
customers. New system provides help to the customer as they can inquire about
the Bus model, its Ticket price, available Seats, facility of the bus, and they
don’t need to walk to the office.
This system will
consist of two parts, one mobile application and one web portal. The mobile
application will be used to find bus destination details and view information
about them while the web portal will be used for managing the information about
the bus schedule and the system.
User can use
mobile application as well as web portal to search bus, reserve seat, make
payment and cancellation of seat.
Since this is a
data-centric product it will need somewhere to store the data. For that, a
database will be used. Both the mobile application and web portal will
communicate with the database, however in slightly different ways. The mobile
application will only use the database to get data while the web portal will
also add and modify data. All the database communication will go over the
application has some restrictions about the resource allocation. To avoid
problems with overloading the operating system the application is only allowed
to use 40 megabytes of memory while running the application. The maximum amount
of hard drive space is also 37 megabytes.
2.2 Product Functions
basically provides a Bus information and regarding bus information.
our website any user views our system and search the bus and how many seats are
available in our buses.
can also register its own seats in bus this website.
person should be able to Login to the system through the first page of the
application Change the password after logging into the system.
be able to create a new login for the accessing the reservation facility.
the buses for two weeks (Only two weeks advance reservation is available).
reservation before two days can be done.
details about the credit card.
this system admin can maintain all the Bus information and maintain Bus
this system admin can maintain the registered users, manage schedule, and admin
can generate reports and manage the whole system.
web portal will provide functionality to manage the system and the bus schedule
will also provide information about the system, for example show when there is
a new update.
Classes and Characteristics
There are two type
of users that interact with the system, user and administrators. Each of these
two types of users has different use of the system so each of them has their
The User can use
mobile application as well as web portal to search a bus, reserve a seat,
make payment and
cancel their reservation. User can search a bus, category wise (Timing wise, destination
Admin use only web
portal to manage entire system, for example destination details, manage
payments, reserve and cancel reserved seat.
Platform (Android 4.0 or above)
Platform (iOS 7.0 or above)
10 mobile Platform
server software, Apache
scripting tools: PHP
tools: My SQL
A maximum of 10
thousand hits per day have been recorded.
2.5 Design and Implementation
The primary design constraint is the mobile platform. Since the
application is designated for mobile handset, limited screen size and
resolution will be a major consideration. Creating a user interface which is
both effective and easily navigable will pose a difficult challenge. Some of
the design and implementation constraints identified are listed below:
or employees do not have any rights to edit any data in the system.
pays the service fees by Card hire the vehicle.
Payment facility may be restricted if the Company not want this facility
for some reasons.
system is not support distributed database Facility.
is limited to HTTP/HTTPS Protocols.
2.6 User Documentation
Online documentation facility is available for the clients to
assess them for the easy use.
A specific document should be prepared for the maintenance of the
system and should say the system in easiest way.
2.7 Assumptions and Dependencies
Vehicles are already purchased and available for use.
Roles and responsibilities are already established.
Admin is assumed to have a computer with internet access.
Administrator is already created.
Credit card authorization services are assumed to be available.