Bule Hora University

Collage of Informatics
Department of Information Systems
Course: Fundumentals of Database Systems

By Tsegaye Desiyo

1
 CHAPTER FOUR

Logical database design

2
 4. LOGICAL DATABASE DESIGN

Logical design is the process of constructing a model of the information used in an

enterprise based on a specific data model (e.g. relational, hierarchical or network or
object), but independent of a particular DBMS and other physical considerations.
Normalization process:
 Discover new entities
 Revise attributes

The Logical database design is concerned with the what and the Physical database design
concerned with the how.

 Logical Database Design: We must choose a DBMS to implement our database design,
and convert the conceptual database design into a database schema in the data model of
the chosen DBMS.

3
Database Normalization is a technique of organizing the data in the database. This
includes creating tables and establishing relationships between those tables according to
rules designed both to protect the data and to make the database more flexible by
eliminating two factors: redundancy and inconsistent dependency.

 Redundant data wastes disk space and creates maintenance problems. If data that
exists in more than one place must be changed, the data must be changed in exactly the
same way in all locations.

 Inconsistent dependencies can make data difficult to access; the path to find the data
may be missing.

Normalization is a systematic approach of decomposing tables to eliminate data

redundancy and undesirable characteristics like Insertion, Update and Deletion
Anomalies. It is a multi-step process that puts data into tabular form by removing
duplicated data from the relation tables.

4
 1. Problems Without Normalization
Without Normalization, it becomes difficult to handle and update the database,
without facing data loss. Insertion, Updating and Deletion Anomalies are very
frequent if Database is not Normalized. The type of problems that could occur in
insufficiently normalized table is called update anomalies.

1. Insertion Anomalies: It is the problem of adding a new row or rows in a table for
one or the other reason. Difficulties inserting data into a relation. An "insertion
anomaly" is a failure to place information about a new database entry into all the
places in the database where information about that new entry needs to be stored. In
a properly normalized database, information about a new entry needs to be inserted
into only one place in the database; in an inadequately normalized database,
information about a new entry may need to be inserted into
more than one place and, human fallibility being what it is, some of the needed
additional insertions may be missed.

5
1. deletion Anomalies: It is the problem of deleting a row or rows in a table for
one or the other reason.
 A "deletion anomaly" is a failure to remove information about an existing
database entry when it is time to remove that entry. In a properly normalized
database, information about an old, to-be-gotten-rid-of entry needs to be deleted
from only one place in the database; in an inadequately normalized database,
information about that old entry may need to be deleted from more than one place,
and, human fallibility being what it is, some of the needed additional deletions may
be missed.
1. Modification Anomalies: It is the problem of updating a row or rows in a table
for one or the other reason. Difficulties modifying data in a relation. A modification
of a database involves changing some value of the attribute of a table. In a properly
normalized database table, whatever information is modified by the user, the
change will be affected and used accordingly.
6
7
8
9
10
11
13
14
15
18
20
20
21
21
 Department

Course Module Lecturer

22
unNormalized
1)Repeat Group
2)PK is not defined
FrstNormalForm
No repeating group
- PK defined
-Test partial dependency
SecondNormalForm
ThridNormalForm No repeating group
-No repeating -PK defined
group -No partial
-PK defined dependency
-No partial -Test transitive
dependency dependency
-No transitive
dependency
QUIZ 2:
Consider the following Employee table with EmployeeID, Employee Name and
Skills. Transform it into First Normal Form (1NF), Second Normal Form (2NF),
and Third Normal Form (3NF). (5 Points).

Note; - Do all necessary steps to get full points!

Original Employee Table:
EmployeeID EmployeeName Skills

1 Abebe Kebede Java, SQL

2 Isayas Kadir Python, C++

3 Boba Amaan Java, Python

32