Scribd
Upload
197 views2 pages

Flight Database ER Diagram Overview

The database stores information about airplanes, flights, passengers, and bookings. Airplanes have a model number and unique registration number. Flights have a unique number, departure and destination airports, and dates/times. Each flight uses a single airplane. Passengers have names and unique emails. Passengers can book seats on flights through bookings, which connect passengers to their selected flights. The registration number uniquely identifies airplanes. Flight numbers uniquely identify flights. Emails uniquely identify passengers.

Uploaded by

Manzar Ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
197 views2 pages

Flight Database ER Diagram Overview

The database stores information about airplanes, flights, passengers, and bookings. Airplanes have a model number and unique registration number. Flights have a unique number, departure and destination airports, and dates/times. Each flight uses a single airplane. Passengers have names and unique emails. Passengers can book seats on flights through bookings, which connect passengers to their selected flights. The registration number uniquely identifies airplanes. Flight numbers uniquely identify flights. Emails uniquely identify passengers.

Uploaded by

Manzar Ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
  • Sample Questions (ER Diagram)

Sample Questions (ER Diagram)

Question 1
Consider a CONFERENCE_REVIEW database in which researchers submit their research papers for
consideration. Reviews by reviewers are recorded for use in the paper selection process. The database
system caters primarily to reviewers who record answers to evaluation questions for each paper they
review and make recommendations regarding whether to accept or reject the paper. The data
requirements are summarized as follows:
■ Authors of papers are uniquely identified by e-mail id. First and last names are also recorded.
■ Each paper is assigned a unique identifier by the system and is described by a title, abstract, and the
name of the electronic file containing the paper.
■ A paper may have multiple authors, but one of the authors is designated as the contact author.
■ Reviewers of papers are uniquely identified by e-mail address. Each reviewer’s first name, last
name, phone number, affiliation, and topics of interest are also recorded.
■ Each paper is assigned between two and four reviewers. A reviewer rates each paper assigned to him
or her on a scale of 1 to 10 in four categories: technical merit, readability, originality, and relevance to
the conference.
Finally, each reviewer provides an overall recommendation regarding each paper.
■ Each review contains two types of written comments: one to be seen by the review committee only
and the other as feedback to the author(s)

Question 2
Consider a MOVIE database in which data is recorded about the movie industry. The data requirements
are summarized as follows:
Each movie is identified by title and year of release. Each movie has a length in minutes. Each has a
production company, and each is classified under one or more genres (such as horror, action, drama,
and so forth). Each movie has one or more directors and one or more actors appear in it. Each movie
also has a plot outline. Finally, each movie has zero or more quotable quotes, each of which is spoken
by a particular actor appearing in the movie. Actors are identified by name and date of birth and
appear in one or more movies. Each actor has a role in the movie.

Question 3

The flight database stores details about an airline’s fleet, flights, and seat bookings.
Again, it’s a hugely simplified version of what a real airline would use, but the
principles are the same.

Consider the following requirements list:


 The airline has one or more airplanes.
 An airplane has a model number, a unique registration number, and the capacity to
take one or more passengers.
 An airplane flight has a unique flight number, a departure airport, a destination
airport, a departure date and time, and an arrival date and time.
 Each flight is carried out by a single airplane.
 A passenger has given names, a surname, and a unique email address.
 A passenger can book a seat on a flight.
 An Airplane is uniquely identified by its RegistrationNumber, so we use this as the
primary key.
 A Flight is uniquely identified by its FlightNumber, so we use the flight number as the
primary key. The departure and destination airports are captured in the From and To
attributes, and we have separate attributes for the departure and arrival date and time.
 Because no two passengers will share an email address, we can use the EmailAddress
as the primary key for the Passenger entity.
 An airplane can be involved in any number of flights, while each flight uses exactly
one airplane, so the Flies relationship between the Airplane and Flight relationships
has cardinality 1:N; because a flight cannot exist without an airplane, the Flight entity
participates totally in this relationship.
 A passenger can book any number of flights, while a flight can be booked by any
number of passengers. As discussed earlier in Intermediate Entities,” we could specify
an M:N Books relationship between the Passenger and Flight relationship, but
considering the issue more carefully shows that there is a hidden entity here: the
booking itself. We capture this by creating the intermediate entity Booking and 1:N
relationships between it and the Passenger and Flight entities. Identifying such entities
allows us to get a better picture of the requirements.

Common questions

Powered by AI

In the flight database, the M:N relationship between passengers and flights is managed by introducing an intermediate entity called 'Booking' . This entity allows capturing specific details about each interaction between passengers and flights, such as seat assignments and booking statuses, which would not be possible in a direct M:N relationship. By creating 1:N relationships between 'Booking' and both 'Passenger' and 'Flight' entities, the database efficiently tracks and differentiates individual bookings, ensuring accurate record-keeping and query capabilities .

Recording quotable quotes in the MOVIE database provides significant advantages by adding layers of memorable content that enrich the narrative description of movies . This feature enhances data richness by capturing iconic lines that contribute to a movie's cultural impact and audience recall. Associating quotes with specific actors further personalizes and contextualizes these moments within the film's structure, aiding in the cultivation of a movie's legacy and identity within popular culture .

In the CONFERENCE_REVIEW database, reviewers provide two types of written comments: one for the review committee and the other as feedback for the authors . This dual feedback mechanism enhances the review process by allowing reviewers to communicate candid observations and recommendations to the committee, which may not be suitable for author feedback. Simultaneously, it enriches the authors' understanding and chances for improvement by giving them targeted insights into strengths and weaknesses without exposing sensitive feedback intended for internal deliberations .

In the flight database schema, the flight and passenger entities are interconnected through the 'Booking' entity, which captures the M:N relationship between these entities . The implication of this design is that it facilitates detailed tracking of each passenger's bookings, including the specifics of each flight booking such as seat number, flight schedule, and booking status . This approach not only improves the database's flexibility in querying and reporting but also enhances accuracy in managing passenger flight history and transactions .

In the CONFERENCE_REVIEW database, authors are uniquely identified by their email IDs, while reviewers are identified by their email addresses as well . This method of unique identification ensures that each author and reviewer can be distinctly recognized in the database, preventing any ambiguity or duplication. Using email addresses as unique identifiers leverages their inherent uniqueness, enhancing data integrity by tying records to distinct, non-replicable IDs .

Having multiple authors for a paper in the CONFERENCE_REVIEW database offers collaborative credibility and enriches the research's depth . Designating one author as the contact author streamlines communication between the review committee and the paper's authors, thereby centralizing correspondence and clarifying responsibility for responding to reviewer feedback and revision requests. This setup minimizes confusion and enhances process efficiency while managing author-related operations within the database .

In the MOVIE database, movies are uniquely identified by their title and year of release, while actors are identified by their name and date of birth . This dual-key system supports comprehensive data management by ensuring each record is distinctly identifiable while avoiding ambiguity, even when movies share titles or actors share names. It also facilitates efficient queries, data integrity, and robust cross-referencing capabilities, allowing accurate long-term tracking and retrieval of filmography data and actor participation .

The paper reviews in the CONFERENCE_REVIEW database are evaluated based on four key criteria: technical merit, readability, originality, and relevance to the conference, each rated on a scale of 1 to 10 . These criteria help reviewers objectively assess the quality and pertinence of the submissions, contributing significantly to informed decision-making during the paper selection process by providing a structured framework for evaluation . The inclusion of an overall recommendation further refines the selection process by encapsulating the reviewer's holistic judgment .

Using email addresses as primary keys in the flight database for passengers presents benefits such as leveraging the uniqueness of email addresses, which simplifies record identification and data entry processes . However, challenges include managing changes in email addresses and ensuring continuous accuracy, given the personal nature and potential turnover of emails. These can impact system reliability if not handled properly, leading to possible data inconsistencies or orphaned records after email changes. Efficiently addressing these challenges requires robust update procedures and validation mechanisms to maintain system reliability and integrity .

In the MOVIE database, constraints are introduced by allowing each movie to be classified under one or more predefined genres, and actors to be identified by specific roles . These constraints ensure standardized data entry and retrieval processes. The justification for genre constraints lies in maintaining a consistent and searchable category system for movie classification. Role constraints ensure that character assignments are systematically captured, which aids in data integrity, allowing accurate representation of filmography records .

Sample Questions (ER Diagram) Question 1 Consider a CONFERENCE_REVIEW database in which researchers submit their research p
 A passenger can book a seat on a flight.  An Airplane is uniquely identified by its RegistrationNumber, so we use this

You might also like