Project 3 Details: This project is based on eight tables (AIRPORT, FLIGHT, DEPARTURES, PASSENGER, RESERVATION, EQUIP_TYPE, PILOTS, and TICKET) that contain data about the Belle Airlines. Download and use data in Project 3 zip file for this project. Some Background on Belle Airlines Belle Airlines is a regional carrier that operates primarily in the southwestern United States. At the present time, Belle Airlines operates its own reservation information system. To simplify our analysis, we will assume that all reservations on Belle Airlines flights are placed through Belle Airlines employees. Flights are not booked through travel agents and Belle Airlines does not participate in industry-wide reservations services. Each flight is assigned a unique flight number and has its own set of flight characteristics (ie. flight number, origin, destination, departure time, arrival time, meal code, base fare, mileage between origin and destination, and number of changes in time zone between the origin and destination of the flight). Departures of each flight are stored in the Departures table. Each departure contains four attributes (flight number, departure date, pilot id, and equipment number). Belle Airlines flies out of airports located all over the country. Data on these airports is stored in the Airport table. Data on these airports includes: a three-character airport code, location of the airport, elevation, phone number, street address, city, stat, zip code, flight pay, date of birth, and date hired. The company also owns its own fleet of airplanes. Data on these airplanes is stored in the Equip_Type table which contains the following attributes: equipment number, equipment type, seating capacity, fuel capacity, and miles per gallon. Three additional tables populate the Belle Airlines database: the Passenger table (with attributes: passenger name, itinerary number, and confirmation number), the Reservation table (with attributes: confirmation number, reservation date, reservation name, reservation phone, reservation flight number, and reservation flight date), and the Ticket table (with attributes: itinerary number, flight number, flight date, and seat assignment).
Project 3 Details:
This project is based on eight tables (AIRPORT, FLIGHT, DEPARTURES, PASSENGER,
RESERVATION, EQUIP_TYPE, PILOTS, and TICKET) that contain data about the Belle Airlines. Download
and use data in Project 3 zip file for this project.
Some Background on Belle Airlines
Belle Airlines is a regional carrier that operates primarily in the southwestern United States. At the
present time, Belle Airlines operates its own reservation
we will assume that all reservations on Belle Airlines flights are placed through Belle Airlines employees.
Flights are not booked through travel agents and Belle Airlines does not participate in industry-wide
reservations services. Each flight is assigned a unique flight number and has its own set of flight
characteristics (ie. flight number, origin, destination, departure time, arrival time, meal code, base fare,
mileage between origin and destination, and number of changes in time zone between the origin and
destination of the flight). Departures of each flight are stored in the Departures table. Each departure
contains four attributes (flight number, departure date, pilot id, and equipment number).
Belle Airlines flies out of airports located all over the country. Data on these airports is stored in the
Airport table. Data on these airports includes: a three-character airport code, location of the airport,
elevation, phone number, street address, city, stat, zip code, flight pay, date of birth, and date hired. The
company also owns its own fleet of airplanes. Data on these airplanes is stored in the Equip_Type table
which contains the following attributes: equipment number, equipment type, seating capacity, fuel
capacity, and miles per gallon.
Three additional tables populate the Belle Airlines
passenger name, itinerary number, and confirmation number), the Reservation table (with attributes:
confirmation number, reservation date, reservation name, reservation phone, reservation flight
number, and reservation flight date), and the Ticket table (with attributes: itinerary number, flight
number, flight date, and seat assignment).
Trending now
This is a popular solution!
Step by step
Solved in 2 steps
1. Create a DFD
2.Convert the EERD into your logical schema
by Bartleby Expert
