Online Air Ticket Reservation System (SRS)

UNIVERSITY OF ENGINEERING & MANAGEMENT, KOLKATA
University Area, Plot No. III - B/5, New Town, Action Area - III, Kolkata, West Bengal 700156
Software Engineering Laboratory

TOPIC :- Online Air Ticket Reservation System
Submitted By:
1. Rahul Roy
2. Godhuli Das
3. Soumi Adhikari
Under Supervision of: Prof Anay Ghosh and Prof Sreyashi

Bhattacharya
1
ACKNOWLEGMENT
This project would not have been possible without considerable

guidance and support. So, we would like to acknowledge those
who have enabled us to complete this project. Firstly we would
like to thank to our project supervisor, Prof Anay Ghosh And
Prof Sreyashi Bhattacharya for providing the guideline with
continues advice and feedback throughout the duration of
finishing this project.
………………
Date: 08.04.2019
Rahul Roy(43)
Godhuli Das(44)
Soumi Adhikari(45)
2
CERTIFICATE
This is to certify that the project entitled “Online Air Ticket

Reservation System” has been developed by “Rahul Roy,
Godhuli Das and Soumi Adhikari”. They have worked on the
project Online Air Ticket Reservation System. They have used Dev
C++ to develop the project. Their work is satisfactory.
I wish them all the best for their bright future.
DATE:
………………………
Project In-charge
3
Software Requirements Specification for Online Air Ticket Reservation System Page ii
Table of Contents
Table of Contents ...........................................................................................................................1
Revision History ............................................................................... Error! Bookmark not defined.
1. Introduction ..............................................................................................................................1
1.1 Purpose............................................................................................................................................. 1
1.2 Document Conventions.................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions .................................................................................. 1
1.4 Product Scope .................................................................................................................................. 1
1.5 References ........................................................................................................................................ 1
2. Overall Description ..................................................................................................................1
2.1 Product Perspective.......................................................................................................................... 1
2.2 Product Functions ............................................................................................................................ 2
2.3 User Classes and Characteristics ..................................................................................................... 2
2.4 Operating Environment.................................................................................................................... 2
2.5 Design and Implementation Constraints .......................................................................................... 3
2.6 User Documentation ........................................................................................................................ 3
2.7 Assumptions and Dependencies ...................................................................................................... 3
3. External Interface Requirements ...........................................................................................4
3.1 User Interfaces ................................................................................................................................. 4
3.2 Hardware Interfaces ......................................................................................................................... 4
3.3 Software Interfaces .......................................................................................................................... 4
3.4 Communications Interfaces ............................................................................................................. 4
4. System Features .......................................................................................................................5
4.1 Opening Screen ................................................................................................................................ 5
4.2 Book Tickets .................................................................................................................................... 5
4.3 Check Status..................................................................................................................................... 6
4.4 Cancel Tickets ……………………………………………………………………………..6
5. Other Nonfunctional Requirements .......................................................................................8
5.1 Performance Requirements .............................................................................................................. 6
5.2 Safety Requirements ........................................................................................................................ 6
5.3 Security Requirements ..................................................................................................................... 6
5.4 Software Quality Attributes ............................................................................................................. 6
5.5 Business Rules ................................................................................................................................. 7
6. Design Documents ...................................................................... Error! Bookmark not defined.
7. Output………………………………………………………………………………….……..5
Appendix A: Glossary....................................................................................................................9
Appendix B: Analysis Models .....................................................................................................13
Software Requirements Specification for Online Air Ticket Reservation System Page 1
1. Introduction
1.1 Purpose
 The purpose of this SRS is to describe the requirements involved

in developing a Airline Reservation system (ARS).
 The intended audience is any person who wants to reserve or cancel tickets or to check
the availability of Airline tickets
1.2 Conventions
This document uses the following conventions.

ER Entity Relationship
DFD Data Flow Diagram
1.3 Intended Audience and Reading Suggestions

This project is a prototype for the flight management system and it is restricted within
the college premises. This has been implemented under the guidance of college professors. This
project is useful for the flight management team and as well as to the passengers.
1.4 Product Scope

The purpose of the online air ticket reservation system is to ease flight management and
to create a convenient and easy-to-use application for passengers, trying to buy airline tickets.
The system is based on flight management and reservation functions. Above all, we hope to
provide a comfortable user experience along with the best pricing available.
1.5 References
https://krazytech.com/projects
2. Overall Description
2.1 Product Perspective
An airline ticket reservation system stores the following information.

 Flight details:
It includes the originating flight terminal and destination terminal, price of travel
between two destinations, flights available etc.
 Customer description:
It includes customer name, age, sex, email id and phone number. This information may
be used for keeping the records of the customer for any emergency or for any other kind
of information.
 Reservation description:
It includes customer details, PNR, flight number, date of booking.
2.2 Product Functions
 Viewing Flight Details

The user must have the access up-to-date information about the flights
including
 Flight number
 Flight Name
 Flight route(Start and Destination stations)
 Flight timings
 Reserving Tickets
The user must be able to reserve tickets after selecting
 Flight number
 Mode of Payment
 Cancelling Tickets
The user must be able to cancel tickets that he has earlier reserved by
quoting the ticket number, mode of payment and bank name.
2.3 User Classes and Characteristics
Users of the system should be able to retrieve flight information between two given cities with
the given date/time of travel from the database. A route from city A to city B is a sequence of
connecting flights from A to B (the starting city and destination city of the trip).
The system will support user privileges of Customer. Customers will have access to customer
functions, The customer should be able to do the following functions:
• Make a new reservation
• One-way
• Flexible Date
• Confirmation
• Cancel an existing reservation
• View his itinerary
2.4 Operating Environment
Operating environment for the airline management system is as listed below.

 Operating system: Windows.
 platform: DEV C++

.
2.5 Design and Implementation Constraints

At the time of reservation, each user is provided a unique ticket number that must be
used for further operation like cancellation or viewing details. Hence the user is required to
remember or store this number carefully.
2.6 User Documentation

 The intended users of this software need not have specific knowledge as to what is the internal
operation of the system. Thus the end user is at a high level of abstraction that allows easier,
faster operation and reduces the knowledge requirement of end user.
 The Product is absolutely user friendly, so the intended users can be the naïve users.
 The product does not expect the user to possess any technical background. Any person who
knows to use the mouse and the keyboard can successfully use this product.
2.7 Assumptions and Dependencies
Let us assume that this is airline ticket reservation system is used in the following application:
 A request for booking/cancellation of a flight from any source to any destination.
Assuming transaction is single transaction, we have designed a distributed database that is
geographically dispersed at four cities Delhi, Mumbai, Bangalore and Kolkata and International
for London, Dubai, Abu Dhabi, Singapore and New York.
3. External Interface Requirements
3.1 User Interfaces
 Front-end software: Dev C++

 Back-end software: C++ FPS
3.2 Hardware Interfaces

 Windows.
3.3 Software Interfaces
Software used Description

Operating system We have chosen Windows operating system for its best support and
user-friendliness.
DEV C++ To implement the project we have chosen DEV C++ language for
its more interactive support.
3.4 Communications Interfaces
This project supports all types of C++ supported IDE. We are using simple electronic forms in
output terminal for the reservation forms, ticket booking etc.
4. System Features
4.1 Opening Page

Description and Priority: This function allows a user to book , check or cancel tickets at their will. For the
system, when provided the details and choice, flight information or booking or cancelling pages will be delivered
at the same time.
Inputs: Choice of booking a ticket, cancelling a ticket or checking a ticket.
Source: All inputs are provided by user.
Outputs: Indication that user is in the system and selected required module.
Destination: The outputs are displayed on the screen as well as stored in the system.
Requires: The user provides choice according to the specified choices.
Pre-Conditions: User is not logged in.
Post-Conditions: User is logged and can access their required choice.
Side-Effects: When any number outside the required choice is selected, error occurs.
4.2 Book Tickets
Description and Priority: The user can use the Book Tickets function to purchase seats for an airplane
flight. The system shall present the user with information on all current flights. The user may then select source
and destination and fight on which to purchase seats. Finally, the system shall guide the user completely through
the checkout process.
Inputs: Domestic or International choice, Source, Destination, Flight name, User information.
Source: Inputs are from the user except flight information, which is retrieved from the system.
Output: The purchased seat are tied to the user’s account, so he/she can reserve seats later.
Destination: The booked flights will be stored in the user’s account information when the user finishes
payment. The flight information shall also display on the screen.
Pre-Conditions: The user must be logged in the session.
Post-Conditions: Completion of this function guarantees that the user has seats on a specific flight. Any
successfully-booked flight from this function is assumed to have completed payment already.
Side-Effects: User’s account is charged. Flight is associated with user’s account.
Stimulus/Response:
User Action System Application
1.The system shows the user a list of
domestic or International flights .
2. The user selects seats 3. The system checks for avaliable flights.
from a list flights by giving source,destination and allow users to confirm their selection.
and date of travel. The The seats and confirmation selection seats
on chosen as individual seats for the screen are displayed.
departing and returning flights.
.
4. The user confirms by giving personal 5. Once confirmed, the seats are applied
details on the screen. and user is shown a final confirmation
screen which displays selected seats
and account information.
4.3 Check Status

Description & Priority: This section shall allow the user to view flight information that
matches input criteria. The user will provide:
a. A PNR no. and Date
b. Departing/Arriving Cities and Date.
The system will display matching flight information
including the following fields:
o Flight Number
o Departure City
o Arrival City
Inputs: Departing city, Destination city, Departure date/time
Source: All inputs are provided by the user.
Outputs: Flight information including Flight Number, Departure City, Arrival City.
Destination: All outputs should display on the screen.
Pre-Conditions: None.
Post-Conditions: User has flight status for any matching flight.
Side-Effects: None
4.4 Cancel Ticket
Description and Priority: The user can use the Cancel Ticket function to cancel seats for an airplane flight.
The system shall ask for the details of the user. Finally, the system shall guide the user completely through the
checkout and cancellation process.
Inputs: PNR number, Flight Details, User information.

Source: Inputs are from the user retrieved from the system.
Output: The cancellation message of seat of the user.
Destination: The cancelled flight will be deleted from the user’s account information and displayed on the
screen.
Pre-Conditions: The user must be logged in the session.
Post-Conditions: Completion of this function guarantees that cancelled a specific flight.
Side-Effects: None
Stimulus/Response:
User Action System Application

1.The system asks for flight details.
2. The user gives details of flight and PNR no 3. The system checks for booked flight.
and allow users to cancel their selection.
The seats and cancelled seats are displayed.
.
5. Other Nonfunctional Requirements
5.1 Performance Requirements
 For each session,system shall guarantee the connection time. A close operation will be
performed when expired. This design is to satisfy each user’s usability and connection
quality.
 The system restarts after a session is closed.
5.2 Safety Requirements

If there is extensive damage such as a disk crash, the recovery method is not present. So
continuous session has to be kept open.
5.3 Security Requirements

PNR has to be kept at all costs,carefully.
5.4 Software Quality Attributes
 AVAILABILITY: The flight should be available on the specified date and specified
time as many customers are doing advance reservations.
 CORRECTNESS: The flight should reach start from correct start terminal and should
reach the correct destination.
 USABILITY: The flight schedules should satisfy a maximum number of customers

needs.
.
5.5 Business Rules
 A secure session is to monitor activity and remain open throughout the entire session. If
a certificate cannot be verified the session will not be created.
 1. A city of departure and city of arrival must be entered by the user.
2. A travel date must be entered by the user.
 All flights must be paid in full for the reservation to be successfully created.
 If a flight has been cancelled, the flight details should still be available to the user along
with a notation that the flight is no longer scheduled
6. Output
The first screen which appears

When you choose to book a domestic flight

Transaction using Debit Card

When you choose to book an international flight

Transaction using Net Banking
When you choose to check your flight details

When you choose to cancel your flight
This screen is displayed after you choose the Exit option

Appendix A: Glossary
 Authentication The process of identifying an individual, usually based on username and
password
 Input Criteria A defined particular group of criteria, which defines inputs.
Appendix B: Analysis Models
Class Diagram
Data Flow Diagram

ER Diagram
Structure Chart
Sequence Diagram

Online Air Ticket Reservation System (SRS)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Online Air Ticket Reservation System (SRS)

Uploaded by

Copyright:

Available Formats

UNIVERSITY OF ENGINEERING & MANAGEMENT, KOLKATA

Software Engineering Laboratory

Under Supervision of: Prof Anay Ghosh and Prof Sreyashi

This project would not have been possible without considerable

This is to certify that the project entitled “Online Air Ticket

 The purpose of this SRS is to describe the requirements involved

This document uses the following conventions.

1.3 Intended Audience and Reading Suggestions

1.4 Product Scope

2.1 Product Perspective

An airline ticket reservation system stores the following information.

2.2 Product Functions

 Viewing Flight Details

2.3 User Classes and Characteristics

2.4 Operating Environment

Operating environment for the airline management system is as listed below.

 platform: DEV C++

2.5 Design and Implementation Constraints

2.6 User Documentation

2.7 Assumptions and Dependencies

3. External Interface Requirements

3.1 User Interfaces

 Front-end software: Dev C++

3.2 Hardware Interfaces

3.3 Software Interfaces

Software used Description

3.4 Communications Interfaces

4.1 Opening Page

4.2 Book Tickets

4.3 Check Status

4.4 Cancel Ticket

Inputs: PNR number, Flight Details, User information.

User Action System Application

5. Other Nonfunctional Requirements

5.1 Performance Requirements

5.2 Safety Requirements

5.3 Security Requirements

5.4 Software Quality Attributes

 USABILITY: The flight schedules should satisfy a maximum number of customers

5.5 Business Rules

The first screen which appears

When you choose to book a domestic flight

Transaction using Debit Card

When you choose to book an international flight

Transaction using Net Banking

When you choose to check your flight details

When you choose to cancel your flight

This screen is displayed after you choose the Exit option

Appendix B: Analysis Models

Data Flow Diagram

You might also like