0% found this document useful (0 votes)
93 views

Software Requirement Specification

This document provides a software requirements specification for an airline reservation system. It outlines three main features: 1) allowing customers to view available flights and book tickets, 2) modifying existing reservations, and 3) cancelling reservations. For each feature, it describes the purpose, user inputs/outputs, and functional requirements. The document also covers the system interfaces, user interfaces, hardware requirements, and other high-level aspects of the reservation system.

Uploaded by

Raja Raghu
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)
93 views

Software Requirement Specification

This document provides a software requirements specification for an airline reservation system. It outlines three main features: 1) allowing customers to view available flights and book tickets, 2) modifying existing reservations, and 3) cancelling reservations. For each feature, it describes the purpose, user inputs/outputs, and functional requirements. The document also covers the system interfaces, user interfaces, hardware requirements, and other high-level aspects of the reservation system.

Uploaded by

Raja Raghu
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/ 10

SOFTWARE REQUIREMENT SPECIFICATION

FOR

AIRLINE RESERVATION SYSTEM


Prepared by :
Group Name: <place your group name here>
Neha Sharma Nonika Gill Rajan Sharma Sahil Sharma Raghu Raja Sharma student student student student student <e-mail> <e-mail> <e-mail> <e-mail> <e-mail>

INSTRUCTOR : LAB SECTION: TEACHING ASST:

Er.Loveleen Kaur

COURSE: Software Engineering

DATE: 18-01-2012

AIRLINE RESERVATION SYSTEM SOFTWARE REQUIREMENTS SPECIFICATION:


1. INTRODUCTION: 1.1. PURPOSE: The main purpose of this software is to reduce the manual errors involved in the airline reservation process and make it convenient for the customers to book the flights as when they require such that they can utilize this 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 available with different timings for a particular date and provides customers with the facility 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 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 Practitioners Approach By 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 software each will its purpose and its main functions. It also gives details about the interface 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 interfaces related 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 base through the network connection.

2.1.2 User Interfaces


The screen formats and menu structure should be in such a way that even have users will find it easy to use. The product must be use-friendly and very inter-active. The functionality provided by the system like displaying error 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:

2.1.5 Communication Interfaces


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 64 MB RAM for client systems.

2.1.7 Operation
The users can first make a reservation in a particular flight for a particular date and time. The system provides the customer with a pin code which gives him access to either make any changes in his reservation or cancel a reservation. These must also be back up of data to enable any easy recovery from any features.

2.1.8 Site Adaptive Requirements


The ARS software is an independent and self-contained product and no modification are required to adapt to a particular installation.

2.2 PRODUCT FUNCTIONS


The major functions include y Providing flight details y Flight bookings for a particular destination, date and time and also providing with a pin code. y Allowing the customer to modify or cancel his reservation provided the correct pin code is given. y 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 is sufficient.

2.4 CONSTRAINTS
y y y y y y y y Regulatory policies: It is a mandatory that no text book must be left empty or contains insufficient data. Hardware limitations: There must be a 64 MB on board memory Control functions: The software must be very user-friendly and display appropriate error messages. Interfaces to other applications: Not applicable. Parallel operations: It must support many users simultaneously. Reliability requirements: Data redundancy and use of special/blank characters must be avoided. Safety/security considerations: The application must be exited always normally. 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 the customer. Future changes like providing different types of flights with different classes like business class, economic class will allow the customers to benefit from one facility.

2.6 APPORTIONING OF REQUIREMENTS


The necessity of providing options to customer to choose their seat or to 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 y 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. y WINDOW FORMAT/ORGANIZATION: When the user chooses some 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. y DATA FORMAT: The data entered by the users will be alpha numeric. y END MESSAGES: When there are some exceptions raising error like entering invalid details, then error messages will be displayed prompting the users to re-enter the details.

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 Key board To accept data from user Source of Input like pin code, personal details, flight details Printer To print the bookings mode Destination of Output E.g.: Destination chosen with date and timings

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 communication only with the server and not with any client system. An LAN of 10 Mbps is used.

3.2 SOFTWARE PRODUCT FEATURES

3.2.1 FEATURE 1
The ability of the software is to provide the details of the flights available and allow the customers to choose a particular destination and make a reservation.

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

3.2.1.2 STIMULUS/RESPONSE
Once the user chooses the particular option, the web pages corresponding to that are to be displayed on the screen i.e., it will 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 within 10 seconds.

3.2.1.3.1.2 INPUTS
The user must enter the destination with date and timings and must 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 is displayed confirming his reservation and displays the pin code.

3.2.2 FEATURE 2
The software allows the user to modify an already existing reservation made 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
The purpose is to allow the customer to make any changes in his personal details or flight booking details.

3.2.2.2 STIMULUS/RESPONSE
Once the user requests for changing his reservation, it must be 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, then would notify the person by displaying error messages.

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 to modify his reservation.

3.2.2.3.1.3 PROCESSING
The pin code is processed and checked for his validity. If it is correct 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 pin code, the user can now modify his reservation. A new pin code will be generated for the customers.

3.2.3 FEATURE 3
The software allows the user to cancel an already existing reservation made by the customer who has booked the ticket.

3.2.3.1 PURPOSE
The purpose is to allow the customer to cancel his reservation if not required.

3.2.3.1 STIMULUS/RESPONSE
Once the user requests for canceling his reservation, it must be displayed on the screen prompting the customer to enter his pin code.

3.2.3.3 ASSOCIATED FUNCTIONAL REQUIREMENTS 3.2.3.3.1 FUNCTIONAL REQUIREMENTS


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

3.2.3.3.1.1 INTRODUCTION

The system will allow the customer to cancel his reservation provided correct pin code has been entered by the customer.

3.2.3.3.1.2 INPUT
The user should enter his pin code which gives him access to cancel his reservation.

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

3.2.3.3.1.4 OUTPUT
Given the correct pin code, the user can now cancel his reservation.

3.2.4 FEATURE 4
The software must also give a report on the number of reservations made for a particular flight.

3.2.4.1 PURPOSE
The purpose is to enable the administrator to view the number of people in a particular flight.

3.2.4.2 STIMULUS/RESPONSE
Once the user requests for this option, all the details of the customers who have made reservation will be displayed.

3.2.4.3 ASSOCIATED FUNCTIONAL REQUIREMENTS 3.2.4.3.1 FUNCTIONAL REQUIREMENTS


If no reservations are made, then a message is displayed that no bookings have been made.

3.2.4.3.1.1 INTRODUCTION
The system will allow the administrator to view all the details of the customer who have made reservations.

3.2.4.3.1.2 INPUT
The administrator must enter the password so that access is given only to him to view the details of all the customers.

3.2.4.3.1.3 PROCESSING

The password is processed and checked for its validity. If it is not correct, then the administrator is asked to enter the correct password.

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

3.3 PERFORMANCE REQUIREMENTS


y y At any instant, a maximum of four nodes or users will be given access simultaneously. Since the program handles multiple users, if more than one person attempts to same date to the files stored in the data base, the program will lock the data file using a 2-phase commit protocol to prevent simultaneous access.

3.4 DESIGN CONSTRAINTS


y y y 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.2 Reliability


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

3.5.2 Availability
The factors guarantee the softwares 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
y y y It must be ensured that 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 a sound technical knowledge about maintaining the software and further enhancements will be undertaken by the developer.

3.5.5 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

You might also like