You have been hired to design the database for Pine Mountain Furniture. You interview the owner to determine what the business rules are for the database. Below is what you find out. The company has many customers. Each customer is given a unique customer ID. We record the name of the customer, the type of customer (business/consumer), and the customers zip code. Many customers have been long time customers and have placed several orders over the years. For each order we assign an order number, and track the date the order was placed, the date the order was fulfilled, and the number of shipments it took to complete the order. The company sells many different types of products (furniture). Each type of product (furniture) is given a product number. For each product we track the product finish, and the product cost. Orders can contain many products and products can be on many different orders. For each ordered product we track the quantity of the order, and the extended price. The owner would also like to track detailed data on products: multiple product price levels for volume orders. Each product can have multiple volume product price levels, but each volume price level is only related to one specific product number (furniture type). For each product price level, we track the product ID, volume quantity, and unit price. Required: Draw an ERD for this database using the REA framework. Show entities and relationships, as well as the primary keys and foreign keys (FK). Required: 1. Draw the ERD (using the REA format) for the above database. Draw entities (organized from left to right as resources, events, and agents), relationships, and cardinalities. Use 1 and M to indicate cardinalities. 2. Indicate the attributes for each of your entities and/or tables produced for those entities. 3. For each of your entities, underline primary key fields (write PK next to the selected attribute). 4. Embed foreign keys as appropriate to relate the tables together. Write FK next to foreign keys.