Scribd
Upload
145 views3 pages

ERD Exercises

The document describes two exercises involving ER diagrams. Exercise 1 involves analyzing an ER diagram of a bank database that shows banks have branches, branches have accounts and loans, and accounts and loans are weak entities that depend on branches. Exercise 2 involves designing an ER diagram for a conference review database that would track authors, papers, reviewers, and the review process.

Uploaded by

saddie56451
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
145 views3 pages

ERD Exercises

The document describes two exercises involving ER diagrams. Exercise 1 involves analyzing an ER diagram of a bank database that shows banks have branches, branches have accounts and loans, and accounts and loans are weak entities that depend on branches. Exercise 2 involves designing an ER diagram for a conference review database that would track authors, papers, reviewers, and the review process.

Uploaded by

saddie56451
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
You are on page 1/ 3

Exercise 1

Consider the ER diagram shown in Figure 7.21 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.
e. List concisely the user requirements that led to this ER schema design.
f. Suppose that every customer must have at least one account but is

1
restricted to at most two loans at a time, and that a bank branch cannot
have more than 1,000 loans. How does this show up on the (min, max)
constraints?

Exercise 2
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

2
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 and build the design using a data
modeling tool.

You might also like