Learning Team: Sparkle Diamonds ProjectThe first part of the process was to determine what data table relationships, fieldattributes, fields, and tables would be needed to develop a database to support the SparkleDiamonds sales team.Next, an Entity Relationship Diagram (ERD) is needed that mirrors therelationships and tables used in the Sparkle Diamonds Database Project.Since the sales teamneeds the inventory to query various specifications of diamonds, an ERD must show tables forcustomers and inventory, as well as the following information about the diamond specificationsof cost, price, carat, clarity, cut, color, and ordering tables.These are the main tables that can support the necessary queries to create Sales Orders,check Inventory status, and ship to multiple customer locations.Orders start with a client, so thefirst table layout was to support the customer information required to make a purchase, ship itout, create a Sales order, and replenish inventory when it starts to run low.The CustomerInfo table includes the following columns:CustomerID (Primary Key),ShipLocID (Foreign Key), Cust_Name, Cust_Addr1, Cust_Addr2, Cust_City, Cust_State,Cust_ZipCode, Cust_EmailAddr, and Cust_PhoneNum, which are all necessary to support thedatabase design.Recognizing customers can have multiple shipping addresses, a ShippingInfotable was needed to contain ShipLocID (Primary Key), Ship_Desc, Ship_Addr1, Ship_Addr2,Ship_City, Ship_State, and Ship_ZipCode for the delivery of the diamonds.The next process was determining the needed details for the ordering process.Detailssuch as what customer is placing the order, order date, and shipping complete could beconsidered one order while the product(s) ordered could be multiple, so the order information
