SUB:- FSD SUB CODE : 3341603

Practical – 3

❖SOFTWARE REQUIREMENTS SPECIFICATION

1. INTRODUCTION
1.1. PURPOSE
Th e main pu rpo se o f this so ftware is to reduce th e
manu al erro rs involved in the airline reservation process
and make it convenient for thecustomers to book the flights as
when they require such that they can utilizethis software to make
reservations, modify reservations or cancel a particular reservation.

1.2 SCOPE
The name of the software is “AIRLINE RESERVATION
SYSTEM”.
This software provides options for viewing different flights
availabled ifferen t timings fo r a p articular date and p ro
v id es custo mers with th efacility to book a ticket, modify or
cancel a particular reservation but it does not provide the
customers with details of cost of the ticket and it does not
allow the customer to modify a particular part of his reservation
and he/she can modify all his details.
1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS

ARS-Airline Reservation System

LAN-Local Area Network
GUI-Graphical User Interface
OS-Operating System
RAM-Random Access Memory
MB-Mega Bytes
GB-Giga Bytes
Mbps-Mega bits per second
THAKUR VIVEK 1
 SUB:- FSD SUB CODE : 3341603

HDD-Hard Disk Drive

1.4 REFERENCES
The books and materials referred during the pre-development stages of
the project include
1. Software Engineering-A Practitioner’s ApproachBy Roger S. Pressman
2. Software Engineering-By James Peters

1.5 OVERVIEW
The rest of the document deals about all the main features of this
softwareeach will its purpose and its main functions. It also gives
details about theinterface with other products and related functionality of
each product.

2. OVERALL DESCRIPTION

2.1 PRODUCT PERSPECTIVE

The “ARS” software is an independent application. It is a self-
contained product. The system interfaces, user interfaces and hardware interfac
esrelated with this software are defined as follows.

2.1.1 System Interfaces

The client systems should be able to share the data available in the data
basethrough the network connection.

2.1.2 User Interfaces

The screen formats and menu structure should be in such a way that
evenh a v e u s e r s w i l l f i n d i t e a s y t o u s e . T h e p r o d u c t m u s t b e
u s e - f r i e n d l y a n d very inter-active. The functionality provided by the
system like displayingerror messages should adapt itself to the different users
of the software.

2.1.3 Hardware Interfaces

Nil

2.1.4 Software Interfaces

Name of the language: Visual Basics

2.1.5 Communication Interfaces

THAKUR VIVEK 2
 SUB:- FSD SUB CODE : 3341603

There is an LAN used for communication among the different client systems to
be used.

2.1.6 Memory Constraints

The system would require disk space of 10 GB and a 256 MB HDD and 64MB
RAM for client systems.

2.1.7 Operation
The users can first make a reservation in a particular flight for a
particular d a t e a n d t i m e . T h e s y s t e m p r o v i d e s t h e c u s t o m e r w i t h
a p i n c o d e w h i c h gives him access to either make any changes in his
reservation or cancel areservation. These must also be back up of data to
enable any easy recoveryfrom any features.

2.1.8 Site Adaptive Requirements

The “ARS” software is an independent and self-contained product and
nomodification are required to adapt to a particular installation.

2.2 PRODUCT FUNCTIONS

The major functions include

 Providing flight details

 Flight bookings for a particular destination, date and time
and also providing with a pin code.
 Allowing the customer to modify or cancel his reservation provided the
correct pin code is given.
 Displaying a report of the number of people flying in a particular flight.

2.3 USER CHARACTERISTICS

No technical experience is required basic knowledge of handling system
issufficient.

2.4 CONSTRAINTS
 Regulatory policies: It is a mandatory that no text book must be leftempty
or contains insufficient data.
 Hardware limitations: There must be a 64 MB on board memory
 Control functions: The software must be very user-friendly anddisplay
appropriate error messages.
 Interfaces to other applications: Not applicable.
 Parallel operations: It must support many users simultaneously.

THAKUR VIVEK 3
 SUB:- FSD SUB CODE : 3341603

 Reliability requirements: Data redundancy and use of

special/blank characters must be avoided.
 Safety/security considerations: The application must be exited
alwaysnormally.

Higher order language requirements: VB

2.5 ASSUMPTIONS AND DEPENDENCIES

It is assumed that the details of the cost of ticket are already known to
thec u s t o m e r . F u tu r e c h a n g e s l i k e p r o v i d i n g d i f f e r e n t t y p e s o f f l
i g h t s w i t h different classes like business class, economic class will allow the
customersto benefit from one facility.

2.6 APPORTIONING OF REQUIREMENTS

T h e n e c e s s i t y o f p r o v i d i n g o p t i o ns t o c u s t o m e r t o c h o o s e t h e i r
s e a t o r t o choose for economic or business class can be delayed until future
versions of the software are developed.

3. SPECIFIC REQUIREMENTS

3.1 EXTERNAL INTERFACE REQUIREMENTS

3.1.1 User Interfaces

The interface must be easy to understand. The user interface includes

 SCREEN FORMATS/ORGANIZATION: The introductory screen

will be the first to be displayed which will allow the users to
choose either of the two options, viewing flight detail or booking
a ticket.
 W I N D O W F O R M A T / O R G A N I Z ATI O N : Wh e n t h e u s e r
c h o o s e s s ome other option, then the information pertaining to that
choice will be displayed in a new window which ensures multiple
windows to be visible on the screen and the users can switch between
them.
 Data : The data entered by the user will be alphanumeric.
 END MESSAGES: When there are some exceptions raising error
likee n t e r i n g i n v a l i d d e t a i l s , t h e n e r r o r m e s s a g e s w i l l
b e d i s p l a y e d prompting the users to re-enter the details.

THAKUR VIVEK 4
 SUB:- FSD SUB CODE : 3341603

3.1.2 Hardware Interfaces

The system must basically support certain input and output devices.
Their descriptions are as follows.

Name of Item Description of Purpose Source of

Input/Description of
output
Keyboard To accept data from Source of Input
user like pin
code, personal details,
flightdetails
Printer To print the bookings Destination of Output
mode E.g.:
Destinationchosen with
date andtimings

3.1.3 Software Interfaces

Not applicable since the product under considerations is an independent one.

3.1.4 Communication Interfaces

Every client system connected through LAN establishes a
communicationonly with the server and not with any client system. An LAN
of 10 Mbps isused.

3.2 SOFTWARE PRODUCT FEATURES

3.2.1 FEATURE
The ability of the software is to provide the details of the flights
available a n d a l l ow t h e c u s t o m e r s t o c h o o s e
a p a r t i c u l a r d e s t in a t i o n a n d m a k e a reservation.

3.2.1.1 PURPOSE
The purpose of this is to enable the users to view the different flightsavailable
so as to make it convenient for him to make a reservation.

3.2.1.2 STIMULUS/RESPONSE

THAKUR VIVEK 5
 SUB:- FSD SUB CODE : 3341603

Once the user chooses the particular option, the web pages corresponding to that
are to be displayed on the screen i.e., it wi l l display the different flights
available to their respective destinations and allow the customer to book
a ticket.

3.2.1.3 ASSOCIATED FUNCTIONAL REQUIREMENTS

3.2.1.3.1 FUNCTIONAL REQUIREMENTS

Once the user makes a reservation, he must be provided with a pin code.

3.2.1.3.1.1 INTRODUCTION
The user must be provided with the required information within10 seconds.

3.2.1.3.1.2 INPUTS
The user must enter the destination with date and timings andmust make
reservation by giving his personal details like name,address, age, gender,
nationality.

3.2.1.3.1.3 PROCESSING
Recognizing the correct details are entered that a message isdisplayed
confirming his reservation and displays the pin code.

3.2.2 FEATURE
The software allows the user to modify an already existing reservationmade
by the customer if in case there are any changes that are to be
modified in the reservations of the ticket.

3.2.2.1 PURPOSE
T h e p u r p o s e i s t o a l l o w th e c u s to m er t o m a k e a n y c h a n g es i n
h i s personal details or flight booking details.

3.2.2.2STIMULUS/RESPONSE
Once the user requests for changing his reservation, it m
u s t b e displayed on the screen prompting the customer to enter his pin code.

3.2.2.3 ASSOCIATED FUNCTIONALITY REQUIREMENTS

3.2.2.3.1 FUNCTIONAL REQUIREMENTS

If the pin code provided by the customer does not match, thenwould
notify the person by displaying error messages.

THAKUR VIVEK 6
 SUB:- FSD SUB CODE : 3341603

3.2.2.3.1.1 INTRODUCTION
The system will allow the customer to modify his reservation provided
correct pin code has been entered by him.

3.2.2.3.1.2 INPUT
The user should enter his pin code which gives him access tomodify his
reservation.

3.2.2.3.1.3 PROCESSING
The pin code is processed and checked for his validity. If it iscorrect
then the user can modify his reservation else an error message will be
displayed asking the user to enter the correct pin code number.

3.2.2.3.1.4 OUTPUT
Given the correct password, the administrator can view all thedetails
of customers with date and time of their bookings made.

3.3 PERFORMANCE REQUIREMENTS

 At any instant, a maximum of four nodes or users will be given

accesssimultaneously.
 S i n c e t h e p r o g r a m h a n d l e s m u l t i pl e u s e r s , i f m o r e t h a n
o n e p e r s o n attempts to same date to the files stored in the data base, the
programw i l l l o c k t h e d a t a f i l e u s i ng a 2 - p h a s e c o m m i t
p r o t o c o l t o p r e v e n t simultaneous access.

3.4 DESIGN CONSTRAINTS

 Requires 256 MB on-board memory.
 Based completely on Windows functionality platform.
 The software should be portable and must be inaccessible to unauthorized
users.

3.5 SOFTWARE SYSTEM ATTRIBUTES

3.5.1 Reliability
The factors needed to establish the software expected reliability are
 The user inputs should be valid and within the given range.
 Normal termination of the program.

3.5.2 Availability
THAKUR VIVEK 7
 SUB:- FSD SUB CODE : 3341603

The factors guarantee the software’s availability includes proper termination

and correct input details. Also the resources used for the project development
are Microsoft Certified which speaks of its high quality standards.

3.5.3 Security
 It must be ensured that the access will be provided to the authorized
persons through user ID and password.
 Network security will be provided by the use of firewalls.
 Checks can be performed at regular internals to ensure data integrity.

3.5.4 Maintainability
The software will be developed by implementing the concept of modularity
which in turn reduces the complexity involved in maintaining it. The
administrator should have sound technical knowledge about maintaining the
software and further enhancements will be undertaken by the developer.

3.5.4 Portability
The application is portable which ensures its adaptability for use on different
computer terminals with different operating systems and standards.

3.6 LOGICAL DATABASE REQUIREMENTS

The system requires the use of text files to maintain the customers personal
details and his booking details. An entity must be used to specify the various
departments and the seats available in them. This information will be
used frequently by the authorities for verification.

3.7 OTHER REQUIREMENTS

Nil

4. INDEX
Nil

5. APPENDICES
Nil

THAKUR VIVEK 8