Scribd
Upload
14 views1 page

DBF161 Activity 1 - ERD

The document outlines a series of scenarios for which Entity Relationship Diagrams (ERDs) need to be created, detailing relationships between entities such as EMPLOYEE, STORE, CUSTOMER, PAYMENT, STUDENT, SUBJECT, and others. Each scenario includes specific business rules that guide the creation of the ERDs, emphasizing the need to resolve many-to-many relationships. Additionally, it specifies attributes and cardinality for the entities involved in each scenario.

Uploaded by

soyap84426
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
14 views1 page

DBF161 Activity 1 - ERD

The document outlines a series of scenarios for which Entity Relationship Diagrams (ERDs) need to be created, detailing relationships between entities such as EMPLOYEE, STORE, CUSTOMER, PAYMENT, STUDENT, SUBJECT, and others. Each scenario includes specific business rules that guide the creation of the ERDs, emphasizing the need to resolve many-to-many relationships. Additionally, it specifies attributes and cardinality for the entities involved in each scenario.

Uploaded by

soyap84426
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/ 1

DBF161 - Activity 1

ERD Practice Questions

Create an Entity Relationship Diagram (ERD) for each of the scenarios below. Add some suitable
attributes.

1. An EMPLOYEE manages one STORE and each STORE is managed by one EMPLOYEE.

2. A customer can make many payments, but each payment is made by only one customer.

3. A student studies many subjects and a subject is studied by many students.

4. Given the following business rules, create the appropriate ERD.


a. A company operates many departments.
b. Each department employs one or more employees.
c. Each of the employees may or may not have one or more dependants.
d. Each employee may or may not have an employment history.

5. A hospital patient receives medications that have been ordered by a particular doctor. Because
the patient often receives several medications per day, there is a 1:M relationship between
PATIENT and ORDER. Similarly, each order can include several medications, creating a 1:M
relationship between ORDER and MEDICATION.

6. Given the following business rules, create an ERD.


a. A musician makes at least one recording, but may over a period of time make many
recordings.
b. One recording consists if at least three or more tracks.
c. A track can appear on more than one recording.

Resolve any many-to-many relationships.

7. A manufacturing company produces products. Product information stored is product name, id,
quantity on hand. These products are made up of many components. Each component can be
supplied by one or more suppliers. Component information kept is component id, name,
description, suppliers who supply them, and which products they are used in.
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.
Resolve any many-to-many relationships.
Assumptions:
 A supplier can exist without providing components.
 A component does not have to be associated with a supplier.
 A component does not have to be associated with product. Not all components are used in
products.
 A product cannot exist without components.

You might also like