Normalization Week 4 Dbm 380

Normalization

Tyrell Frater

DBM/380

January 15 2015

Travin Hill

Normalization

Normalization is used to bring a certain project to a point of understanding. In the Internet Technology field it is used to break down and describe a file in the appropriate tables they need to be formatted in. This breakdown is what is going to form the database for the project. There can be several steps in this process that are known as normal forms. To create this process, with our park project we be utilizing Three forms of normalization forms. In the first form, in our first form we will have no repeating attributes so in our DSD that is listed below for the different categories such as employee, park, ranger, and visitor we will eliminate any rampancy for the information that will be entered. Then in our second normal form we will remove and make a separate table for any attribute that is not primarily dependent on the UID. So looking at our DSD we will separate the park for the other attributes because it is a designation on where the employees or rangers will go. Then final in our third normalization form we will separate the employee ranger and visitor which is all dependent on the park they will be assigned to. This is because no attributes should depend on any other attributes but the Uid. It is important to designate what is the uid from what is not. When normalizing a table it is always important to understand and break down of what is giving the diagram flow. In conclusion Boyce-cod Normal Form or otherwise known as (BNCF) has w working relation if the main or determinate key is a candidate key. BNCF is not 3nf but at a glance can seem very similar. The difference is they deal with dependencies with the main or primary key functions. Most relationships that are 3nf are bncf as well. If 3nf is made up of more than one field from the primary key, that’s when they will be different. A you reach 3NF or BNCF that’s when a database is said to be normalized....