Grand Travel Airlines has to keep track of its flight and airplane history. A flight is uniquely identified by the combination of a flight number and a date. In addition, every flight has an actual departure time and an actual arrival time. Every passenger who has flown on Grand Travel has a unique passenger number plus their name, address, and telephone number. For a particular passenger who has taken a particular flight, the company wants to keep track of the fare that she paid for it and the date that she made the reservation for it. Clearly, a passenger may have taken many flights (he must have taken at least one to be in the database) and every flight has had many passengers on it.
A pilot is identified by a unique pilot (or employee) number, a name, date of birth, and date of hire. A flight on a particular date has exactly one pilot. Each pilot has typically flown many flights but a pilot may be new to the company, is in training, and has not flown any flights, yet.
Each airplane has a unique serial number, a model, manufacturer name, passenger capacity, and year built. A flight on a particular date used one airplane. Each airplane has flown on many flights and dates, but a new airplane may not have been used at all, yet.
Grand Travel also wants to maintain data about its airplanes' maintenance history. A maintenance procedure has a unique procedure number, a procedure name, and the frequency with which it is to be performed on every airplane. A maintenance location has a unique location name, plus an address, telephone number, and manager. Grand Travel wants to keep track of which airplane had which maintenance procedure performed at which location. For each such event it wants to know the date of the event and the duration.
Attributes
Pilot Number
Pilot Name
Date of Birth
Date of Hire
Flight Number
Date (of flight)
Departure Time
Arrival Time
Passenger Number
Passenger Name
Address
Telephone Number (of passenger)
Fare
Reservation Date
Serial Number
Model
Passenger Capacity
Year Built
Manufacturer
Procedure Number
Procedure Name
Frequency
Location Name
Address
Telephone Number (of maintenance location)
Manager
Date (of maintenance)
Duration
Functional Dependencies
Pilot Number Pilot Name
Pilot Number Date of Birth
Pilot Number Date of Hire
Flight Number, Date (of flight) Departure Time
Flight Number, Date (of flight) Arrival Time
Flight Number, Date (of flight) Pilot Number
Flight Number, Date (of flight) Serial Number
Passenger Number Passenger Name
Passenger Number Address (of passenger)
Passenger Number Telephone Number Flight Number, Date, Passenger Number Fare
Flight Number, Date, Passenger Number Reservation Date
Serial Number Model
Serial Number Passenger Capacity
Serial Number Year Built
Serial Number Manufacturer
Procedure Number Procedure Name
Procedure Number Frequency
Location Name Address (of maintenance location)
Location Name Telephone Number
Location Name Manager
Serial Number, Procedure Number, Location Name, Date Duration For each of the following tables, first write the table's current normal form (as 1NF, 2NF, or 3NF.) Then, for those tables that are currently in 1NF or 2NF, reconstruct them as well-structured 3NF tables. Primary key attributes are underlined. Do not assume any functional dependencies other than those shown.
a. Flight Number, Date (of flight), Passenger Number, Departure Time, Arrival Time, Passenger Name
b. Flight Number, Date (of flight), Passenger Number, Fare, Reservation Date
c. Flight Number, Date (of flight), Serial Number, Departure Time, Arrival Time, Model, Passenger Capacity
d. Pilot Number, Pilot Name, Date of Birth, Date of Hire
e. Serial Number, Procedure Number, Location Name, Date (of maintenance), Duration, Year Built, Manufacturer, Procedure Name, Frequency
Correct Answer:
Verified
Flight Number, Date (of flight), ...
View Answer
Unlock this answer now
Get Access to more Verified Answers free of charge
Q48: Convert the following Central Zoo entity-relationship diagram
Q49: In first normal form a single, generally
Q50: In third normal form, all foreign keys
Q51: Converting from first to second normal form
Q52: A partial functional dependency occurs when an
Q53: A group of tables is said to
Q54: The determinant of an attribute must always
Q56: Central Zoo wants to maintain information
Q57: Convert the following Grand Travel Airline entity-relationship
Q58: The data normalization process is progressive. If
Unlock this Answer For Free Now!
View this answer and more for free by performing one of the following actions
Scan the QR code to install the App and get 2 free unlocks
Unlock quizzes for free by uploading documents