Scribd
Upload
4K views2 pages

Airline ER

The document outlines requirements for designing a database for an airline. The database needs to track customers and reservations, flight statuses and schedules, seat assignments, and future flight plans. An entity-relationship diagram, relational schemas, and constraints including primary keys and foreign keys are required. Entities include passengers, airports, booking offices, airplanes, airlines, and flights. Relationships include booking tickets, airplanes landing at airports, airlines owning airplanes, flights flying for airlines, flights traveling routes, and routes charging fares. Constraints prevent null values for key passenger, airport, flight, and route fields.

Uploaded by

Sahil Ahuja
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
4K views2 pages

Airline ER

The document outlines requirements for designing a database for an airline. The database needs to track customers and reservations, flight statuses and schedules, seat assignments, and future flight plans. An entity-relationship diagram, relational schemas, and constraints including primary keys and foreign keys are required. Entities include passengers, airports, booking offices, airplanes, airlines, and flights. Relationships include booking tickets, airplanes landing at airports, airlines owning airplanes, flights flying for airlines, flights traveling routes, and routes charging fares. Constraints prevent null values for key passenger, airport, flight, and route fields.

Uploaded by

Sahil Ahuja
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Problem Statement: Design a database for an airline ,the database must keep track of customers and their reservations,

flights and their status, seat assignments on individual flights, and the schedule and routine of future flights. Your design should include an E-R diagram ,a set of relational schemas, and a list of constraints, including primary key and foreign key constraints. Assumptions: Passenger cannot make cancellations. Entities: Passenger: This entity includes passenger details P-id,name,age address,e-mail. Airport:This entity includes Airport details like Airport code,name,city and country. Booking Office :It includes Office _Id and Office_name. Airplane :This entity includes Reg_No,Flight type,ans no of seats. Airlines :This entity represents the Airline Name and its owner. Flight: This entity includes details about the flights which comprises of Flight, Class Eg:Business class, Economy class etc.,source and destination airports of flights,its departure date and time,arrival date and time.

Relationships: Books Ticket : It is a relationship between the Passenger and Booking office. Lands On : Its a relationship between the Airplane and Airport,it depicts which plane lands on which airport. Owned By :Its a relationship which shows which relationship between the Airplane and Airlines ie. Which airplane belongs to which Airlines. Flies:is a relationship that tells which Flight flies under which Airline. Travels on:Its a relationship that tells us which flight travels on which routes ie. It shows the relationship between Flight and Route. Charges :Its a relationship between the Route and Fare entities.

Constraints: 1.Passport Id ie P-Id and Name cannot be null in Passenger table 2.Airport code name cannot be null 3.Flight no,Source Destination cannot be null 4.Route no cannot be null. 5.Airplane has total participation o Land on relationship.

You might also like