UMBC
CMSC-461 Summer 2002
Database Management Systems
Project Requirements
1. Overview
The purpose of this project is (1) To analyze the requirements; (2) To design, implement,
document and test a database application which automates an airline database system.
The database system should perform the following basic functions: (1) When a passenger
makes reservations on a flight, the users can enter passenger information; (2) Before and after
a flight, the users can enter/modify flight information including flight schedule, passenger
check-in, etc.
The users of this application are staff members of the airline. It is assumed that all users have
network computers capable of running Java applications.
2. Information Requirement
In an airline database system, a number of different types of information need to be
maintained. They are classified according to the activities that take place:
 When a flight is scheduled, the following information is needed:
-Flight number
-Date
-Aircraft type (from those provided*)
-Source city & state (from list of cities provided**)
-Destination city & state (Give route if there are one or more intermediate stops)
(from list of cities provided**)
-Scheduled departure time(s) & date(s)
-Scheduled arrival time(s) & date(s)

Other flight information has to be entered:
-Flight number
-Date
-Number of seats booked
-Number of passengers on board

The following information on the flight passengers is needed:
-Flight Number
-Date
-Social Security Number
-First and last name
-Age
-Reservation status (Confirmed/Waiting with waiting number)
-Flight Class (from those provided ***)
-Seat number
-Amount charged
-Contact address
-Baggage information
Page 1 of 4
CMSC 461

Summer 2002 Project
Address should be maintained in the following format wherever appropriate:
-Street
-Apartment number
-City
-State
-Zip
-Telephone numbers (home & office)
-Email address
*The possible types of aircraft are: Boeing 727, 737, 747 and Airbus A300, 320, 340
** The cities in which the airline operates: New York, Washington D.C., Baltimore, L.A., San Francisco,
Seattle, Chicago, Newark, Detroit, Boston, Raleigh, Tucson, Columbus, Tampa, Houston, Las Vegas,
Minneapolis, Atlanta, Pittsburgh and Toronto
*** The possible types of flight class are: First, Business, and Economy
3. Function Requirement
The database application should be able to handle the occurrence of the following events
 When a flight is scheduled, the following information should be entered:
-Flight number, Date
-Source, destination & intermediate cities & state(s)
-Departure & arrival time(s) & date(s) at each city

When a passenger books a ticket, the following information should be entered:
- SSN
- Name
- Contact address
- Flight Class (from those provided ***)
- Amount paid
- Status of reservation (Confirmed/Waiting with waiting number)

Before a flight's departure, the following information can be entered or modified. This
information may be changed or entered at each intermediate city of the flight:
-Departure time(s) & date(s) may be changed if the flight is rescheduled
-Arrival time(s) & date(s) may be changed if the flight is rescheduled

When a passenger checks in, the following information should be entered:
-SSN
-Baggage carried
-Seat number assigned

After a flight’s arrival, the statistical information should be generated:
-The number of passengers on the flight
-The number of stops
-The total amount of time taken
CMSC 461
Summer 2002 Project
4. Submit this project
When the project is completed, a project needs to be submitted. You also need to demonstrate
the database application.
4.1
Project Report
The Project report should consist of the following sections:
A. Requirement Analysis
 Analyze project requirements and write high-level description of the tasks involved.
B. Database Design
 Develop an Entity-Relationship model detailing the relations involved.
 Identify the attributes of the entities and the relations along with the primary key for
each entity.
 List the constraints for each relation and entity.
 Give details of the procedures that you will implement in the database application.
You should be able to explain why you have chosen the particular design approach.
C. Implementation I: Create Database
 Design an Oracle database based on the design developed in section B.
 Implement SQL tables for the relations and the constraints. Maintain scripts for the
creation of tables.
 Submit pseudo-code for the procedures that you will develop.
 Justify your design choices.
D. Implementation II: Maintain Database
 Write embedded code to access, update and administer SQL tables made.
 Develop a user interface, using which each of these functions should be performed.
 Create indices for the database application. Justify the reasons.
 Integrate the user interface and rest of the database application.
E. Maintenance
 Make a user's guide for the users of the database application.
F: Evaluation
 Summarize the application
 Give the highlight of the application
 Give a list of the limitations and possible improvements of the application.
4.2
Project Demonstration
Populate the tables with data for
 At least 5 aircraft
 20 cities in which the airline operates
 Schedule at least 10 flights, at least 2 of which should have more than one intermediate
stop
 Each flight should have the details of at least 10 passengers.
The demonstration should include scheduling flights, entering and updating a flight’s
information, passenger booking and cancellation of a flight. The system must also include
features for user authentication for the above-mentioned functions, through the use of user-ids
and passwords.
CMSC 461
4.3
Summer 2002 Project
Miscellaneous
The final project report should document all the activities with appropriate E-R diagrams,
relation schema, etc. It should also give a list of the limitations of the application and give
possibilities for improvement.
Features and functions other than specified in the document can also be added but should be
documented clearly and demonstrated as well.