[attachment=10505]
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 Practitioner’s 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
2.1.4 Software Interfaces
Name of the language: Visual Basics
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
• 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 is sufficient.
2.4 CONSTRAINTS
• 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
• 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.
• 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.
• DATA FORMAT: The data entered by the users will be alpha numeric.
• 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.