Complete the Entity-Relationship diagram below (Figure 1) by adding the necessary entities, attributes and relationships to include

the following additional data requirements.

Identify any constraints not captured by the ER diagram. Use the total/partial as participation constraints and cardinality ratio notation to specify maximum number of relationship instances. Please ensure to note any unspecified requirements, and make appropriate assumptions to make the specification complete. Below are the provided details about the ER diagram to complete the diagram on Figure 1. TRI wishes to use the database to generate invoices for customers' purchases. Each invoice must contain customer number, the sales representative's number, date, status, subtotal, amount of tax, and total amount of the purchase. Each invoice is written by a sales representative. Each sales representative can write many invoices, but each invoice is written by a single sales representative. An invoice is generated for a single customer. However, each customer can receive many invoices. Each invoice contains a list of items, each of which describes a single product purchased (e.g. product code, price per item, quantity purchased, and total price per item). RepNo Fname FName Phone name Lname CustNo Email Email No Year salesrep Customers ShipAddress Street City Postal Code Province SUPPLY M N Vendor Product Item email Desc Total Price contact Price vendName aty MPart No Stockly vendName PCode ItemPrice