Scribd
Upload
6 views4 pages

Database Group Course work. Normalization Assignment

The document discusses normalization in database management, emphasizing its role in organizing data to reduce redundancy and dependency, thereby improving data quality and efficiency. It outlines the processes involved in achieving different normal forms (1NF, 2NF, 3NF) and the significance of functional dependencies in this context. Additionally, it highlights potential challenges and considerations when implementing normalization in database design.

Uploaded by

nabatanzi.gorret
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
6 views4 pages

Database Group Course work. Normalization Assignment

The document discusses normalization in database management, emphasizing its role in organizing data to reduce redundancy and dependency, thereby improving data quality and efficiency. It outlines the processes involved in achieving different normal forms (1NF, 2NF, 3NF) and the significance of functional dependencies in this context. Additionally, it highlights potential challenges and considerations when implementing normalization in database design.

Uploaded by

nabatanzi.gorret
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/ 4

UGANDA TECHNOLOGY AND MANAGEMENT UNIVERSITY

SCHOOL OF COMPUTING AND ENGINEERING

BACHELOR OF SCIENCE IN COMPUTER SCIENCE

IS300 – DATABASE MANAGEMENT SYSTEM

MR. BRUNO SSEKIWERE


[email protected]

GROUP MEMBERS
ABIGABA ROLAND REG NO: SEP22/BCS/1422U
TUMUKUNDE MARKJOE REG NO: SEP22/BCS/1647U

NORMALIZATION GROUP COURSE WORK


DAEDLINE: 30/11/2023
14.1
Normalization is a process of organizing data in a database to reduce redundancy and dependency. It
helps to minimize data duplication, insertion, update, and deletion anomalies.
14.2
Normalization can be used in various ways to support database design. It helps to eliminate data
redundancy, dependency, and anomalies.
Normalization can be used to create a more efficient database structure, improve data quality and
simplify the query process.
It can also help to reduce storage space and ensure that queries on a database run as fast as possible.
14.3
Normalization eradicates update anomalies from a relation by breaking down a large table into smaller
tables. This process ensures that each table has a single purpose and that each attribute is atomic. By
doing so, it eliminates data redundancy and dependency, which in turn eliminates update anomalies.
14.4
Functional dependency is a relationship between two sets of attributes in a database, where one set (the
determinant) determines the values of the other set (the dependent).
14.5
The following are the main characteristics of functional dependencies that are used for
normalization:

• A functional dependency is a relationship between two sets of attributes in a database.


• It occurs when the value of one attribute determines the value of another attribute.
• It is denoted as X → Y, where X is called Determinant, and Y is called the Dependent.
• A determinant is a set of attributes that uniquely determines the value of another attribute.
• A dependent is an attribute whose value is determined by another attribute.
14.6
A database designer identifies the set of functional dependencies associated with a relation by analyzing
the data and identifying the relationships between the attributes.
14.7
Factors that influence the choice of normalization or ER modelling when designing a database include
the complexity of the data, the size of the database, the number of users, the type of application and the
performance requirements.
14.8
Normalization is a bottom-up design approach that eliminates data redundancy and dependency by
breaking down a large table into smaller tables. ER modelling is a top-down design approach that starts
with the overall structure of the database and works down to the smallest components.
14.9
There are two approaches to converting an UNF table to 1NF relation(s): remove the repeating groups
by creating a new relation for each group and including a copy of the original key attribute(s) in each
new relation, or remove the repeating groups by entering appropriate data in the empty columns of rows
containing the repeating data.
14.10
Partial dependency occurs when a non-key attribute is functionally dependent on only a part of the
primary key. Removing partial dependencies from 1NF relations results in 2NF relations.
14.11
Transitive dependency occurs when a non-key attribute is functionally dependent on another non-key
attribute. 3NF requires that all non-key attributes be dependent on the primary key, not on other non-
key attributes. For example, consider a relation that contains the attributes {A, B, C, D}, where A is the
primary key and B → C and C → D. In this case, D is transitively dependent on A through B and C. To
normalize this relation to 3NF, we need to create two relations: {A, B, C} and {C, D}
14.12
2NF and 3NF based on primary keys differ from the general definitions. The former are based only on
the primary key of a relation, while the latter are based on all candidate keys of a relation. Every non-
key attribute must be directly dependent on the primary key.
Example,
consider a relation {A, B, C, D}, where A is the primary key and B → C and C → D. This relation is
in 2NF and 3NF according to the general definition, but not according to the definition based on primary
keys because B is not a candidate key. To normalize this relation to 2NF based on primary keys, we
need to create two relations: {A, B, C} and {C, D}. Similarly, to normalize this relation to 3NF based
on primary keys, we need to create three relations: {A, B}, {B, C}, and {C, D}.
14.13
Before carrying out the normalization process, it is important to be aware of the following basic issues:

• Normalization can be a time-consuming process that requires careful planning and execution.
• It can lead to an increase in the number of tables in a database, which can make queries more
complex and time-consuming.
• Normalization may lead to a loss of data if not done correctly.
• Normalization can lead to a decrease in performance if not done correctly.
• Normalization can lead to an increase in disk space usage due to the creation of additional tables.
• Normalization can lead to a decrease in flexibility due to the creation of additional tables.
• Normalization can lead to an increase in the complexity of the database design, which can make it
more difficult to maintain and modify the database.
14.14
a) The functional dependencies in the form are:
Patient Number -> Full Name, Ward Number, Bed Number, Ward Name
Drug Number -> Name, Description, Dosage, Method of Admin, Units per Day, Start Date, Finish Date
(b) To normalize the attributes to 3NF:
Remove partial dependencies by creating new tables for each set of related data.
Patient Table: Patient Number (PK), Full Name, Bed Number
Ward Table: Ward Number (PK), Ward Name
Medication Table: Drug Number (PK), Name, Description
Prescription Table: Prescription ID (PK), Patient Number (FK), Drug Number (FK), Dosage, Method
of Admin, Units per Day, Start Date and Finish Date
c) Keys:
Primary keys:
Patient Table – Patient Number;
Ward Table – Ward number;
Medication Table – Drug number;
Prescription table – Prescription ID.
Foreign keys in the prescription table are Patient number and Drug number linking to the patient and
medication tables respectively.

You might also like