Business case

The need for airline reservation system came from the fact that automated technical systems were taking over manual systems. Given below are some of the characteristics of manual and technical systemManual system: The system is very time consuming and lazy. This system is more prone to errors and sometimes the approach to various problems is unstructured. Technical system: With the advent of latest technology if we do not update our system then our business result in losses gradually with time. The technical systems contains the tools of latest trend i.e. computers printers, fax, Internet etc. The systems with this technology are very fast, accurate, user-friendly and reliable. Few factors that directs us to develop a new system are- Faster System Accuracy Reliability, Informative Reservations and cancellations from any place Airlines were among the first to use databases in a geographically distributed manner-terminals situated around the world accessed the central database system through phone lines and other data networks The airline reservation system maintains information on flights, classes of seats, personal preferences, prices and bookings. The system allows three classes of users: casual, registered and administrators; to view flights on particular days and to book a number of seats. Users of the airline ticket booking system will have the ability to search for the cheapest flights available for a certain destination on a certain date. After finding and selecting the flight required, a user can book a ticket. Only registered users will be allowed to book a ticket; hence, while booking the ticket, the user has the option either to provide authentication details or, if not registered, to register with the application. Before finalising the booking of a flight, personal information must have been entered. Registered users may go on a waiting list for seats if the desired flight does not have enough free seats. Management of the waiting list is left undefined. Registered users must logon using a user-id and password, and the system maintains personal information for such users. Registered users may view and update their personal information. The system is expected to have a Web user interface for customers and an authorization based Web interface for administrators. The key elements in the system revolve around planned and actual Flights, and the reservations made by customers of actual flights. A planned flight represents a

forward schedule of the expected flight pattern for a flight. Given below is a model of the business case which represents how airline reservation system works and how various entities and departments interact with each other.

Booking department

FLIGHT MAINTENANCE, BOOKING, CANCELLATION

RECEIVE CUSTOMER REQUEST

Passenger List, Confirmed list

Airline

Passenger

Reports

Reservation System
Waiting list cancellation

DATA STORAGE

DATA ACCESS

Ticket reservation Cancellation, Request for enquiry

Database

Passenger list, Fleet info concession, Flight information, Fare details

ER diagram

CODE

NAME

CITY

STATE
DEPARTURE

ARRIVAL TIME

N
DEPT. TIME

LEG NO.

AIRPORT FLIGHT LEG

ARRIVAL

N 1
INSTANCE OF

ARRIVES CAN LAND LEGS TYPE NAME MAX SEATS DEPARTS

AIRPLANE TYPE 1

COMPANY

FLIGHT 1
DEPT. TIME FARES

TYPE
CODE

N
AIRPLANE ID

AMOUNT

TOTAL NO. OF SEATS

FARE N
ASSIGNED
DATE

1 AIRPLANE

LEG INSTANCE
PHONE NAME

SEAT NO.

N SEAT

NO OF AVAL SEATS
RESERVATIO N

Rectangles represent entity sets, Ellipses represent attributes. Diamonds represent relationship sets. Lines link attributes to entity sets and entity sets to relationship sets. Double ellipses which represent multi valued attributes. Double lines which indicate total participation of an entity in a relationship set.

List of transactions
The database represents each Airport, keeping its unique Airport Code, the Airport Name, and the City and State in which the Airport is located. Each airline flight has a unique number, the Airline for the flight, and the Weekdays on which the flight is scheduled A flight is composed of one or more flight legs for example, flight number CO1223 from New York to Los Angeles may have two flight legs, leg 1 from New York to Houston and leg 2 from Houston to Los Angeles. Each flight leg has a leg number, Departure airport and Scheduled Departure Time, and an arrival airport and Scheduled Arrival Time. A leg instance is an instance of a flight leg on a specific date. The actual departure and arrival airports and Times are recorded for each flight leg after the flight leg has been concluded. The Number of available seats and the airplane used in the leg instance are also kept. The customer reservations on each leg instance include the customer name, phone, and seat number(s) for each reservation. Information on Airplanes and Airplane Types are also kept. For each Airplane type, the Type Name, manufacturing company, and maximum number of seats are kept. The Airports in which planes of this type Can Land are kept in the database. For each Airplane, the Airplane Id, total number of seats, and Type are kept Below mentioned are the basic transactions that will take place - Enter the details of the traveller. Check for availability of tickets. Inform the traveller the position of the available seat. Ask his/her decision whether to reserve the ticket or not.

Positive reply-book ticket after receiving the amount for the cost of ticket. Issue the ticket. Ask the traveller to check in time so that he/she doesnt miss the plan because of delay. Update the database before the next booking is to be done.

Attributes and Entities

Relationships
One to many Airport to flight leg Flight leg to leg instance Airplane type to airplane Airplane to leg instance Flight to fare Number of available seats to seat one to one legs to flight airport to airplane type airport to leg instance legs to fares flight leg to flight