Introduction

 INTRODUCTION
The purpose of this document is to build an online system to manage flights and
passengers to ease the flight management.
The purpose of the online flight management system is to ease flight
management and to create a convenient and easy-to-use application for
passengers, trying to buy airline tickets. The system is based on a relational
database with its flight management and reservation functions.
We will have a database server supporting hundreds of major cities around the
world as well as thousands of flights by various airline companies.
 PRODUCT PERSPECTIVE
A distributed airline database system stores the following information.
 Flight details:
It includes the originating flight terminal and destination terminal,
along with the stops in between, the number of seats
booked/available seats between two destinations .
 Customer description:
It includes customer code, name, address and phone number. This
information may be used for keeping the records of the customer for
any emergency or for any other kind of information.
 Reservation description:
It includes customer details, code number, flight number, date of
booking, date of travel.
 USER CLASS and CHARACTERISTICS
Users of the system should be able to retrieve flight information between two
given cities with the given date/time of travel from the database. A route from
city A to city B is a sequence of connecting flights from A to B such that: a) there
are at most two connecting stops, excluding the starting city and destination
city of the trip, b) the connecting time is between one to two hours. The system
will support two types of user privileges, Customer, and Employee. Customers
will have access to customer functions, and the employees will have access to
both customer and flight management functions. The customer should be able
to do the following functions:
Make a new reservation
• One-way
• Round-Trip
• Multi-city
• Flexible Date/time
• Confirmation
Cancel an existing reservation
View his itinerary
The Employee should have following management functionalities:
CUSTOMER FUNCTIONS.
• Get all customers who have seats reserved on a given flight.
• Get all flights for a given airport.
• View flight schedule.
• Get all flights whose arrival and departure times are on time/delayed.
• Calculate total sales for a given flight.
ADMINISTRATIVE
• Add/Delete a flight
• Add a new airport
• Update fare for flights.

• Add a new flight leg instance.
• Update departure/arrival times for flight leg instances.
Each flight has a limited number of available seats. There are a number of flights
which depart from or arrive at different cities on different dates and time.
 HARDWARE REQUIREMENT AND SOFTWARE REQUIREMENT
 Operating environment for the airline management system is as listed

below. <<Include the details as per your application >>
 distributed database
 client/server system
 Operating system: Windows.
 database: sql+ database
 platform: vb.net/Java/PHP
DESIGN and IMPLEMENTATION CONSTRAINTS
 The global schema, fragmentation schema, and allocation schema.
 SQL commands for above queries/applications
 How the response for application 1 and 2 will be generated. Assuming

these are global queries. Explain how various fragments will be combined
to do so.
 Implement the database at least using a centralized database

management system.
ASSUMPTION DEPENDENCIES
 Let us assume that this is a distributed airline management system and it is

used in the following application:
 A request for booking/cancellation of a flight from any source to any

destination, giving connected flights in case no direct flight between the
specified Source-Destination pair exist.
 Calculation of high fliers (most frequent fliers) and calculating appropriate
reward points for these fliers.
 Assuming both the transactions are single transactions, we have designed

a distributed database that is geographically dispersed at four cities Delhi,
Mumbai, Chennai, and Kolkatta as shown in fig. below.
 SYSTEM FEATURES
 DESCRIPTION and PRIORITY
 The airline reservation system maintains information on flights, classes of

seats, personal preferences, prices, and bookings. Of course, this project
has a high priority because it is very difficult to travel across countries
without prior reservations.
 STIMULUS/RESPONSE SEQUENCES
 Search for Airline Flights for two Travel cities
 Displays a detailed list of available flights and make a “Reservation” or

Book a ticket on a particular flight.
 Cancel an existing Reservation.
 SOFTWARE QUALITY ATTRIBUTES
 AVAILABILITY: The flight should be available on the specified date and

specified time as many customers are doing advance reservations.
 CORRECTNESS: The flight should reach start from correct start terminal
and should reach the correct destination.
 MAINTAINABILITY: The administrators and flight in chargers should

maintain correct schedules of flights.
 USABILITY: The flight schedules should satisfy a maximum number of

customers needs.

Introduction

Uploaded by

Copyright:

Available Formats

Introduction

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Introduction

Uploaded by

Copyright:

Available Formats

 INTRODUCTION

 USER CLASS and CHARACTERISTICS

Make a new reservation

Cancel an existing reservation

View his itinerary

The Employee should have following management functionalities:

• Get all customers who have seats reserved on a given flight.

• Get all flights for a given airport.

• View flight schedule.

• Calculate total sales for a given flight.

• Add a new airport

• Update fare for flights.

• Update departure/arrival times for flight leg instances.

 HARDWARE REQUIREMENT AND SOFTWARE REQUIREMENT

 Operating environment for the airline management system is as listed

 Operating system: Windows.

 database: sql+ database

DESIGN and IMPLEMENTATION CONSTRAINTS

 The global schema, fragmentation schema, and allocation schema.

 SQL commands for above queries/applications

 How the response for application 1 and 2 will be generated. Assuming

 Implement the database at least using a centralized database

 Let us assume that this is a distributed airline management system and it is

 A request for booking/cancellation of a flight from any source to any

 Assuming both the transactions are single transactions, we have designed

 DESCRIPTION and PRIORITY

 The airline reservation system maintains information on flights, classes of

 Search for Airline Flights for two Travel cities

 Displays a detailed list of available flights and make a “Reservation” or

 Cancel an existing Reservation.

 SOFTWARE QUALITY ATTRIBUTES

 AVAILABILITY: The flight should be available on the specified date and

 MAINTAINABILITY: The administrators and flight in chargers should

 USABILITY: The flight schedules should satisfy a maximum number of

You might also like