RB Candy sells its products to customers through a network of company salespeople. Each salesperson services a separate group of customers and is allowed to offer them various discounts from list to induce sales. Each sale can include one or more types of products and can be paid for (1) on the 15th of the following month, or (2) over the course of six months. When cash is received, a cashier deposits it into a company bank account. Sales are signaled by invoices.

The policies above plus the information elements listed below are relevant to potential users of this data model, and they all should be included in its final structure. Please assume that cashiers and salespeople both belong to an entity called "employee."

Information elements in the model (attributes): -product# -product description -list price -QOH (quantity-on-hand) -bank account# -bank name -account type -employee's highest degree -customer name -A/R amount -customer# -invoice# -sale date -sale amount -inventory quantity sold -actual price of each product -employee name -salesperson quarterly sales -salesperson comm. rate -employee# -bank# -cash receipt date -cash receipt amount -employee category -remittance advice# - bank address -number of employees in category -bank phone number -medical plan for this category -cash account balance -monthly pay of employee -amount of cash receipt applied to a certain sale -unit cost -cash receipt#

Required: Use the information above and the list of data elements to construct an UML Class Diagram for RB Candy. You must include the attributes in the diagram, and indicate the primary key and foreign keys in each table. Please consider generalization (IS-A relationship) and typification for some entities.