A database represents each AIRPORT, keeping its unique AirportCode,the AIRPORT Name, and the City and State in which the AIRPORT is
located
(a) Each airline FLIGHT has a unique number, the Airline for the
FLIGHT, and the Weekdays on which the FLIGHT is scheduled (for
example, everyday of the week except Sunday can be coded as X7).
(b) 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 DEPARTURE
AIRPORT and Scheduled Departure Time, and an ARRIVAL AIRPORT
and Scheduled Arrival Time.
(c) A LEG INSTANCES is an instance of a FLIGHT LEG on a specific Date
(for example, C01223 leg 1 on July 30, 1989). 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 AIRPLAN used in the LEG INSTANCE are also kept.
(d) The customer RESERVATIONS on each LEG INSTANCE include the
Customer Name, Phone, and Seat Number(s) for each reservation.
(e) Information on AIRPLANES and AIRPLAN TYPEs are also kept. For
each AIRPLAN TYPE (for example, DC-10), the TypeName,
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,
TYPE are kept.
(i) Draw an E-R diagram.
(ii) Map E-R diagram to Relational model.
