• +1-617-874-1011 (US)
  • +44-117-230-1145 (UK)
Live Chat
Follow Us:

UML Diagram Assignment Question

Project Three

Suppose you are helping ERR Cleaners design a database. McDirty the owner of ERR Cleaners needs a couple of things to improve his business. Those things revolve around his data.

One – he cannot keep track of customers and the clothes that they bring in for cleaning or laundering very well. His tracking is all paper and pretty much catch-can.

Two – pricing for a service is manually entered into the POS device by the clerk, and that is full of error.

His pricing chart looks like this:

Item

Base Cost

Dry Cleaned

Laundered

Blanket

$6.00

$2.00

$1.50

Blouse

$2.00

$1.00

Coat

$5.00

$3.00

$2.00

Dress

$3.00

$2.00

Pants

$2.50

$2.00

$1.50

Shirt

$1.00

$1.00

So you see, some items are dry cleaned only, some are laundered only and some can be both. The price is the base price plus the cost for the cleaning method.

McDirty wants to keep track of his customers in a complete but nice way. A customer number is not friendly at all; so he needs a unique key for each customer account. He only takes cash so tracking bills is not necessary at all. Customer accounts have names, phone numbers, addresses and email addresses.

  • When an item comes in for cleaning:
    The clerk needs to get the customer account number and create a ticket for the items coming in. Noting the time, the date, each item and the price for cleaning of each item.
  • When the clothes are cleaned:
    The ticket needs to be marked with the time and date and noted that the clothes are clean ready for pickup.
  • When an item is picked up:
    The clerk collects the money, renders the clothes and marks the ticket as paid.

Given the above information design a database for McDirty. Make sure that the tables can hold the required information. Make sure that your design follows McDirty’s desires and tracks the business flow.

Present your solution as a list of Tables/Relations and a UML diagram showing tables, keys, attributes, data types, relationships. Plus write personal evaluation.