Reminder: Microsoft Visio has a library of shapes specifically for UML Diagrams. In the left-hand Shapes box, click on "More Shapes >> Software and Database >> Software. There is a collection of pre-set shapes for each type of UML diagram we draw.
Sequence Diagrams Building on any of your use case scenarios, create 4 sequence diagrams that depict the interactions between use cases and the messages that pass between them. These diagrams should be instance-specific and not generic sequence diagrams. See Chapter Six: Interaction Diagrams (i.e., sequence and communication diagrams). I highly recommend each team member take a crack at drawing a sequence diagram and its corresponding communication diagrams.
Communication Diagrams
Building on your class diagrams, create 4 communication diagrams to represent the message-passing relationships in your model (rather than the simple associations in your class diagrams). Sequence and Communication diagrams should depict the same process. You should create the sequence diagram first, then its corresponding communication diagram. The same person should do this or two people working very closely together.
Behavioral State Diagram
Behavioral diagrams may not make a lot of sense for your project (depending on how complex your system is), but I’d like you to at least demonstrate that you know how to do them and what they are. Your book talks about them in Chapter Six: Behavioral State Machines.
Create 1 behavioral state diagram for one of the classes in your class diagram or a class in your system that is not yet captured in the models you’ve drawn.
Before submitting any of your diagrams, validate them! Walk through them with one another to make sure they communicate what you want them to. You’ll be walking through them with me after they’re turned in.