WGU C170 VHT1-0514 IT-MANAGEMENT OF DATA APPLICATION

C170, VHT1-0514 IT-MANAGEMENT OF DATA APPLICATION 1




WGU C170, VHT1-0514 IT-MANAGEMENT OF DATA APPLICATION




C170, VHT1-0514 IT-Management of Data Application

XXXXXXXXX

Western Governors University

WGU Student ID

, C170, VHT1-0514 IT-MANAGEMENT OF DATA APPLICATION 2

A.1.a 1st Normal form




Primary Key for the table is DonutInvoiceID.


I chose to create a 1st Normal Form table by selecting a primary key of the

DonutInvoiceID. Every field in the 1st form table can be tied to the DonutInvoiceID column.

During the 1st form normalization step I insured that each column possessed atomic single values

and there was no repeating data in each row. 1st form normalization however has left much of

the data redundant throughout the entire table. All non-calculated data from the Invoice Slip has

figured into a column within the 1st form normalization table above.



A.1.b 2nd Normal form




Primary Key is DonutInvoiceID

, C170, VHT1-0514 IT-MANAGEMENT OF DATA APPLICATION 3




Primary Key is a composite of DonutInvoiceID and DonutID




Primary Key is DonutID

During the 2nd normilization step I elected to create three tables. Table one is the Invoice

table. Every column in it is functionaly depenant upon the DonutInvoiceID column. The second

table is the InvoiceLine table. It has a composite key of DonutInvoiceID and DonutID and

contains the intersection data bewtween the Invoice table and the Donut table as quanity. The

third table created is the Donut table and it primary key is DonutID. All columns are functionaly

dependant upon the DonutID.



A.1.c 3rd Normal form




Primary Key is DonutInvoice ID