Create and submit an ER Diagram with at least two tables an…

Create and submit an ER Diagram with at least two tables and their attributes.  Your diagram should include: Your tables should be should be normalized (first, second and third normal forms) You can use the attached form or upload your tables in Excel or create and link them in an Access database file. For information on how to use Word to create and ERD, go to: You can upload your tables in Excel, Word or create and link them in an Access database file.  If you use another tool please create a PDF file of the results. Resources for Building ER Diagrams and Normalization: What is an ER Diagram: Video Tutorial Entity Relationship Diagram (ERD) Training Video: Video: How do I normalize a database: cle Article: Sample of a Diagram with many tables:

ER Diagram:

Table 1: Customers
Attributes:
– CustomerID (Primary Key)
– First Name
– Last Name
– Email Address
– Phone Number

Table 2: Orders
Attributes:
– OrderID (Primary Key)
– CustomerID (Foreign Key referencing the Customers table)
– Order Date
– Order Total

Normalization:

First Normal Form (1NF):
To achieve 1NF, each attribute in both tables should contain only atomic values. In the given tables, the attributes already satisfy this condition as they contain only single values.

Second Normal Form (2NF):
2NF requires that each non-key attribute in a table is functionally dependent on the entire primary key. In the Customers table, all the attributes (First Name, Last Name, Email Address, Phone Number) are functionally dependent on the CustomerID, which is the primary key. Therefore, the Customers table satisfies 2NF.

In the Orders table, the OrderID is the primary key, and the Order Date and Order Total attributes are functionally dependent on it. However, the CustomerID attribute is not functionally dependent on the entire primary key. It is only functionally dependent on a subset of the primary key (OrderID). To achieve 2NF, we can split the Orders table into two separate tables: Orders and OrderDetails.

Table 2: Orders
Attributes:
– OrderID (Primary Key)
– CustomerID (Foreign Key referencing the Customers table)
– Order Date

Table 3: OrderDetails
Attributes:
– OrderID (Primary Key and Foreign Key referencing the Orders table)
– Order Total

Now, the Orders table satisfies 2NF as every non-key attribute is functionally dependent on the primary key.

Third Normal Form (3NF):
3NF requires that no non-key attribute is transitively dependent on the primary key. In the Customers table, all attributes are directly dependent on the primary key, so it satisfies 3NF.

In the Orders table, the OrderDate attribute is directly dependent on the primary key. However, the OrderTotal attribute is transitively dependent on the primary key through the OrderDetails table. To achieve 3NF, we can further split the OrderDetails table into two tables: OrderDetails and Products.

Table 3: OrderDetails
Attributes:
– OrderID (Primary Key and Foreign Key referencing the Orders table)
– ProductID (Foreign Key referencing the Products table)

Table 4: Products
Attributes:
– ProductID (Primary Key)
– Product Name
– Price

Now, the Orders table satisfies 3NF as no non-key attribute is transitively dependent on the primary key.

In summary, the provided ER diagram includes two tables (Customers and Orders) and their attributes. The tables have been normalized to comply with the first, second, and third normal forms. The Customers table is in 2NF and 3NF, while the Orders table has been split into two tables (Orders and OrderDetails) to achieve 2NF and 3NF.