DESIGN AND IMPLEMENTATION OF AIRLINE RESERVATION AND TICKET BOOKING SYSTEM

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 flight’s 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, 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.

ANALYSIS

2.REQUIREMENTS ELICITATION: 

Reqirement number	Description	Type	Priority
Req-1	The user will be able to search for flights through a standard screen.	Functional	Must have
Req-2	Database administrator maintains the user details and the flights details in the database.	Non functional	Must have
Req-3	Through a standard flight search method  the user will be able to search one-way,round trip or multi destination flights.	Functional	Must have
Req-4	The user should able to specify the departure,arrival places and date of their flight.	Functional	Must have
Req-5	By advanced flight search method the user will allow the user to specify a preffered airline by its name or its number.	Functional	Could have
Req-6	The user will have the option to select the either non-stop,single stop or multi-stop flights.	Functional	Must have
Req-7	The user can only search for a flight in the future and with in only one year of current date.	Functional	Must have
Req-8	Any error in entry of the system will stop the system fro processing the search. an error message will be presented to the user.	Functional	Must have
Req-9	The user will be able to see the price,duration of trvelling,departure time and arrival time.	Functional	Must have
Req-10	User will able to specify the  flight class which will be with respect to the flight choosen.	Functional	Could have
Req-11	The user will be able to choose the seats from the list of available seats of particular flights.	Functiuonal	Must have
Req-12	The user must complete all the necessary steps to book flight to be gaurenteed and autherentised.	Functional	Must have
Req-13	After booking the flight the user may cancel or modifing their flight.	Functional	Must have
Req-14	Response time of the airline reservation system must be less than 5 sec most of time.	Non functional	Shall have
Req-15	Ars shall be able to handle atleast 1000 transactions  per second.	Non functional	Shall have
Req-16	Ars should  be available 24×7.	Non functional	Must have
Req-17	Ars shall always provide real time information about flight availability information.	Non functional	Must have
Req-18	The web interface should be interactive and easily navigable users  sholud be able to understand the menu and options provided by ars.	Nonfunctional	Must have
Req-19	Users need to authenticated before having access to any personal data	Non functional	Must have
Req-20	Ars shall authenticate the  users credit cards and their personal information.	Functional	Must have
Req-21	Support for waiting list functionality.	Functional	Shall have
Req-22	The ars shall be able to handle the situation where flight services are available to multiple cities or a single city.	Functional	Could have
Req-23	Only the system abministrator hat the right to change the system parameters.	Non-functional	Shall have
Req-24	Ars should be roboust enough to have a high degree fauklt tolerance.	Non-functional	Shall have

 

3. System Requirements Specification   

HARDWARE:

 PROCESSOR      : PENTUIUM IV 2.6 GHz

RAM                     : 512MB DD RAM

MONITOR           : 15” COLOR

HARD DISK        :250 GB

CDDRIVE                        : LG52X

KEYBOARD       : STANDARD 102 KEYS

MOUSE                :OPTICAL MOUSE

SOFTWARE:

FORNT END                   :JAVA,HTML,SERVLETS

BACKEND                      : ORACLE 10i

OPERATING SYSTEM  : WINDOWS XP

                                        Use-case view

4. IDENTIFICATION OF ACTORS

Actors are not part of system.

Actors represent anyone or anything that interacts with (input to receive output from) the system.

An actor is someone or something that:

Ø  Interacts with or uses the system.

Ø  Provides input tot and receives information from the system.

Ø  Is external to the system and has no control over the use cases.

Actors are discovered by examining:

Ø  Who directly uses the system?

Ø  Who is responsible for maintaining the system?

Ø  External hardware used by the system.

Ø  Other systems that need to interact with the system.

The need of the actor are used to develop use cases. This insures that the system will be what the user expected.

Graphical Depiction

An actor is a stereotype of a class and is depicted as “stickman” on a use-case diagram.

Naming:

The name of the actor is displayed below the icon.

Questions that help to identify actors

1. Who is interested in a certain requirement
2. Where is the system used within the organization?
3. Who will benefit from the use of the system?
4. Who will supply the system with information, use this information, and remove this information?
5. Who will support and maintain the system?
6. Does the system use an external resource?
7. Does one person play several different roles?
8. Do several people play the same role?
9. Does the system interact with a legacy system?

Using the above questions we have identified four actors is online airline reservation system. They are

1)      Traveler

2)      Credit and authorization

3)      Airline database

4)      User database

Customer: Initially Customer searches the fights available in the web page by submitting departure city and arrival city. After he chooses a flight from a light of available flights. After choosing he has to submit his details for booking and confirm the booking. He can also have the ability to cancel the flight if any problem occurs.

UML notion:

2) Database Administrator: It is responsible for maintaining all the rights details such as flight number, company, price duration of journey. The request come to any airline database is queried and executed. The query may be either executable or update query. It is invoked by the booking system whenever the traveler confirms the booking. It maintains the customer details such as name, address, city, state and contact number. Whenever the customer cancels the booking his details will be removed from the database.

UML notation

5. IDENTIFICATION OF USE-CASES AND SUB USE-CASES

Use case is a sequence of transactions performed by a system that yields a measurable result of values for a particular actor. The use cases are all the ways the system may be used.

Graphical Depiction:

The base shape of a use case is an ellipse:

Naming

Ø  A use case may have a name, although it is typically not a simple name. It is often written as an informal text description of the actors and the sequences of events between objects. Use case names often start with a verb.

Ø  The name of the use case is displayed below the icon.

Questions that help to find use cases

1. What are the tasks of each actor?
2. Will any actor create, store, change, remove or read information in the system?
3. What use cases will create, store, change, remove, or read this information?
4. Will any actor need to inform the system about sudden, external changes?
5. Does any actor need to be informed about certain occurrences in the system?
6. What use cases will support or maintain the system?
7. Can all functional requirements be performed by the use cases?

By applying the above questions to the online shopping the following use cases are identified. They are

1)      Search Flight

This use case is started by traveler.  It provides the facility for traveler to search for flight based on departure and arrival city.

Request Complete Work Here