0% found this document useful (0 votes)
196 views4 pages

Assignment 2 Unit 1

This document contains questions about designing entity-relationship diagrams for several databases: a conference review database, movie database, mail order database, university database, and bank database. It asks to identify entity types, weak entity types, relationship types, and constraints in the diagrams. It also asks how many tables would be required to represent an entity-relationship diagram in a relational database model.

Uploaded by

trippic2396
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
196 views4 pages

Assignment 2 Unit 1

This document contains questions about designing entity-relationship diagrams for several databases: a conference review database, movie database, mail order database, university database, and bank database. It asks to identify entity types, weak entity types, relationship types, and constraints in the diagrams. It also asks how many tables would be required to represent an entity-relationship diagram in a relational database model.

Uploaded by

trippic2396
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

GALGOTIAS UNIVERSITY

Greater Noida, Uttar Pradesh


Assignment -2

Course: Database Management System (E1PA104B_DBMS)

Department: School of Computer Application & Technology

Program: MCA First


Semester: 2023-24

Q1. 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).
Design an entity–relationship diagram for the CONFERENCE_REVIEW database.

Q2. 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.
■ Directors are also identified by name and date of birth and direct one or more movies. It is
possible for a director to act in a movie (including one that he or she may also direct).
■ Production companies are identified by name and each has an address. A production company
produces one or more movies.
Design an entity–relationship diagram for the movie database.
Q3. Consider a MAIL_ORDER database in which employees take orders for parts from
customers. The data requirements are summarized as follows:
■ The mail order company has employees, each identified by a unique employee number, first
and last name, and Zip Code.
■ Each customer of the company is identified by a unique customer number, first and last name,
and Zip Code.
■ Each part sold by the company is identified by a unique part number, a part name, price, and
quantity in stock.
■ Each order placed by a customer is taken by an employee and is given a unique order number.
Each order contains specified quantities of one or more parts. Each order has a date of receipt as
well as an expected ship date. The actual ship date is also recorded.
Design an entity–relationship diagram for the mail order database.
Q4. Consider the UNIVERSITY database described in below.
a. During a particular semester and year, only one section can use a particular classroom at a
particular DaysTime value.
b. During a particular semester and year, an instructor can teach only one section at a particular
DaysTime value.
c. During a particular semester and year, the section numbers for sections offered for the same
course must all be different.
Q5. Consider the ER diagram shown in Figure 3.22 for part of a BANK database. Each bank can
have multiple branches, and each branch can have multiple accounts and loans.
a. List the strong (nonweak) entity types in the ER diagram.
b. Is there a weak entity type? If so, give its name, partial key, and identifying relationship.
c. What constraints do the partial key and the identifying relationship of the weak entity type
specify in this diagram?
d. List the names of all relationship types, and specify the (min, max) constraint on each
participation of an entity type in a relationship type. Justify your choices.

Q-5) Find the minimum number of tables required to represent the given ER diagram in
relational model.

You might also like