0% found this document useful (0 votes)
70 views3 pages

Database Management Systems Chapter 11 Qns

The document discusses entity relationship (ER) modeling and database design. It provides several examples of entities, relationships, and attributes to model in ER diagrams. It also asks questions about: [1] identifying entity types, relationship types, and attributes for different scenarios; [2] representing relationships, cardinalities, and constraints; [3] distinguishing between strong and weak entities; and [4] avoiding traps in ER modeling. The overall goal is to practice designing and building ER diagrams to model real-world data requirements and relationships between entities.
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
0% found this document useful (0 votes)
70 views3 pages

Database Management Systems Chapter 11 Qns

The document discusses entity relationship (ER) modeling and database design. It provides several examples of entities, relationships, and attributes to model in ER diagrams. It also asks questions about: [1] identifying entity types, relationship types, and attributes for different scenarios; [2] representing relationships, cardinalities, and constraints; [3] distinguishing between strong and weak entities; and [4] avoiding traps in ER modeling. The overall goal is to practice designing and building ER diagrams to model real-world data requirements and relationships between entities.
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

Database Management Systems.

BIS 3103: Review questions

Note: If you can not try out all these questions, try to at least attempt question 3.

Entity Relationship modelling.

1) Create an ER Diagram for each of the following descriptions:

a) Each company operates four Departments, and each department belongs to


one company.
b) Each Department in part (a) employs one or more employees, and each
employee works for one Department.
c) Each of the employees in part (b) may or may not have one or more
dependants, and each dependant belongs to one employee.
d) Each employee in part (c) may or may not have an employment history.
e) Represent all the ER diagrams described in (a),(b),(c)and (d) as a single ER
Diagram

2) You are required to create a conceptual data model of the data requirements for a
company that specializes in IT training. The Company has 30 instructors and can
handle up to 100 trainees per training Session. The Company offers five advanced
Technology Courses, each of which is taught by a teaching team of two or more
Instructors. Each instructor is assigned to a maximum of two teaching teams or may
be assigned to do research. Each trainee trainee undertakes one advanced
technology course per training session.

a) Identify the main entity types for the company.


b) Identify the main relationship types and specify the Multiplicity for each
relationship. State any assumptions you may make about the data.
c) Using your data in (a) and (b), draw a single ER diagram to represent the data
requirements for the company.

3) Read the following Case study, which describes the data requirements for a video
rental Company. The Video rental company has several branches throughout the
USA. The data held on each branch is the branch address made up of street, city,
state, and zip code, and a telephone number. Each branch is given a branch number,
which is unique throughout the company. Each branch is allocated staff, which
includes a manager. The manager is responsible for the day-to-day running of a given
branch. The data held on a member of staff is his or her name, position, and salary.
Each member of staff is given a staff number, which is unique throughout the
company. Each branch has a stock of videos. The data held on a video is a catalog
number, video number, title, category, daily rental cost, status, and names of the
main actor, and the director. The catalog number uniquely identifies each video.
However, in most cases, there are several copies of each video at a branch, and the
individual copies are identified using the video number. A video is given a category
such as action, Adult, Children, drama, Horror, or Sci-Fi. The status indicates whether
a specific copy of a video is available for rent. Before hiring a video from the
company, a customer must first register as a member of a local branch. The data
held on a member is the first and last name, address, and the date that the member
registered at a branch. Each member is given a member number, which is unique
throughout all branches of the company. Once registered, a member is free to rent
videos, up to a maximum of ten at any one time. The data held on each video rented
is the rental number, the full name and number of the member, the video number,
title, and daily rental, and the dates the video is rented out and returned. The rental
number is unique throughout the company.

a) Identify the main Entity types of the video rental company.


b) Identify the main relationship types identified between the entity types
described in (a) and represent each relationship as an ER diagram.
c) Determine the multiplicity constraints for each relationship described in (b).
Represent the multiplicity for each relationship in the ER diagrams created in (b).
d) Identify attributes and associate them with entity or relationship types.
Represent each attribute in the ER diagrams created in (c).
e) Determine Candidate and Primary key attributes for each (strong) entity type.
f) Using your answer in (a) to (e), attempt to represent the data requirements of
the Video rental Company as a single ER diagram. State any assumptions
necessary to support your design.

4)
i. Describe what entity types represent in an ER model and provide examples of
entities with a physical or conceptual existence.
ii. Describe what relationship types represent in an ER model and provide
examples of in each known relationship degree. That is, binary, ternary and
quaternary relationships.
iii. Describe what attributes represent in an ER model and provide examples of
simple, composite, multi-valued, and derived attributes.
iv. Describe what the multiplicity constraints represent for a relationship type.
v. What are enterprise constraints and how does multiplicity model these
constraints?
vi. How does multiplicity represent both cardinality and participation constraints
on a relationship type?
vii. Provide an example of a relationship type with attributes.
viii. Describe how strong and weak entity types differ and provide an example of
each.
ix. Describe how fan and Chasm traps can occur in an ER model and how they
can be resolved.

After deriving the conceptual database design (EERDs and or EERDs), can you derive
the relevant relations? I hope you now can.

You might also like