Student Auditorium Management Software (SAMS)

Software Requirement Specification

Version <1.0>
 Table of Contents

1 Introduction
1.1. Purpose
1.2. Scope
1.3. Definitions, Acronyms and Abbreviation
1.3.1.Ticket Receipt
1.3.2.Balance Sheet
1.3.3.Employee ID
1.3.4.Transaction ID
1.4. References
1.5. Overview
2. Overall Description
2.1. Product Perspective
2.2. Product Function
2.2.1.Ticket Booking
2.2.2.Cancelling Ticket
2.2.3.Update Database
2.2.4.Query Management
2.2.5.Balance Sheet Generation
2.3. User Characteristics
2.3.1.Show Manager
2.3.2.Sales Person
2.3.3.Accounts Clerk
2.4. Constraints
2.5. Assumptions and Dependencies
3. Specific Requirements
3.1. External Interface Requirements
3.1.1.User Interface
3.1.2.Software Interface
3.1.3.Hardware Interface
3.2. Functional Requirements
3.2.1.Query of a Show
3.2.2.Ticket Transaction
3.2.3.Cancel Ticket
3.2.4.Viewing Balance Sheet
3.2.5.Setting Show Details
3.2.6.Updating Employees
3.3. Reliability and Availability
3.4. Security
4. Supporting Information
1.1 Purpose
This SRS describes the software functional and non-functional requirements for the Students'
Auditorium Management Software (SAMS). It explains the functional features of the software, along
with interface details, design constraints and related considerations. This software is designed to
efficiently manage the various shows conducted in a student auditorium. The SRS is intended for
spectators and managers of an auditorium. Unless otherwise stated, all requirements specified here
are high priority and committed in this software.

1.2 Scope

The Students' Auditorium Management Software consists of the following major functions:

• Maintaining and updating the information on various shows held at an auditorium.

• Booking and cancelling the tickets by spectators through a sales person.

• Hiring and firing an employee.

• Querying for seat availability.

• Displaying and printing the balance sheets of various shows for every year.

1.3 Definitions, Acronyms and Abbreviation

Clarify key terms and abbreviations used throughout the document, including Ticket Receipt,
Balance Sheet, Employee ID, and Transaction ID

1.3.1 Ticket Receipt

Refers to a document or record generated by the system upon successful booking or
purchase of tickets for a student-related event. It contains essential details such as ticket
number, event information, and transaction specifics, serving as proof of purchase.

1.3.2 Balance Sheet

A Balance Sheet in the context of the Student Management System is a financial
statement that provides a summary of the organization's financial position. It includes
assets, liabilities, and equity, offering insights into the financial health of the
institution related to student-related activities.

1.3.3 Employee ID
Employee ID is a unique identifier assigned to each staff member within the system. It
serves as a key reference for employee-related transactions, ensuring accurate
record-keeping and identification of individuals involved in various administrative
and managerial roles.

1.3.4 Transaction ID
A Transaction ID is a unique identifier assigned to each transaction within the system,
particularly relevant in the context of ticket bookings, cancellations, or any financial
 transactions. It helps track and reference specific transactions for auditing and
management purposes.

1.4 References
List relevant sources and documents that influenced the creation of the Student
Management System, aiding users in obtaining additional information.

1.5 Overview
Provide a brief summary of the Student Management System, highlighting its
significance and the core aspects it addresses in the academic environment.

2 Overall Description
2.1 Product Perspective
Detail how the Student Management System fits into the broader educational context,
emphasizing its relationship with existing systems and its role in enhancing overall
management.

2.2 Product Function

Enumerate primary functions, including Ticket Booking, Cancelling Ticket, Database
Updates, Query Management, and Balance Sheet Generation, to present a
comprehensive view of system capabilities.

2.3 User Characteristics

2.3.1 Show Manager
Show manager are key users responsible for planning and organizing student-related
events. They possess elevated privileges to set up and manage show details, allocate
seating arrangements, and oversee the overall execution of events. Show Managers
play a pivotal role in ensuring the success of student-oriented programs.

2.3.2 Sales Person

Sales person are users involved in ticket transactions and revenue generation. They
have access to functionalities related to ticket booking and cancellation. Sales
Persons contribute to the efficient and smooth operation of the system by facilitating
the ticketing process for attendees.

2.3.3 Account Clerk

Account clerk are users focused on financial aspects. They engage in Balance Sheet
Generation and other financial reporting tasks. Accounts Clerks play a vital role in
maintaining financial transparency, ensuring accuracy in financial records related to
student events, and supporting overall fiscal management.
3 Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interface
Describe the graphical and navigational aspects of the system's user interface,
ensuring a user-friendly experience.

3.1.2 Software Interface

Specify interactions with other software systems, ensuring seamless integration and
data exchange.

3.1.3 Hardware Interface

Detail hardware requirements to support the Student Management System, ensuring
compatibility with the designated infrastructure.

3.2 Functional Requirements

3.2.1 Query of a Show
Specify processes related to ticket booking, cancellation, and updating transaction
details.

3.2.2 Ticket Transaction

Specify processes related to ticket booking, cancellation, and updating transaction
details.

 Initiate Ticket Transaction

 Payment Processing
 Ticket Confirmation and Details
 Update Database

3.2.3 Cancel Ticket

The Cancel Ticket functionality allows users, including administrators, salespersons, or
attendees, to cancel previously booked tickets. Upon cancellation, the system initiates
a process to deduct seat fees and generates a detailed confirmation for the user.

 User Initiation :- Users trigger the cancellation process by accessing their

booking history or relevant interface.
 Deduction of Seat Fees :- Calculate and deduct applicable seat fees from the
original transaction amount.
 Database Update :- Update the system database to reflect the cancellation,
freeing up the reserved seats.
 Confirmation and Details :- Generate a detailed confirmation message,
including information about the cancelled ticket, deducted fees, and any
applicable refund processes.
3.2.4 Viewing Balance Sheet
Describe functionalities enabling users to access and analyze generated balance
sheets.

3.2.5 Setting Show Details

Outline procedures for administrators to input and manage details related to
scheduled shows.

3.2.6 Updating Employees

Define how the system manages the addition, modification, or removal of employee
information.

3.3 Reliability and Availability

Establish criteria for the system's reliability and availability, ensuring consistent
performance and minimal downtime.

3.4 Security
Outline security measures to safeguard sensitive data, ensuring the confidentiality and
integrity of information.

4 Supporting Information
Include any additional information supporting the Student Management System, such as
user guides, training materials, or maintenance documentation.