AIRLINE RESERVATION SYSTEM

Submitted to:
Ms. Dimple chawla Assistant Professor

Submited by:
Deepika (09212304412) Deepti.K(09612304412) Surjeet Kaur(03312304412)

INDEX
S.No 1. 2. 3. 4. 5. 6. Problem Statement Software Requirements Specifications Use case Diagrams Data Flow Diagrams Entity Relationship Diagrams Questionnaire Contents Teachers Signature

PROBLEM STATEMENT
The web based airline reservation system project is an attempt to stimulate the basic concepts of airline reservation system. The system enables the customer to do the things such as search for airline flights for two travel cities on a specified date, choose a flight based on the details, reservation of flight and cancellation of reservation. The system allows the airline passenger to search for flights that are available between the two travel cities, namely the Departure city and Arrival city for a particular departure and arrival dates. The system displays all the flights details such as flight no, name, price and duration of journey etc. After search the system display list of available flights and allows customer to choose a particular flight. Then the system checks for the availability of seats on the flight. If the seats are available then the system allows the passenger to book a seat. Otherwise it asks the user to choose another flight. To book a flight the system asks the customer to enter his details such as name, address, city, state, and credit card number and contact number. Then it checks the validity of card and book the flight and update the airline database and user database. The system also allows the customer to cancel his/her reservation, if any problem occurs.

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: 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. 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 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 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 The user inputs should be valid and within the given range. 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 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

Use Case Diagram

Figure 1: Use case Diagram

Use case Description

This use case the shows how a customer of an Airline Reservation system can reserve flight online Actors: Customer, Administrator

Precondition:

The customer must book flight before payment,, the customers and admin must make sure the flight details such as departure airport and date are correct

Basic Flow of Event

-Users Log into the system - users enters flight details - users enter personal details such as name, address and social security number -users reserve ticket -users pay for ticket by credit card or pay pal

Alternate Flow

-If the users of the systems enters wrong information, like if the departure date is after the supposed arrival date, A pop message would show - if no destination is added the system would tell the user to ass a destination

Key Scenarios

-The users of this system must enter the correct details before sending the http Request

Post Condition

-Successful Completion: The user has finished making the Reservation and has obtained a receipt -Failure Completion: The user did not enter details correct, incorrect password, did not pay.

Special Requirement

-Users must be connected to the internet - Users should use webs browsers such as google chrome and internet Explorer.

DATA FLOW DIAGRAM: LEVEL 0: Reservation User Airline reservation System Cancellation

Display

LEVEL 1(a):

User

Reservation

Accept the details

Reserve in the file LEVEL 1(b): Accept the details

Passenger Database

User

Cancellation

Cancel in the file

Passenger Database

Entity Relation Diagram

Questainare
1 Your age
A- Below 16 (1) B- 16-25 (18) C- 26-35 (20) D- 36-45 (4) E- 46-55 (0) F- 56-65 (0) G- Above 65 (1)

2 Your gender
A- Male (29) B- Female (15)

3 Your country
A- Pakistan (14) B- Malaysia (10) C- Other (4) D- Indonesia (4) E- Philippines (3) F- India (2) G- United States of America (1) H- Thailand (1) I- Ecuador (1) J- Hong Kong(SAR) (1) K- Others (3)

4 Your education level

A- Primary (0) B- Secondary (0) C- High School (0) D- University (14) E- Postgraduate (30)

5 How frequently you shop online?

A- Mostly (4) B- Occasionally (11) C- Rarely (16) D- Never (13)

6 Have you ever booked an online airline ticket?

ABYes (if Yes please attempt SECTION B only) (28) No (if No please attempt SECTION C only) (16)

7 Which of the following airlines web-site you have used to book ticket?

A- Malaysia Airline (8) B- Emirates Air (4) C- British Airways (1) D- Thai Airways (7) E- Lufthansa Airline (0) F- Pakistan International Airline (2) G- Air Asia (14) H- Other (11)

No Selection (17) Select 1 item (18) Select 3 items (5) Select 5 items (0) Select 2 items (3) Select 4 items (2) Select 6 items (0)

Select 7 items (0) Select 8 items (0) 8 Have you ever tried to make changes in your traveling dates online?
A- Never (17) B- Unable to do so (2) C- Option not available (5) D- Successful (3)

9 Have you ever tried to cancel your ticket online?

A- Never (13) B- Unable to do so (4) C- Option not available (8) D- Successful (2)

10 Have you ever tried to transfer your ticket online?

A- Never (18) B- Unable to do so (2) C- Option not available (6) D- Successful (1)

11 Have you ever tried to correct error (such as typos) in you name or in your address online?
A- Never (19) B- Unable to do so (2) C- Option not available (3) D- Successful (3)

12 Have you ever tried to reserve a ticket for few days with the intention to buy it later?
A- Never (13) B- Unable to do so (3) C- Option not available (5) D- Successful (6)

13 Would you like to use "make online changes in traveling schedule" feature in online system?

A- Strongly Disagree (1) B- Disagree (0) C- Neutral (3) D- Agree (8) E- Strongly Agree (14)

14 Would you like to use "online cancellation of ticket" feature in online system?
A- Strongly Disagree (1) B- Disagree (1) C- Neutral (3) D- Agree (6) E- Strongly Agree (15)

15 Would you like to use "online transfer of ticket" feature in online system?
A- Strongly Disagree (0) B- Disagree (1) C- Neutral (2) D- Agree (10) E- Strongly Agree (13)

16 Would you like to use "online correction of typo errors" feature in online system?
A- Strongly Disagree (0) B- Disagree (1) C- Neutral (3) D- Agree (5) E- Strongly Agree (17)

17 Would you like to use "online reservation of ticket" feature in online system?
A- Strongly Disagree (0) B- Disagree (0) C- Neutral (3) D- Agree (5) E- Strongly Agree (18)

18 Reading characters on the screen of online reservation web site was hard.
A- Strongly Disagree (4) B- Disagree (9) C- Neutral (7) D- Agree (3) E- Strongly Agree (3)

19 Organization of information was confusing.

A- Strongly Disagree (2) B- Disagree (5) C- Neutral (10) D- Agree (7)

E- Strongly Agree (2)

20 Sequence of screens was confusing.

A- Strongly Disagree (1) B- Disagree (7) C- Neutral (10) D- Agree (6) E- Strongly Agree (1)