C. ER Modeling and Normalization (10%) Mini Case: A local computer shop sells hardware parts that are related to laptops. A brief info about some important business entities and transactions are summarized below . Part: It is identified by a unique SKUe and characterized by Name, description, and suggested . Order: It is identified by a unique . Customer: It is identified by a unique CustID and characterized by name, email, and phone unit price Supplier: It is identified by a unique S and characterized by Name and Phone order is placed by ordered is associated with an ordered On and characterized by Date and Shipping Method An a customer and an order may associate with one or more parts, and each part GoodsReturn: It is characterized by a unique SKUlE and characterized by Rethurn Date Return O tion to the above, for tracking of business reliability, each Part is further classified into two Domestic and Imported. The properties associated with a Domestic part have State and an subtypes 800 hotline for phone services, and the properties of an Imported part include Country, and Warrant for each h part. By convention, a supplier will provide at least one or several parts, and a part may be vided by one or e several suppliers (i.e.. .some parts may be on the catalog but have no suppliers..A customer will place one or several orders, and an order will have one or several onder items, and an order item may or may not be returmed since it may not have any defects 1) Use the symbols as adopted by Visio 2013 to hand draw an extended ER (EER) diagram that is based on the above facts (Note: In your ER diagram, it shall not have many-fo-many relationships) A symbol of Supplier is given as an example for you to start 06%) 2) Write down each normalized entity in your EERD. Specifically, use the following format for each normalized relation. (4%) SUPPLIER (SupplierlD, Name, Phone) PK: SupplierlD FK: none Use space provided on the next page to complete your database schemal