0% found this document useful (0 votes)
596 views15 pages

Airline Reservation System: Prof. Jyotiranjan Hota

The document describes requirements for an airline reservation system. The system will allow users to search for flights by entering criteria like destination, dates, and class of travel. It will book tickets by collecting passenger details and accepting online payments. The system provides secure payment processing and allows users to print tickets or check flight statuses by passenger name record (PNR) number. Key requirements include user interfaces for searching, booking, and paying for flights as well as storing passenger and flight data in a database.

Uploaded by

tulika_agarwal
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
596 views15 pages

Airline Reservation System: Prof. Jyotiranjan Hota

The document describes requirements for an airline reservation system. The system will allow users to search for flights by entering criteria like destination, dates, and class of travel. It will book tickets by collecting passenger details and accepting online payments. The system provides secure payment processing and allows users to print tickets or check flight statuses by passenger name record (PNR) number. Key requirements include user interfaces for searching, booking, and paying for flights as well as storing passenger and flight data in a database.

Uploaded by

tulika_agarwal
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 15

AIRLINE RESERVATION SYSTEM

Submitted to: Submitted by:


Prof.  Jyotiranjan Hota Ankit jain 09bshyd0110
Astha bhat 09bshyd0192
Akshita lakhanpal 09bshyd0061
Tulika poddar 09bshyd0932
Priyanka Datta 09bshyd0599
Contents
1 Introduction..................................................................................................................2
1.1 Purpose..................................................................................................................2
1.2 Scope.....................................................................................................................2
1.3 Definitions, acronymns, abbreviations..................................................................2
1.4 REFERENCES......................................................................................................2
1.5 OVERVIEW.........................................................................................................2
2 Overall Description......................................................................................................2
2.1 PRODUCT PERSPECTIVE.................................................................................2
2.1.1 SYSTEM INTERFACES..................................................................................2
2.1.2 INTERFACES...................................................................................................2
2.1.3 HARDWARE INTERFACES...........................................................................3
2.1.4 SOFTWATRE INTERFACES..........................................................................3
2.1.5 COMMUNICATION INTERFACES...............................................................3
2.2 PRODUCT FUNCTIONS.....................................................................................3
2.3 CONSTRAINTS...................................................................................................4
3 specific requirements............................................................................................5
3.1 external interface requirements.............................................................................5
3.1.1 USER INTERFACES.............................................................................................5
3.1.2 Hardware interfaces................................................................................................7
3.1.3 Software interfaces.................................................................................................7
3.1.4 Communication Interfaces......................................................................................7
3.2 SYSTEM FEATURES..........................................................................................7
3.2.1 Flight Information Maintenance........................................................................7
3.2.2 Ticket Reservation System................................................................................9
3.2.3 Payment system.................................................................................................9
3.2.4 Special Offer System.......................................................................................10
3.3 Performance requirements..................................................................................11
3.4 DESIGN CONSTRAINT....................................................................................11
3.5 SOFTWARE SYSTEM ATTRIBUTES..................................................................11
3.5.1 Reliability........................................................................................................12
3.6 LOGICAL DATABASE REQUIREMENTS.....................................................13
3.7 OTHER REQUIREMENTS...............................................................................13
1 Introduction

1.1 PURPOSE
This document is the Software Requirement Specification for Airline ticket reservation
system and will outline the purpose and functionalities of this project. This document
contains the functional and non-functional requirements as specified by the client.

1.2 SCOPE
Airline ticket reservation system will enable company to book the tickets for passengers
at the airports. We will be able to select the flight and class according to their choice and
provide variable mode of payments.

1.3 DEFINITIONS, ACRONYMNS, ABBREVIATIONS

Term Description
sHTTP Secure HyperText Transfer Protocol
ARS Airline Reservation System
SRS Software Requirements Specification Document

1.4 REFERENCES

(I) www.google.com

(II) www.microsoft.com\access

(iii) www.yatra.com

1.5 OVERVIEW
This document will contain the requirements for the different functions to be inculcated
in the Airline reservation system. The basic requirements will be listed first and later on
the specific requirements. This document will only contain requirements for those
functions that are planned to be developed soon and not all the possible demos we
want/will develop.
2 Overall Description

The ARS uses latest access 2007 technology to enable to book tickets and provides a
secure environment to make payment. The purpose of the system is to provide passengers
the freedom to choose their flight, class and mode of payment. This project will be made
as flexible as possible to suit the needs of each individual and can be easily customized.

2.1 PRODUCT PERSPECTIVE

ARS will be stand alone independent system. It will take the input and provides ticket
confirmation PNR code. Along with this system will enable user to query about flights
schedules and their ticket status. All the features will be packaged as a single system.

2.1.1 SYSTEM INTERFACES

(i) ARS takes inputs and flight preference from the user.

(ii) ARS can print the ticket directly

2.1.2 INTERFACES

(i) ARS interacts with user with GUI. It has a flight search screen where user can
select source and destination cities and all the flights plying on that route on
the selected date will be displayed.

(ii) ARS has a reservation screen where user after selecting the flight can enter the
no of passengers travelling and their personal information.

(iii) ARS provides a secure payment portal which uses secure HTTP layer for
transaction and third party certificate for authentication.

(iv) ARS provides a query screen where user can check the status of the ticket .

2.1.3 HARDWARE INTERFACES


(i) Screen resolution of at least 800x600 resolution for proper viewing of screens.

2.1.4 SOFTWATRE INTERFACES

(i) Any GUI operating system like Windows, Fedora.

(ii) Microsoft access as database for storing data.

2.1.5 COMMUNICATION INTERFACES

None

2.2 PRODUCT FUNCTIONS

A summary of major functions that the system will perform:

(i) A flight search facility where user can select his preference about the date of
travel, class and source and destination cities. All the flights matching the
criteria will be displayed.

(ii) Ticket reservation facility where user selects his preferred flight and books a
ticket by entering the personal information about the passengers and selects
the preferred mode of payment.

(iii) A secure payment portal where user can make payment through credit or debit
card.

(iv) Provide ticket which can be printed directly.

(v) User can check flight schedules or status of their tickets through their PNR no.

(vi) Users can get their tickets cancelled 24 hrs before flight is scheduled to fly.
2.3 CONSTRAINTS

 System will accept only VISA or MASTERCARD thereby limiting payment


option.

 Due to security reason certain browser feature will be disabled during payment.

3.0 SPECIFIC REQUIREMENTS

This section contains the software requirements to a level of detail sufficient to


enable designers to design the system, and testers to test the system.

3.1 EXTERNAL INTERFACE REQUIREMENTS

3.1.1 USER INTERFACES

The following screens will be provided:

Flight Search Screen

This will be the first screen that will be displayed. It will allow user to search for
flights. User will be required to select the source city, destination city, preferred
class of travel, date of travelling and budget constraint if any. All the flights
matching the criterian will be displayed on the screen.

Ticket Reservation Screen

After users selects his preferred flight for travel user will be directed to this
screen. User will be required to enter personal information of the travelers. User
will be asked to enter the name, age, address, email id and contact number of
individual passengers.
Payment Screen

After entering the passenger information user will be asked his preferred mode of
payment. System enables user to pay through credit card, debit card or cheque.
For cheque payments the same will be required to be mailed by the user to a
company’s address and needs to be verified before generation of ticket.

Ticket Printing Screen

After verification of payment (instantaneously for card payments) system will


generate ticket for passengers which can be printed directly using printer at client
side or user can get the tickets mailed to their email ids.

Query Screen

This screen enables user to make some general queries. User can check the
flight schedules for the next week, their prices for economy and business class.
User can also enter their PNR number and get the status for their tickets.

Ticket Cancellation Screen

Users can get their tickets cancelled 24hrs prior to the flight. The amount will be
refunded, after appropriate deductions, depending on the mode of payment
selected during ticket reservation. For payments made through cheque and cash
refund will be in form of cheque and for card payments refund will be made to the
card holders account.

Report generation Screen

Reports can be generated only by authorized personnel of the company. The


page will be accessible only to authorized users. User can generate various
routine reports like flight efficiency and usage rate on click of buttons. Further
user will have an option to enter customized SQL query and execute it. The
result will be returned in tabular form. Reports can be printed using the browser.
Administrator Login Screen

Administrator can login to the system using this screen. Administrator will be
required to enter the password to gain access to the system. Password will be
authenticated with the password stored in backend.

Flight Information Screen

The page will be accessible only to the administrator. Administrator will be


allowed to Add, delete or modify flight information like flight schedule, flight price
for different class, flight number. Flight route etc.

3.1.2 Hardware interfaces

As stated in Section 2.1.3

3.1.3 Software interfaces

As stated in Section 2.1.4

3.1.4 Communication Interfaces

As stated in Section 2.1.5

3.2 SYSTEM FEATURES

3.2.1 Flight Information Maintenance System

Description

This system maintains information of various flights which the company operates
on various routes. It stores the flight number, departure time, source city, arrival
time, destination city, number of seats in executive class and economy class,
price of executive and economy class and flight route
Entities: Flight

Attributes:

1. Flightno: flight number

2. Departure

3. Arrival

4. Source

5. Destination

6. Seatexec

7. Seateco

8. Via

9. Costexec

10. costeco

Validity checks

(i) Only system administrator can insert or edit information in the system.

(ii) Flight no can be of “aa-0000” format only

(III) None of the field except the route field can be left blank.

(IV) Flightno is the primary key

Error Handling\Response to Abnormal Situations


If any of the above validation checks are violated appropriate error messages are
displayed and the information is discarded.

3.2.2 Ticket Reservation System

Description

The system will maintain details about all the passengers booked for various
flights or cancel their tickets. Users will be asked to enter personal information
about the passengers. It stores information like passenger name, date of
booking, special offers etc. The system will allow insertion of new records but
doesn’t allow updation or deletion of existing records.

Entities: Passenger, cancelled tickets

Attributes:
1. pnr
2. passengername
3. dob
4. telno
5. flightnum
6. address
7. seatno
8. dateofbooking
9. gender
10. sourcecity
11. destinationcity
12. offerno

Validity checks

(i) PNR no will be self generated by the system which will be the primary
key. PNR will be of the form aaa-000000.

(ii) Date and Time must be entered in a standard format and should be
correct.

(iii) Flight number must be of the format “aa-0000”


Error Handling\Response to Abnormal Situations

If any of the above validation checks are violated appropriate error messages are
displayed and the information is discarded.

3.2.3 Payment system

This system provides user to make secure payment for the booked ticket. The
system will be secured using sHTTP protocol and third party certification. The
system allows user to select mode of payment from credit card, debit card or by
cheque. For card payment user will be asked to enter the card details( card no,
card holder name, card validity and security code) which will be verified by third
party(VISA or MASTERCARD). Upon verification amount will be billed to user.
For payment by cheque user will be required to mail the cheque to company. The
fare will be calculated using the cost from flight tables and any special offers
used by user. The system will allow insertion of new records but doesn’t allow
updation or deletion of existing records.

Entities: mode of payment

Attributs:

1. Pnr

2. Fare

3. Mode

4. Status

5. cardno

Validity check

(i) All functions for this system must be performed in real time.
(ii) Certain browser functions like scripts, back navigation must be
disabled due to security reason.

(iii) PNR no will be the primary key

Error Handling\Response to Abnormal Situations

In case any of the above validation cannot be achieved then the system sounds
off an alarm to alert neighbors of an emergency.

3.2.4 Special Offer System

Description

It will store information about special offers offered by the airline company.
Administrator will be the sole authorized person to insert, delete, update record of
offers.

Entities: Offer

Attributes:

1. Offerno

2. discount

Validation checks

(i) Offer number must be of the format “aa-00”

(ii) Offerno is the primary key

Error Handling\Response to Abnormal Situations


If any of the above validation checks are violated appropriate error messages are
displayed and the information is discarded.

3.3 PERFORMANCE REQUIREMENTS

The system must respond in real time. Seat reservations must be reflected on
real time basis and flight schedules details and fare must be latest i.e. system
needs to disable caching in these cases. System must also be robust in nature.

3.4 DESIGN CONSTRAINT

None

3.5 SOFTWARE SYSTEM ATTRIBUTES

3.5.1 Reliability

When user wants to call the system over a given period of time, the system should

correctly deliver services as expected by the user. The reliability of the system shall be

good if it delivers services as specified. Otherwise, reliability is bad and it shall produce

unexpected output. So, program should be changed according to right situation.

3.5.2 Availability

When the system has any request at any given time, system should be available, it should

be up and running and able to deliver useful service at this time. The availability of the

system shall be good if it delivers services when it is requested. Otherwise, if requests are

not responded at any given time then it implies bad availability.

3.5.3 Security
The system should resist accidental or deliberate intrusions, when users operate on the

system. If the system should not resist accidental or deliberate intrusions, then important

data – such as credit card number, id number, username, etc. – which belongs to user,

shall be stolen by hacker. Thus, security of the system shall be low and trust of users shall

be ruined. So, security of the system is very important for users.

3.5.4 Maintainability

When the system is used, new requirements may emerge. When these requirements are

emerged, the system should be changeable to accommodate these requirements for

maintaining the usefulness of the system. If the system is not maintainable, then the

system can not be modified for new requirements. In this situation, a new system should

be developed for provide new requirements. The maintainability is important for avoiding

from cost.

3.5.5 Performance

The system should use the minimum part of memory. The processes of the system should

use the processor most efficiently. User should finish operation in the least time interval.

3.5.6 Repairability

When the system is used, system failures are inevitable. The disruption caused by failure

can be minimized if the system can be repaired quickly. So, the system should be

possible to find the problem, access the component that has failed and make changes to

fix that component. When the system has a repair, the source code should be modified.

3.6 LOGICAL DATABASE REQUIREMENTS

(I) passenger
(II) flight

(III) offer

(IV) cancelled tickets

3.7 OTHER REQUIREMENTS

none

You might also like