SL

no.
GANDHI INSTITUTE FOR
Group member Roll no. Regd no.

01
02 TECHNOLOGY
Soumya Ranjan Sahoo
Rituraj Lenka
59
45
2221298017
2101298145
03 Kabita Priyadarshini Nayak 27 2101298100
04 Rohit Kumar Patra 46 2101298146

SOFTWARE REQUIREMENT SPECIFICATION

TOPIC

TICKET BOOKING SYSTEM

- Purpose

- Scope

- Definitions, Acronyms, and Abbreviations

- References

- Overview

2. Overall Description

- Product Perspective

- Product Functions

- User Characteristics

- Operating Environment

- Design and Implementation Constraints

- Assumptions and Dependencies

3. Specific Requirements

- External Interface Requirements

- User Interfaces

- Hardware Interfaces

- Software Interfaces

- Communication Interfaces

- Functional Requirements

- User Registration and Authentication

- Event Browsing and Ticket Selection

- Secure Payment Processing

- Booking Confirmation and Ticket Generation

- Booking Cancellation

- User Profile Management

- Administrator Functionalities

- Non-functional Requirements

- Performance Requirements

- Security Requirements

- Reliability Requirements

- Availability Requirements

- Maintainability Requirements

- Portability Requirements
1. Introduction

1.1 Purpose

The purpose of this document is to outline the requirements for the development of a Ticket Booking System.
This system aims to provide users with a platform to browse, select, and book tickets for various events such as
movies, concerts, sports events, etc.

1.2 Scope

The Ticket Booking System will allow users to register, browse available events, select tickets, make payments,
receive booking confirmations, and manage their bookings. It will provide administrators with tools to manage
events, bookings, and user accounts.

1.3 Definitions, Acronyms, and Abbreviations

- SRS: Software Requirements Specification

- UI: User Interface

- API: Application Programming Interface

- DBMS: Database Management System

1.4 References

List any documents or resources referred to during the creation of this SRS.

1.5 Overview

This document provides an overview of the requirements for the Ticket Booking System, including the overall
description, specific requirements related to external interfaces, functional requirements, and non-functional
requirements.

2. Overall Description

2.1 Product Perspective

The Ticket Booking System will be a standalone web application accessible via web browsers. It will interact
with external payment gateways for payment processing and may integrate with external APIs for event data.

2.2 Product Functions

The system will provide the following functions:

- User registration and authentication

- Event browsing and ticket selection

- Secure payment processing

- Booking confirmation and ticket generation

- Booking cancellation

- User profile management

- Administrator functionalities for managing events, bookings, and user accounts

2.3 User Characteristics

The system will cater to two main types of users:

1. Customers: Users who browse and book tickets for events.

2. Administrators: Users responsible for managing events, bookings, and user accounts.
2.4 Operating Environment

The system will be accessible via web browsers (Chrome, Firefox, Safari, etc.) and will support desktop and
mobile devices.

2.5 Design and Implementation Constraints

- The system must handle concurrent user sessions efficiently.

- Data security measures must be implemented to protect user information and payment details.

- Compliance with relevant regulations and standards related to online payment processing and data
protection.

2.6 Assumptions and Dependencies

- Assumption: Users have access to stable internet connections to browse and book tickets.

- Dependency: Integration with third-party payment gateways for payment processing.

3. Specific Requirements

3.1 External Interface Requirements

3.1.1 User Interfaces

The system will have the following user interfaces:

- Registration/Login Page

- Event Listing Page

- Seat Selection Page (if applicable)

- Payment Page

- Booking Confirmation Page

- User Profile Page

3.1.2 Hardware Interfaces

The system will be accessible via devices with web browsing capabilities, including desktop computers, laptops,
tablets, and smartphones.

3.1.3 Software Interfaces

The system may integrate with external APIs to fetch event data and with payment gateways for payment
processing.

3.1.4 Communication Interfaces

The system will communicate with users via web-based interfaces and may send email notifications for booking
confirmations and updates.

3.2 Functional Requirements

1. User Registration and Authentication

- Users can create accounts with unique usernames and passwords.

- Users can log in securely using their credentials.

2. Event Browsing and Ticket Selection

- Users can browse available events sorted by categories, dates, or locations.

- Users can view event details including date, time, venue, and ticket availability.

- Users can select desired tickets and add them to their cart.
3. Secure Payment Processing

- Users can securely enter payment details and complete transactions.

- Integration with third-party payment gateways for processing credit/debit card payments.

4. Booking Confirmation and Ticket Generation

- Users receive confirmation emails with booking details and e-tickets.

5. Booking Cancellation

- Users can cancel bookings within a specified time frame and receive refunds as per cancellation policy.

6. User Profile Management

- Users can view and edit their profile information.

- Users can view their booking history and track current bookings.

7. Administrator Functionalities

- Administrators can add, edit, and delete events.

- Administrators can view and manage bookings.

- Administrators can manage user accounts and access control.

3.3 Non-functional Requirements

3.3.1 Performance Requirements

- The system should load event listings and perform transactions swiftly to provide a seamless user experience.

- The system should be able to handle multiple concurrent users without performance degradation.

3.3.2 Security Requirements

- User data and payment information should be encrypted and stored securely.

- The system should implement measures to prevent unauthorized access and protect against attacks such as
SQL injection and cross-site scripting (XSS).

3.3.3 Reliability Requirements

- The system should be available and reliable 24/7, with minimal downtime for maintenance.

3.3.4 Availability Requirements

- The system should have a high level of availability, with uptime exceeding 99%.

3.3.5 Maintainability Requirements

- The system should be designed with modularity and scalability in mind to facilitate future updates and
enhancements.

3.3.6 Portability Requirements

- The system should be compatible with major web browsers and accessible across different devices and
platforms.