Software Requirements Specification(SRS)

Topic: “Spicejet”
CSE320
(Software Engineering)

COMPUTER SCIENCE AND ENGINEERING

Submitted by:
Name: Davinder Singh
Registration number: 12324257
Roll No.: 30
Section: K23EA

Submitted to :
Jatinder Kaur

LOVELY PROFESSIONAL UNIVERSITY

 Table of Contents

1. Introduction

1.1 Purpose

1.2 Scope

1.3 Intended Audience and Reading Suggestions

1.4 Definitions, abbreviations

2. Overall Description

2.1 Product Perspective

2.2 Product Features

2.3 User Classes and Characteristics

2.4 Operating Environment

3. functional Requirement

4. External Interface Requirements

4.1 User Interfaces

4.2 Hardware Interfaces

4.3 Software Interfaces

5. Other Non-functional Requirements

5.1 Performance Requirements

5.2 Safety Requirements

5.3 Security Requirements

5.4 Software Quality Attributes

6. Other Requirements

7. Data Flow Diagrams (DFD)

7.1 Level 0
7.2 Level 1
 7.3 Level 2
8. Use Case Diagrams
9. Test cases

1.Introduction
1.1 Purpose

• This document describes the software requirements and specification for Software of a
SpiceJet airlines .
• The purpose of this document is to provide a comprehensive overview of the
requirements for developing a booking system for SpiceJet airlines. It outlines the
functionalities, constraints, and performance expectations of the system.

1.2 Scope

SpiceJet services provide better comforts to the passengers last few Years. SpiceJet is the
cheapest air travels in India.

• It gives better comforts in domestic flights as well as in international flights.

• It have online sites for booking the tickets, food and beverages.
• This site is useful in many ways to book the tickets and to cancel the tickets.
• This site provides special packs and bonus ticket booking for festival offers also. It
provides cheap and better services.

1.3 Intended Audience and Reading Suggestions

This document is intended for software developers, project managers, and stakeholders involved
in the development of the SpiceJet reservation system.

1.4 Definitions, abbreviations

• SpiceJet

A low-cost airline based in India.

• Booking System

A software platform that facilitates flight reservations and management.

 • GUI- Graphical User Interface Stockholder

The person who will participate in system

Ex. Passengers, Administrators etc…

• SRS: Software Requirements Specification

2 Overall Description

2.1 Product Perspective:

The product perspective outlines the software system's place within the greater network of
interconnected systems, procedures, and stakeholders.
• Integration with Current Systems:

SpiceJet's current flight scheduling, inventory management, and customer relationship

management systems should all work in together with the reservation system. This
integration guarantees that seat inventory can be managed, real-time flight data can be
accessed by the reservation system, and bookings can be synchronized across all
platforms.

• User Interface Consistency:

SpiceJet's branding and user interface design guidelines should be adhered to by the
reservation system. This guarantees a consistent customer experience on all platforms,
such as self-service kiosks, mobile apps, and websites.

• Scalability and Flexibility:

SpiceJet's reservation system should be flexible enough to grow with the company and
adapt to changing business requirements as well as rising demand. In order to
accommodate new features, services, and alliances as the airline develops, it should also
be adaptable enough.
2.2 Product Features

• User registration and authentication: With this function, users can register for accounts
on the SpiceJet website or mobile application. Users enter personal information such their
name, email address, and contact details during registration. The process of
authentication guarantees that specific capabilities, such as flight booking and reservation
management, are exclusively accessible to logged-in users.

• Booking and search for flights: With this tool, users can look for flights by entering
parameters like destination, departure time, and passenger count. Users can proceed to
book tickets for their preferred itinerary once they have identified flights that fit them.

• Reservation management: This tool allows users to see, edit, or cancel their flight
reservations. Users have the freedom to modify their travel arrangements, including
changing the passenger list or the dates of their flights.

• Seat selection: When making a reservation, users can decide where they want to sit. This
function guarantees a comfortable flight experience by letting passengers choose seats
based on their preferences, such as aisle or window seats.

• Interface for customer service: SpiceJet should offer an interface for customer service
so that customers can ask questions or get answers about their reservations. This could
involve features like email support, live chat, or a special helpline, making sure that
travelers get help quickly when they need it.

2.3 User Classes and Characteristics

• Passengers: Users who book flights through the system.

• Administrators: Staff responsible for managing system settings and configurations.

2.4 Operating Environment

2.4.1 Hardware Operating Environment:

• Servers
• Network Equipment
• End-User Devices

2.4.2 Software Operating Environment:

• Operating System
 • Web Server
• Database Management System (DBMS)
• Application Framework
• Security Software
• Payment Gateway Integration
• Monitoring and Management Tools

3 Functional Requirements
This section provides requirement overview of the system. Various functional modules that Can
be implemented by the system will be –

3.1Description:
• SpiceJet is a low-cost airline headquartered in Gurgaon India. It is the fourth largest
airline in the country by number of passengers carried, with a market share of 13.1% as
of February 2016. The airline operates 306 daily flights to 41 destinations, including 35
Indian and 6 international destinations from its hubs at Delhi and Hyderabad.

3.2Registration:
• If passenger want to book the tickets they have to register on that site before Booking the
tickets.

3.3Login:
• In order to book tickets, passengers must first log in to the system using a valid user ID
and password.

3.4Flight Search and Booking:

• Enable users to search for flights based on destination, date, and number of passengers.
• Show the available flights along with the relevant details such as seat availability,
pricing, and scheduling.
• Make it easier to book a few selected flights.

3.5Flight Status and Information:

 • Allow users to check the status of their booked flights.
• Provide recent details about flight schedules, cancellations, and delays.

3.6Seat Selection:
• Give customers the choice to choose their seats when making a reservation.
• Show the layout and available seats so that the user can choose.

3.7Reservation Management:
• Allow users to view, modify, or cancel their reservations.
• Update reservation status in real-time.

3.8Payment:
• Accept a variety of payment options, such as net banking, credit/debit cards, etc.

3.9Customer Support Interface:

• Offer customer support channels for resolving queries and providing help.
• Support options such as live chat, email support, and phone helpline.

3.10 Logout:
• After booking the tickets the customer will log out.

3.11 Technical Issues:

• This system will work on client-server architecture. It will require an internet server and
which will be able to run PHP application. The system should support some commonly
used browser such as IE etc.

4 External Interface Requirements

4.1 User Interfaces:
• The system should have simple and user-friendly interfaces for both desktop and mobile
devices.
• Clear presentation of flight options, simple navigation, and effective search features
should all be supported by interfaces.
4.2 Hardware Interfaces:
• Web servers for managing and delivering webpages to users.
• Database servers for safely managing and storing reservation data.
• Ticketing machines at airports for offline ticket purchases and modifications.
• The reservation system should be compatible with various hardware configurations
commonly used by customers, including desktop computers, laptops, smartphones, and
tablets.
• Devices for networking (firewalls, switches, and routers) that provide security and
communication.

4.3 Software Interfaces:

• Integration with flight data providers for real-time flight information.
• Integration of payment gateways to ensure secure transaction processing.
• Interface with CRM (Customer Relationship Management) systems for managing
customer data and preferences.
• Integration with seat inventory management systems for seat allocation.
• Interface with email services for sending booking confirmations and notifications.

5 Non-functional Requirements

5.1Performance Requirements:
• Response time for user interactions: 2 seconds.
• Support for concurrent bookings during peak hours: 1000 users.
• System load handling: up to 10,000 simultaneous users.

5.2Safety Requirements:
• The system should adhere to aviation safety regulations for data security and passenger
privacy.
• It should encrypt sensitive user information such as payment details and personal data to
protect against unauthorized access.
• Regular security audits and penetration testing should be conducted to identify and
address vulnerabilities.

5.3Security Requirements:
 • The system should have measures in place to prevent unauthorized access, data breaches,
and cyber-attacks.
• It should comply with industry standards such as PCI DSS for secure payment
processing.
• User authentication mechanisms should be robust to prevent account hijacking and
fraudulent activities.

5.4Software Quality Attributes:

• The system should be reliable, with a target uptime of 99.9%.
• It should to be expandable in order to handle future increases in the number of users and
reservations.
• The user interface should be intuitive and user-friendly, with clear navigation and
responsive design for different devices.
• Maintenance and updates should be easy to perform without disrupting service
availability.

6 Other requirements
6.1 Accessibility Requirements:
• The system should comply with accessibility standards (e.g., WCAG) to ensure usability
for users with disabilities.

6.2 Regulatory Compliance:

• Compliance with international aviation regulations and standards, including those related
to passenger data protection, aviation safety, and consumer rights.

6.3 Performance Monitoring and Optimization:

• Continuous monitoring of system performance metrics and proactive optimization efforts
to maintain optimal performance levels.
7 Data Flow Diagrams:

7.1 Level 0:

7.2 Level 1:
7.3 Level 2:
7.3.1 Registration:
7.3.2 Login:
7.3.3 Booking and Payment:
8. Use Case Diagrams:
 9. Test cases:

9.1. Login:

Pre-conditions:
User has valid username and password

Step Test Steps Test Data Expected Result Actual Result Status (Pass/Fail) Notes

User should be able to type User is navigated to Pass

the username and password dashboard with successful
1 Navigate to login page User= example@gmail.com successfully. login

Provide valid User is logged into portal

2 username Password: 1234 successfully

Provide valid
3 password

4 Click on Login button

Post-conditions:
User is validated with database and successfully login to account. The account session details are
logged in database.
 9.2. One-way Flight Booking:

Pre-conditions:
User is logged into the flight booking application.

Step Test Steps Test Data Expected Result Actual Result Status (Pass/Fail) Notes

Open the flight Departure airport: New Booking is successfully Booking is successfully Pass
1 booking application. York completed. completed.

Confirmation page displays Confirmation page

correct details (departure displays correct details.
Select one-way trip Destination airport: Los city, destination city, date,
2 option. Angeles number of passengers).

Enter departure
airport, destination
airport, departure Booking reference number is
date, and number of generated.
3 passengers. Departure date: 2024-05-15

Click on the search

4 button. Number of passengers: 2

Select a flight from the

5 search results.

6
Enter passenger
details.

7 Proceed to payment.

Complete the booking

8 process.

Post-conditions:
Booking is confirmed and a confirmation email is sent to the user.
 9.3. Payment Processing:

Precondition:
Flight is selected, and passenger details are entered.

Step Test Steps Test Data Expected Result Actual Result Status (Pass/Fail) Notes
Navigate to the Payment is processed Payment is processed Pass
payment page after successfully. successfully.
selecting a flight and
entering passenger Credit card number: [Valid
1 details. credit card number]

Enter valid payment Confirmation page displays Confirmation page

details (credit card the payment confirmation displays the payment
number, expiration Expiration date: [Valid along with booking details. confirmation along with
2 date, CVV, etc.). expiration date] booking details.

Review the payment Payment confirmation email Payment confirmation

details and total is sent to the user. email is sent to the user.
3 amount. CVV: [Valid CVV]

Click on the "Pay Now" Billing address: [Valid billing

4 or equivalent button. address]

Verify the payment

confirmation page or Total Amount: [Amount to
5 message. be paid]

Postcondition:
Payment is confirmed, and booking is completed.