Design a simple relational database that captures the information required to

maintain records of orders. Take into account that your design should allow a

customer to order as many items as he$/$she would like, eliminate potential errors

and redundancies by having multiple tables for the entities that are needed in

this process. Present your design with an Entity Relationship Diagram $($ERD$)$

for this database. Add attributes if necessary $($e$.$g$.$ primary key$($s$))$ to make sure

you have unique records in your tables. Consider compounding fields to create

unique records on your intersection table. Follow the design process to avoid

potential issues as discussed in class.

b$)$ Use the concept your initial design from part a$,$ and create your database in

Access. Create the relationships between your tables and populate your

tables with the orders$/$information in Table $1.$

Deliverables: Access database file. Include your ERD diagrams $($either created

in access or scan any ERDs drawn by hand.$)$