Relational Database Design Report 2022

Running head: Relational Database Design
RELATIONAL DATABASE DESIGN
Name of the Student
Name of the University
Author Note

Relational Database Design1
Table of Contents
Introduction:...............................................................................................................................2
Discussion:.................................................................................................................................2
Task 1:....................................................................................................................................2
Task 2:....................................................................................................................................5
Conclusion:..............................................................................................................................11
Bibliography:............................................................................................................................12

Relational Database Design2
Introduction:
After analyzing the provided documentation, every entity can be identified. This
report provides the step by step process of normalization. After completing the normalization
process an ERD can be produced. Every entity and its attributes and keys can be identified in
the ERD. After identified the ERD a data dictionary is attached in this report. This data
dictionary provides every attribute detail that is identified in the ERD.
Discussion:
Task 1:
Before starting the normalization process every entities and attributes must be in UNF
structure. The UNF structure is providing below.
Customer (Customer_number, Customer_Name, Salesperson_Number, Salesperson_Name,
Salesperson_Area, Delivery_Company_Number, Delivery_Company_Location,
product_number, product_description, quantity, price, supplier_number, supplier_name
invoice_number, Shipping_number)
Now, most of the important attributes are identified but it is not properly normalized
in order to organize the data normalization is required (Amin et al. 2019). Normalization is a
special type of technique to organize every data with the database. Above entity and
attributes only dependent on one key and data is redundant. Decomposing table in various
form is the best way to eliminate the data redundancy problem (Eessaar. 2016). There are
many rules are available such as 1NF, 2NF, 3NF BCNF and fourth normal form. In this
report, we are going to the decomposing table in 1NF, 2NF and 3NF only.
1NF 2NF 3NF
Identifying entities and Identifying entities with partial No key dependencies

Relational Database Design3
attributes in 1NF form dependencies
(Product)
product_number,
product_description, quantity,
price, supplier_number,
supplier_name
invoice_number, Date
Shipping_number
(Customer)
Customer_number,
product_number,
Customer_Name,
Salesperson_Number,
Salesperson_Name,
Salesperson_Area,
Delivery_Company_Number,
Delivery_Company_Location,
(Product)
product_number,
product_description, quantity,
price,
(supplier)
supplier_number,
product_number,
supplier_name
(Customer)
Customer_number,
invoice_number,
Shipping_number
Salesperson_Number,
Date
Customer_Name,
Salesperson_Name,
Salesperson_Area,
Delivery_Company_Number,
Delivery_Company_Location
(Customer)
Customer_number,
Customer_Name,
Address,
Contact_number
(Salesperson)
Salesperson_Number,
Salesperson_Name,
Salesperson_Area,
Contact_Number
(Delivery_Company)
Delivery_Company_Number,
Delivery_Company_Location,
Contact_Number
(supplier)
supplier_number,
supplier_name
contact_number
(Product)