Can you help? I am not good at ERD set ups and i need to do task 4. Thank you!

customer orders orderltems PK customerID PK LorderlD fname productID customerID FK name OrderDate quantity phone price shipping Method ema dateOfBirth shipping Cost gender ccType ccNumber expireDate billingAddress billing City billingState product billing ip shipping Address PK productID shipping City productName shippingstate description shippingzip price salePrice department category keywords As stated above, it appears that we have redundant data in our database with the price attribute being stored in multiple tables. At first glance, it seems like we could just connect orderltems and product together using an inner join on the productID attribute and use the price attribute listed in the product table. But think about prices at your local grocery store and what happens to them over time. They change! Therefore, these two attribute actually serve different purposes. Price in the product table shows the current price of the product and the price attribute in the orderItems table show the price of the product at the time it was purchased. If a customer were to purchase the item when it was on sale then we need measures in place to ensure they don't retum it at regular price. So we track the price that the item was sold for We also have a business rule in terms of price and salePrice in our product table. If the sale price is lower than the price, then we want to highlight that the item is on sale to the customer and provide the item for the sale price Now that we have established a working ERD without M:N relationships, we can move on to the normalization process. But before we do, let's make some minor changes that our programmers will appreciate. Remember, the programmers will be writing applications that connect to the database and require SQL statements to do so. Therefore, they will be typing the entity and attribute names in their source code when programming. Long attribute names are a nuisance to programmer because they have to type the name out each t ime they use the attribute. As a courtesy to our programmers, it's always useful to abbreviate attribute names and make them as short as possible. It will increase the speed at which our programmers can program their applications. Here is the same ERD we just developed but with many attributes abbreviated