Database Plan for Riordan Manufacturing Material Ordering

Step 2. Data Analysis: The data will be analyzed to determine database modeling. Step 3. Database normalization: Fields and

2. using the data requirements and the business rules provided, develop a conceptual model (ERD), including attribute data types and required field lengths; and

To answer each question, darken the circle corresponding to your answer using a pencil. If you decide to change your answer, please erase your original answer completely and darken your new answer.

This week was a little harder comparing to last; well it is expected because we are getting more into how to create a more dependable database. The topics for this week were “The problem of redundancy, Decompositions, Functional Dependencies and normal forms. We learned how to recognize and avoid the problem redundancy in database along with how to convert database schema into first, second, third normal forms.

There are three stages to normalization, 1st NF, 2nd NF, and 3rd NF. In the 1st NF stage must ensure that the table has no multivalued attributes. If there are the table should be broken down into separate tables so that there are no multivalued attributes. The 2nd NF stage requires that we break the tables down even more to ensure that all attributes and functional dependency entirely to the primary key and has met all requirements of the 1st NF. Then, and only then will it be considered to have met 2nd NF requirements. To transform the database to 3rd NF you must identify the primary key in the 2nd NF table. Then we must identify functional dependencies in the relationship to ensure there are no transitive dependencies. These types of dependencies can cause insertion, deletion, and update

Phase 3: Sketch the star schema for the database and developed the database based on the star schema.

Hence, this session has enhanced my understanding about normalization and how essential to create a data that is well organized with the relationships clearly defined and established between the tables (based on the business rules) in order to eliminate data redundancy and inconsistency.

After above 5 steps are done, create/initialize the database by adding tuples in appropriate fields.

2NF (Second Normal Form): The relation should not have any partial dependencies; part of the primary key should not identify a subset of attributes in the same table. The relation must be in 1NF before it can be in 2NF [12]

Although Change Request No. 3 seems fairly simple, it will bring to light any issues that might have been encountered while interpreting the tables from the ERD Diagram. It is not uncommon for changes to be needed to the database after it has been created from the ERD. Moreover, now is the best time to catch these issues before the system is fully functioning making it much more difficult to make certain changes.

First our team will talk about how Microsoft Access was used to create these tables by Huffman Trucking Database. Then how we used the tables with made up information to be tested on. Then on how we used forms in the maintenance database system. While the creation of relationships and normalization is explained in the process of using queries to search the database (University of Phoenix, 2007).

A. Lab # : BSBA BIS245A-1 B. Lab 1 of 7 : Introduction to MS Visio and MS Access C. Lab Overview--Scenario/Summary TCOs: 1. Given a business situation in which managers require information from a database, determine, analyze and classify that information so that reports can be designed to meet the requirements. 2. Given a situation containing entities, business rules, and data requirements, create the conceptual model of the database using a database modeling tool. Scenario: You have been asked to create two conceptual database models using MS Visio Database Model Diagram Template. The purpose of this lab is to have you gain familiarity with the various modeling tools needed to create a conceptual model (entity relationship diagram) of a

When it comes to the data model, there exists a relationship that has three different representations for the reason that database requires the relationship between the tables. It goes hand-in-hand with one another without the relationship the tables would have no purpose. The information cannot be repetitive in order for the each table to work and provide the specific database that is related to the information. In different ways the tables in the Huffman Trucking Fleet Truck database

b. To help us process your order with our new database software, we need you to go to this Web site and fill out the required customer information.

if A!B and B!C, then C is transitively dependent on A via B (provided that A is not functionally dependent on B or C) Third Normal Form (3NF) is a relation that is in first and second normal form in which no Non- Primary key attribute is transitively dependent on the primary key.