In lecture, we will be developing Class and Sequence diagrams. You are free to use as

these as starting point $($recommended$!).$ The Class diagram that we develop will be

mostly complete, and we will also develop a sequence diagram in class. For the

assignment, you will just need to extend and expand these.

Part $1$: Class Diagram

Your class diagram should show your classes, along with the relationships between

those classes. You only need to show the public members of the class. You don't need

to show the private members of the class, although you can if you wish.

Your file should be named ClassDiagram.pdf$.$

Part $2$: Sequence Diagram

You are required to have at least $2$ sequence diagrams, but you are allowed to do more if

you like. Your two sequence diagrams should show how your objects interact over time

to perform some functionality of the system.

Your sequence diagrams need to be built from the classes that you have included on

Page $1$

Assignment $3$ CS $362$

your class diagram, in other words...the sequence diagrams indicate the flow of

messages between objects on the class diagram. This means that if the class isn$$t on

your class diagram, it should not be on your sequence diagram.

Your files should be named SequenceDiagram$1$pdf and SequenceDiagram$2.$pdf$.$

Additional Requirements

In addition to the description provided in lecture $($ToolStore$.$pdf$),$ your store will have

the following additional functionality. You must add these new features onto the

diagram we developed in class.

$$ The store sells two types of medicine, pills and liquid. Liquid medicine has

a CC $($cubic centimeters$)$ attribute to record the volume. Pills have a pill

count attribute to describe how many pills are in a bottle.

$$ The store now sells an additional type of tool: crowbars

$$ The store also sells an additional class of tools called Power Tools.

Specifically, PowerTools can be jigsaws, drills, or circular saws.

PowerTools have an attribute called $$amps$$ that other types of tools don$$t

have.

$$ There is an additional type of user for the store called a SalesClerk

$$ There is additional functionality that the store provides:

$$ SalesClerks can look up tools to get a tool id

$$ Customers can purchase a tool based on a tool id$.$

$$ For the sequence diagram, you may choose any store action except the

open$()$ action that we did in class.

$$ You must use proper UML notation.

$$ You must use the correct type of association between classes on your class

diagram $($aggregation$,$ composition, generalization, etc$).$

$$ All diagrams must have a title. For example: $$Tool Store Class Diagram$,$

etc. Also, the sequence diagram must have a sub$-$title based on the

operation that sequence is doing. For example: $$Tool Store Sequence

Diagram: Open Store