Case Overview: PUP Petshop, an independent company that sells food and other supplies to pet owners, specializing in supplies for dogs and cats. The owners want to automate PUPs record-keeping. All of PUPs revenues are produced through the large volume of retail sales of these supplies. For now,the owners want to focus on the 'sell' side of the business, tracking customers, sales order, and inventory sold.

Customers at PUP are generally repeat customers. The owners know many customers by face, but they want to build stronger customer loyalty by knowing their customers names, and by tracking their purchase history. They think that it would be great if they could keep track of the name, type of animal, and age of every pet a customer owns.

For each item, PUP keeps descriptive information: SKU# (stock keeping unit), the items name and the item's description. PUP also records the cost per unit, the suggested retail price per unit, the quantity on hand, and a reorder point. PUP keeps this information in hardcopy binders. Currently, when a customer shops at PUP, a clerk must go through the binders and manually update the inventory to show what items have been purchased. Customers typically buy more than one item at a time, and often will buy several units of an item. Every item has the price stamped on it, but if the price is not on the item, the clerk must look up the price in the binder.

The owners would like to have a way for the system to automatically look up the price of an item based on the items SKU#, and also update the inventory amount of that item. Theyd like to be able to see which items move faster and which move slower, and also would like to have a report that informs them when an item is low on quantity, so that they can reorder it. They also want to categorize PUPs inventory into groups like Food, Toys, Grooming, in order to track sales per category better. They would like to avoid having to type in the entire category label, however, to minimize clerical errors. PUP needs a DBMS.

TASK: You are to develop and submit an entity-relationship diagram (ERD) for this case. Plan on developing and refining several drafts before reaching complete and accurate ER diagrams.

Plan on developing and refining several drafts before reaching complete and accurate ER diagrams.

Draw the UML E-R diagram for this enterprise, including the attributes for each entity;

Identify all possible relationships;

Identify the cardinality for each relationship;

Identify the mandatory/optional dependencies for the relationships;

Identify any weak entities; Resolve all M:N relationships.

Also, on a separate sheet, specify any additional assumptions you made in designing your diagram