wgu c170 vht task 1 it management of data application
Written for
VHT Task
All documents for this subject (1)
Seller
Follow
LeCrae
Reviews received
Content preview
IT-Management of Data Application
(C170) VHT Task 1
A. Normalization
a. First Normal Form
In order to place the sales order form into first normal form I took all the fields from the form and made
an attribute for each field. I then took away the attributes that can be calculated. I then marked the
primary keys that would make each row in a table of data unique when they are combined into a
composite primary key.
b. Second Normal Form
In order to take the database into second normal form I made 2 additional tables. One table for each line
item on the order and another for the information about the donut. All the attributes under order are
only dependent on the OrderID and can only be given one value when associated with an OrderID. Since
there can be more than one DonutID associated with an OrderID the donut information needed to be
separated into its own table. This was also done so that the donut information can be stored once and
used many times. Since there can be many different donuts ordered on each order that also needed to
be separated into another table. This makes it so that all non-key attributes are functionally dependent
on the entire primary key in each table.
c. Third Normal Form
In order to take the database into third normal form I separated out the customer information into its
own table. I did this so that the customer information can be stored once and used many times. It was
also separated out because it can exist without needing to be associated to an order.
, B. Entity-Relationship Diagram
The entities selected in the ERD below are based off of the normalization of the Sales Order form in third
normal form. In order to be able to store customer data and use it for multiple orders I made the
customer entity. One customer creates 1 or many orders. Each order can only contain one customer. The
orders entity was created to hold each record of an order. Then I created the Order Line Item entity to
track the line items for an order. One order can contain many order line items. This leads to the creation
of the Donut entity that holds information about the donut that is contained on the order line item. One
donut can be on many order line items and only one order line item for an order can contain one donut.
This alleviates all repeating groups and data redundancy.
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller LeCrae. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $11.49. You're not tied to anything after your purchase.