Prepare a UML class diagram (classes, associations, attributes, and multiplicities) for the specified component of CADBURY Enterprises.

CADBURY sells its chocolates to customers through a network of company salespeople. Each type of chocolate is bought from a particular vendor and is given an initial list price. 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 chocolates and can be paid for in any one of three ways: (1) immediately in cash, (2) on the 15th of the following month, or (3) over the course of six months. When cash is received, a cashier deposits it into a company bank account. Sales are signaled by invoices; cash receipts by remittance advices.

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 (attributes with asterisks are hints for some (not all) of the needed relationships).

-chocolate# -chocolate description -list price

-primary vendor for this chocolate type -QOH (quantity-on-hand)

-bank for cash account -bank account# -bank-account type

-customer name -a/r amount -customer salesperson*

-customer# -invoice#

-sale date -sale amount -inventory quantity sold

-actual price of each chocolate -receipt date

-salesperson quarterly sales -salesperson comm. rate -Sales person ID#

-fidelity bond rating of cashier -cash receipt amount

-remittance advice# - Sales person highest degree

- Cashier name - Cashier highest degree

Cashier ID# -cash account balance -monthly salary-cashier

-monthly salary of sales person -amount of cash receipt applied to a certain sale

-unit cost