Software Requirements

Specification
For

Online Bus Ticket Booking

System

Prepared by:

Group Name: RRS

Savalapurapu Roshan 22CS10068 [email protected]

Ramesh Rathod 22CS10047 nenavathrameshrathod28
@gmail.com
Saptarshi Sarkar 22CS30047 [email protected]
 Software Requirements Specification for Online Bus Ticket Booking System

Contents

Contents
Version 1.0 .......................................................................................................................................................... 1
1. INTRODUCTION ................................................. Error! Bookmark not defined.
1.1 Document Purpose........................................................................................ 1
1.2 Product Scope .............................................................................................. 1
1.3 Intended Audience and Document Overview ...................................................... 1
1.4 Definitions, Acronyms and Abbreviations ........................................................... 2
1.5 Document Conventions .................................................................................. 2
1.6 References and Acknowledgments ................................................................... 2
2 OverallDescription ........................................................................................... 3
2.1 Product Perspective ...................................................................................... 3
2.2 Product Functionality ..................................................................................... 3
 Registration: .......................................................................................... 3
 Sit Reservation: ...................................................................................... 3
 Report Generation: ................................................................................. 3
2.3 Users and Characteristics ............................................................................... 3
 Administrators: ......................................................................................... 3
 Passenger ................................................................................................ 3
2.4 Operating Environment.................................................................................. 4
2.5 Design and Implementation Constraints ........................................................... 4
3 SpecificRequirements .................................................................................... 5
3.1 Functional Requirements ................................................................................ 6
 Registration: ............................................................................................... 6
 Reserve Ticket: ............................................................................................ 6
 Maintain History ........................................................................................... 6
 Report Generation ....................................................................................... 6
 Database: ................................................................................................... 6
 Notifications:………………………………………………………………………………………………………………….6
3.2 Behaviour Requirements ................................................................................ 7
 Use Case View.......................................................................................... 7
4 Other Non-functionalRequirements ................................................................. 8
4.1 Performance Requirements ............................................................................ 8
4.2 Safety and Security Requirements ................................................................... 8
 Software Requirements Specification for Online Bus Ticket Booking System
4.3 Software Quality Attributes ............................................................................ 8
 Software Requirements Specification for Online Bus Ticket Booking System Page 1

1. INTRODUCTION
The introduction of the Software Requirements Specification (SRS) provides an overview
of the entire SRS with purpose, scope, definitions, acronyms, abbreviations, references and
overview of the SRS. This is a SRS document for Online Bus Ticket Booking System (OBTBS).
The objective of Bus Reservation System is to manage buses, their routes, fare and passenger
and also providethe comfort to both organization and Passenger.

1.1 Document Purpose

The purpose of this Software Requirements Specification (SRS) document is to provide a

comprehensive overview of the Bus Reservation System. This document outlines the functional
and non-functional requirements, user interfaces, and system features necessary to develop an
efficient and user-friendly Bus Reservation System.
The main objectives of the Bus Reservation System are to facilitate efficient bus
management for operators, provide a convenient booking process for passengers, and enhance
the overall comfort and experience for both parties. By defining the requirements and features
of the Bus Reservation System in this SRS document, we aim to guide the development
process effectively, ensuring that the final system meets the needs and expectations of both
the bus operators and the passengers.

1.2 Product Scope

The Online Bus Ticket Booking System aims to manage buses, their routes, fares, and
passengers. The system will facilitate bus operators in managing their bus schedules, seat
availability, and booking details, while providing passengers with a convenient platform to
search for buses, book tickets, and manage their reservations. The system will ensure a
comfortable and efficient experience for both the organization and the passengers.The
intentions of the system are to reduce over-time pay and increase the number of passengers
that can be treated accurately. Requirements statements in this document are both
functional and non- functional.

1.3 Intended Audience and Document Overview

The intended audience includes all stakeholders in the potential system. These include,
but are not necessarily limited to, the following: Administrative Staff, patients and
developers.

The objective of this document therefore is to formally describe the system’s high
level requirements including functional requirements, non-functional requirements and
business rules and constraints. The detail structure of this document is organized as follows:

Section 2 of this document provides an overview of the business domain that the
proposed Online Bus Ticket Booking System (OBTBS) will support. These include a general
description of the product, user characteristics, general constraints, and any assumptions for
this system. This model demonstrates the development team's understanding of the business
domain andserves to maximize the team's ability to build a system that truly does support the
business.

Section 3 presents the detail requirements, which comprise the domain model.
 Software Requirements Specification for Online Bus Ticket Booking System Page 2

1.4 Definitions, Acronyms and Abbreviations

 OBTBS– Online Bus Ticket Booking System

 BN - Bus Number
 PIN - Passenger Identification Number
 Logon ID - a user identification number to enter the system
 Password - a word that enables one to gain admission into the system
 Web-based application - an application that runs on the Internet
 PHP - Hypertext Preprocessor
 HTML - Hypertext Markup Language
 CSS - Cascading Style Sheets
 MySQL - a query language to interrogate the system
 GUI - Graphical User Interface
 SRS - Software Requirements Specification

1.5 Document Conventions

In general, this document follows the IEEE formatting requirements. This document contains
Verdana template font size 11 throughout. We have used italics for comments. The document
text is single spaced and has 1” margins. The sectional heading uses Arial Heading 1 with
font size 18 and Subsection titles follow the Arial Heading 2 with font size 14.

1.6 References and Acknowledgments

1. IEEE SRS Template

2. SRS Online Shopping System

www.scribd.com/doc/60703226/Srs-.-Shopping-System
 Software Requirements Specification for Online Bus Ticket Booking System Page 3
2 OverallDescription
2.1 Product Perspective

The Online Bus Ticket Booking System is a self-contained system designed to manage various
activities related to bus travels, including passenger information, bus schedules, and booking
management.

2.2 Product Functionality

The system functions and funtions can be described as follows:

 Registration:

Login/Registration:
 The passenger enters their Login ID and Password.
 If the passenger is already registered, they can proceed to login.
 If the passenger is not registered, they can register by providing their information.
 A new Passenger Identification Number (PIN) is assigned to the passenger.
 The passenger's information, such as date of birth, address, and telephone
number, is entered into the computer system.

 Seat Reservation:

 Functional Flow:

 Login: The passenger logs in with their Login ID and Password.

 Journey Details: The system prompts the passenger to enter the source and destination of
their journey, route, date and time of journey, and type of bus (Normal or AC).

 Availability Check: The system checks the availability of seats in the database for the
proposed time.

 Reservation:

If the seat is available, the reservation is confirmed by processing the e-payment.

The seat number, bus number, date, and time of the bus are sent to the passenger along
with a blueprint of the ticket.

If the seat or bus is not available, the system provides the passenger with alternative
options.

 Report Generation:

The system generates reports on the following information: List of detailed

information regarding the buses run by travel company and passengers.

2.3 Users and Characteristics

The system will be used by the travel agency. The main users will be the administrators and
passengers. Given the condition that not all users are computer-literate, the system is
designed to be user-friendly and utilizes a Graphical User Interface (GUI).
Software Requirements Specification for Online Bus Ticket Booking System Page 4
 Administrators:
o Education and Training: All administrators have post-
secondary education relating to general business
administration practices and have undergone basic
computer training.
o Responsibilities: Administrators are responsible for
scheduling, updating day/night employee shifts, and
managing the overall operation of the bus reservation
system.
 Passenger :

o Computer Literacy: Passengers need to have basic knowledge about

computers and the Internet for seat booking.
o Booking Process: Passengers can book seats, view bus details, and
manage their reservations through the user-friendly interface of the
OBTBS.

2.4 Operating Environment

 Web-based Application: The system will be accessible via web browsers.

 Operating Systems :Compatible with Windows, macOS, and Linux.

2.5 Design and Implementation Constraints

 All bus and passenger records must be securely protected throughout all processes to ensure
data confidentiality and integrity.
 Changes or additions to payment methods can directly affect the system's functionality and
should be implemented iwth flexibility to adapt to new payment methods seamlessly.
 The system must be designed with a user-friendly interface to accommodate users
with varying levels of computer literacy, ensuring ease of use for both administrators
and passengers.
 Since the OBTBS can be accessed via the internet, the system should be designed to
handle potential network issues, ensure data encryption for secure online
transactions, and provide a responsive design for various devices.

3 System Features and Requirements

3.1 Functional Requirements

 Registration:
 Add passenger: The OBTBS shall allow new passengers to register
themselves in the system by setting their own unique username and
password. 

 Reserve Ticket:

 Sign In:
o Passenger: The passenger must first sign in to the system using their
chosen ID and password.
o Validation: The system must validate the provided ID and password before
granting access.
 Software Requirements Specification for Online Bus Ticket Booking System Page 5

 Check Availability: 
o Passenger: The passenger must be allowed to see all available options
for journey. And see if the seat is available or not.
 Reserve Ticket:
o Passenger: If a seat is available, the passenger should be able to book the seat
using their chosen ID. The seat should not be available for booking by other
passengers until it becomes free.

 Maintain History:

 Maintain Booking Info:

o Administrator: The administrator should be able to update the
booking info by storing the schedule id, starting location,
destination, name, number of tickets booked, Status of payment
and date.

 Update Seat Availability:
o Administrator: The administrator should be able to update the seat
availability list after the journey is completed or if a seat is canceled.

 . Report Generation :
 Schedule List Information: 
o The OBTBS shall generate reports on schedule list containing the
following information: Bus Number, from location, to location, departure
time, status, availability.
 Booking list Information:
o The OBTBS shall generate reports on Booking list containing the
following information: name, schedule id, from location, to location,
number of tickets booked by the person , Status of payment and date.
 Sit Availability: 
o The OBTBS shall generate reports on seat availability containing the following
information: bus number, number of occupied and number of seats
unoccupied.
 Database: 
 Passenger Information:
o Each passenger should have the following mandatory information stored:
Name, chosen ID and password.
 Bus Information:
o Each bus should have the following information stored: bus number, number
of seats, price and status.
 Update Schedule List Information:
o Administrator: The OBTBS shall allow the administrator to update any bus
information like from location and to location, change fare, and update seat
availability.

 Notifications: Users and bus operators should receive notifications for booking
confirmations, updates, etc.




 Software Requirements Specification for Online Bus Ticket Booking System Page 6
3.2 Behavior Requirements

 Use Case View

A use case defines a goal-oriented set of interactions between external actors and the system
under consideration. Since sometimes we will not be able to specify completely the behaviour
of the system by just State Diagrams, hence we use use-cases to complete it.

Passenger Administrator
 Software Requirements Specification for Online Bus Ticket Booking System Page 7

Use Case 1: Register Passenger

Actor: Passenger
Goal: To register as a new user in the OBTBS.
Main Flow:
1. Passenger provides required personal information.
2. Passenger chooses a unique ID and password.
3. System validates the information.
4. System registers the passenger in the database.
Alternate Flows:
 A1: If the chosen ID is already in use, the system prompts the passenger to choose a different ID.
Use Case 2: Sign In
Actor: Passenger
Goal: To sign in to the OBTBS.
Main Flow:
1. Passenger enters the registered ID and password.
2. System validates the ID and password.
3. System grants access to the passenger.
Alternate Flows:
 A1: If the ID or password is incorrect, the system prompts the passenger to re-enter the credentials.
Use Case 3: Check Bus Availability
Actor: Passenger
Goal: To check the availability of buses.
Main Flow:
1. Passenger selects the source and destination locations.
2. System displays a list of available buses with their schedules.
Alternate Flows:
 A1: If no buses are available for the selected route, the system informs the passenger.
Use Case 4: Reserve Ticket
Actor: Passenger
Goal: To reserve a seat on a bus.
Main Flow:
1. Passenger selects a bus schedule.
2. System checks the availability of seats.
3. Passenger chooses the number of seats to reserve.
4. System confirms the reservation and updates the seat availability.
Alternate Flows:
 A1: If the selected bus schedule is full, the system prompts the passenger to choose a different schedule.
Use Case 5: Maintain Booking Info
Actor: Administrator
Goal: To maintain the booking information.
Main Flow:
1. Administrator accesses the booking records.
2. Administrator updates the booking status and other details as required.
Use Case 6: Update Seat Availability
Actor: Administrator
Goal: To update the seat availability after a journey or cancellation.
Main Flow:
1. Administrator accesses the bus schedule and seat availability.
2. Administrator updates the seat availability for the specific bus schedule.
Use Case 7: Generate Bus and Seat Reports
Actor: Administrator
Goal: To generate reports on buses and seat availability.
Main Flow:
1. Administrator selects the type of report to generate (Bus Information or Seat Availability).
2. System generates and displays the report.
Software Requirements Specification for Online Bus Ticket Booking System Page 8
 Software Requirements Specification for Online Bus Ticket Booking System Page 9

4 Other Non-functionalRequirements

4.1 Performance Requirements

 Response Time: The OBTBS should respond to user actions within 2 seconds
under normal load conditions.

 Capacity: The System must support 100 people at a time.

 User-interface : The user-interface screen shall respond within 5 seconds.
 Conformity: The systems must conform to the Microsoft Accessibility guidelines.
 Network Connection: The should br connrcted to internet 24 X 7. And the Server
must be on all time.

4.2 Safety and Security Requirements

 Logon ID : Any user who uses the system shall have a Logon ID and Password.
 Modification : Any modification (insert, delete, update) for the Database shall be
synchronized and done only by the administrator in the ward.

 Administrators' Rights: Administrators shall be able to view and modify all

information in OBTBS for any modification (insert, delete, update) for the
Database shall be synchronized and done only by the administrator.
.

4.3 Software Quality Attributes

 Technology Stack:
 Development Platform: The OBTBS is developed using PHP,HTML,CSS,JavaScript.
 Database: The system uses MySQL for data storage.

 Maintainability:

 Back Up : The system shall provide the capability to back-up the Data
 Errors: The system shall keep a log of all the errors

 Reliability:
 Availability :The system shall be available all the time

4.4 Business Rules
 User Roles and Permissions:
o Passenger: Can view bus schedules, book tickets, and manage personal information.
o Administrator: Can view and modify bus schedules, manage user accounts, and monitor
system performance.

 Booking Rules:
o A passenger can book a maximum of 5 seats per transaction.
o A booking can be canceled up to 24 hours before the departure time.
 Software Requirements Specification for Online Bus Ticket Booking System Page
 Payment Rules: 10
o Payment must be completed within 30 minutes of booking to secure the seat.
o Refunds will be processed within 7 working days for canceled bookings.

5. Other Requirements
 Database Requirements:
o The system shall use a relational database to store bus schedules, user information, and
booking details.
 Internationalization Requirements:
o The system shall support multiple languages and currencies to cater to international
users.
 Legal Requirements:
o The system shall comply with data protection and privacy laws to ensure the security of
user data.
 Reuse Objectives:
o The system components should be designed with reusability in mind to facilitate future
expansions and modifications.




















