Question

The AIRLINE relational database schema shown in the above figure describes a database for airline
flight information. Each FLIGHT is identified by a Flight_number, and consists of one or more
FLIGHT_LEGs with Leg_numbers 1, 2, 3, and so on. Each FLIGHT_LEG has scheduled arrival and
departure times, airports, and one or more LEG_INSTANCEs—one for each Date on which the flight
travels. FAREs are kept for each FLIGHT. For each FLIGHT_LEG instance, SEAT_RESERVATIONs are kept,
as are the AIRPLANE used on the leg and the actual arrival and departure times and airports. An
AIRPLANE is identified by an Airplane_id and is of a particular AIRPLANE_TYPE. CAN_LAND relates
AIRPLANE_TYPEs to the AIRPORTs at which they can land. An AIRPORT is identified by an Airport_code.
2. Extend your design to satisfy the following requirements:
• Separate the CUSTOMER entity from the SEAT_RESERVATION and extend it with the following
attributes; e-mail, adress, country, passport number.
• Create a COMPANY entity for both AIRPLANE and AIRLINE. Use generalization/specialization
hierarchy.
• Create an entity for frequent flyer customer tracking called FFC to keep track of the customers’
flight information. If a customer has checked-in physically a flight create a transaction record
with the mileage information assigned to that flight leg.
Identify all the important concepts represented in EER diagram.

Answer 1

so, what's the problem?
Start by defining your tables.
Look for similar examples online. You will find many.
Do not expect anyone here to undertake such a project for you.