La3 1

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 3

DFC 20203 DATABASE DESIGN

LAB ACTIVITY 3: Entity Relationship (ER) Model &


Normalization – PART 1
Duration: 4 Hours

Learning Outcomes
This activity encompasses activities 3A, 3B, and 3C.

At the end of this activity session, you should be able to:


1. Understand normalization in database.
2. Understand Functional and Transitive dependencies
3. Construct normalization from 1NF until 3NF.

Activity 3A
Activity Outcome : Understand normalization in database.

Fill in the appropriate terms for normalization in database based on the following statements.

1. ______________________ is a 2 dimensional table with columns and row.

2. 2 problems in relational data model are _______________________________ and


______________________________________.

3. 3 types of anomalies are _________________________, _________

______________ and ______________________________.

4. ___________________________ is a process for assigning into a table and reduces


data redundancy and helps eliminate the data anomalies.

5. ________________________ is a table that contains one or more repeating groups.

6. 3 level of normalization are _______________________, _______________________


and _____________________________.

7. ________________________ is a relation in which based on the concept of transitive


dependency.

8. In the _____________ normal form, a composite attribute is converted to individual


attribute

Page 24 of 57
DFC 20203 DATABASE DESIGN

Activity 3B
Activity Outcome : Understand functional and transitive
dependencies in database normalization.

Consider the following relation definition and sample data:

PROJECT
ProjectID EmployeeName EmployeeSalary
100A Jamilah 1500
100A Samad 2000
100B Samad 2000
200A Jamilah 1500
200B Jamilah 1500
200C Affendi 2500
200C Samad 2000
200D Affendi 2500

PROJECT (ProjectID, EmployeeName, EmployeeSalary)

Where ProjectID is the name of a work project.


EmployeeName is the name of an employee who works on that project.
EmployeeSalary is the salary of the employee whose name is EmployeeName.

Assuming that all of the functional dependencies and constraints are apparent in this data,
which of the following statements is true?

 ProjectID EmployeeName
 ProjectID_ EmployeeSalary
 (ProjectID, EmployeeName) EmployeeSalary
 EmployeeName EmployeeSalary
 EmployeeSalary ProjectID
 EmployeeSalary (ProjectID, EmployeeName)

Answer these questions:

a) What is a key for PROJECT?


b) Are all non-key attributes dependent on the entire key?
c) In what normal form is PROJECT?
d) Describe two modification anomalies from which PROJECT suffers.

Page 25 of 57
DFC 20203 DATABASE DESIGN

Activity 3C

Activity Outcome: Construct normalization process (UNF – 3NF) based on the given
scenario.

SCENARIO

Success Software Co., a software contract and consultancy firm maintains details of all
the various projects in which its employees are currently involved. These details comprise:
 Employee Number
 Employee Name
 Date of Birth
 Department Code
 Department Name
 Project Code
 Project Description
 Project Supervisor
Assume the following:
 Each employee number is unique.
 Each department has a single department code.
 Each project has a single code and supervisor.
 Each employee may work on one or more projects.
 Employee names need not necessarily be unique.
 Project Code, Project Description and Project Supervisor are repeating fields.

Page 26 of 57

You might also like