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 routing 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.

Construct an E-R diagram for a hospital with a set of patients and a set of medical doctors. Associate with each patient a log of the various tests and examinations conducted.

Consider the following set of requirements for a UNIVERSITY database that isused to keep track of students’ transcripts.

The university keeps track of each student’s name, student number, Social Security number, current address and phone number, permanent address and phone number, birth date, sex, class (freshman, sophomore, ..., graduate), major department, minor department (if any), and degree program (B.A., B.S., ..., Ph.D.). Some user applications need to refer to the city, state, and ZIP Code of the student’s permanent address and to the student’s last name. Both Social Security number and student number have unique values for each student.

Each department is described by a name, department code, office number, office phone number, and college. Both name and code have unique values for each department.

Each course has a course name, description, course number, number of semester hours, level, and offering department. The value of the course number is unique for each course.

Each section has an instructor, semester, year, course, and section number. The section number distinguishes sections of the same course that are taught during the same semester/year; its values are 1, 2, 3, ..., up to the number of sections taught during each semester.

A grade report has a student, section, letter grade, and numeric grade (0, 1, 2, 3, or 4).

Design an ER schema for this application, and draw an ER diagram for the schema. Specify key attributes of each entity type, and structural constraints on each relationship type. Note any unspecified requirements, and make appropriate assumptions to make the specification complete.

A manufacturing company produces products. The following product information is stored: product name, product ID and quantity on hand. These products are made up of many components. Each component can be supplied by one or more suppliers. The following component information is kept: component ID, name, description, suppliers who supply them, and products in which they are used. Use Figure B.1 for this exercise.

Create an ERD to show how you would track this information.

Show entity names, primary keys, attributes for each entity, relationships between the entities and cardinality.

Create an ERD for a car dealership. The dealership sells both new and used cars, and it operates a service facility (see Figure B.2). Base your design on the following business rules:

A salesperson may sell many cars, but each car is sold by only one salesperson.

A customer may buy many cars, but each car is bought by only one customer.

A salesperson writes a single invoice for each car he or she sells.

A customer gets an invoice for each car he or she buys.

A customer may come in just to have his or her car serviced; that is, a customer need not buy a car to be classified as a customer.

When a customer takes one or more cars in for repair or service, one service ticket is written for each car.

The car dealership maintains a service history for each of the cars serviced.

The service records are referenced by the car’s serial number.

A car brought in for service can be worked on by many mechanics, and each mechanic may work on many cars.

A car that is serviced may or may not need parts (e.g., adjusting a carburetor or cleaning a fuel injector nozzle does not require providing new parts).

Question

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 routing 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.
1. Construct an E-R diagram for a hospital with a set of patients and a set of medical doctors. Associate with each patient a log of the various tests and examinations conducted.
2. Consider the following set of requirements for a UNIVERSITY database that isused to keep track of students’ transcripts.
3. The university keeps track of each student’s name, student number, Social Security number, current address and phone number, permanent address and phone number, birth date, sex, class (freshman, sophomore, ..., graduate), major department, minor department (if any), and degree program (B.A., B.S., ..., Ph.D.). Some user applications need to refer to the city, state, and ZIP Code of the student’s permanent address and to the student’s last name. Both Social Security number and student number have unique values for each student.
4. Each department is described by a name, department code, office number, office phone number, and college. Both name and code have unique values for each department.
5. Each course has a course name, description, course number, number of semester hours, level, and offering department. The value of the course number is unique for each course.
6. Each section has an instructor, semester, year, course, and section number. The section number distinguishes sections of the same course that are taught during the same semester/year; its values are 1, 2, 3, ..., up to the number of sections taught during each semester.
7. A grade report has a student, section, letter grade, and numeric grade (0, 1, 2, 3, or 4).
Design an ER schema for this application, and draw an ER diagram for the schema. Specify key attributes of each entity type, and structural constraints on each relationship type. Note any unspecified requirements, and make appropriate assumptions to make the specification complete.
1. A manufacturing company produces products. The following product information is stored: product name, product ID and quantity on hand. These products are made up of many components. Each component can be supplied by one or more suppliers. The following component information is kept: component ID, name, description, suppliers who supply them, and products in which they are used. Use Figure B.1 for this exercise.
Create an ERD to show how you would track this information.

Show entity names, primary keys, attributes for each entity, relationships between the entities and cardinality.
1. Create an ERD for a car dealership. The dealership sells both new and used cars, and it operates a service facility (see Figure B.2). Base your design on the following business rules:
A salesperson may sell many cars, but each car is sold by only one salesperson.

A customer may buy many cars, but each car is bought by only one customer.

A salesperson writes a single invoice for each car he or she sells.

A customer gets an invoice for each car he or she buys.

A customer may come in just to have his or her car serviced; that is, a customer need not buy a car to be classified as a customer.

When a customer takes one or more cars in for repair or service, one service ticket is written for each car.

The car dealership maintains a service history for each of the cars serviced.

The service records are referenced by the car’s serial number.

A car brought in for service can be worked on by many mechanics, and each mechanic may work on many cars.

A car that is serviced may or may not need parts (e.g., adjusting a carburetor or cleaning a fuel injector nozzle does not require providing new parts).

Accepted Answer

Objective: An entity-relationship diagram should be designed to maintain a database for an airline.…