Match the description of a model with the appropriate UML diagram type. Each UML diagram should be used exactly once.

A. A mult-step process, showing the steps taken from one task to another within the process. There is (usually) one starting point shown with a solid disc but there may be multiple ending points, drawn as a disc plus an outline. Decision points are drawn as hollow diamonds and the direction from one step to the next is shown with an arrow.

B. The interactions among objects required to complete some particular task. The objects are shown each in their own column, and the interactions start at the top, concluding at the bottom.

C. The users of a system and the actions they can take; may also show that an action interacts with a second user or system. Users are typically drawn as simple stick figures.

D. Represents the behavior of an event-driven system that may respond to internal events (such as a timer) or external events (interaction with a user or other system)

E. Reveals associations between objects in the system such as generalization and aggregation. An object in the system may be expanded to show detail about its capabilities and data.

	1. Activity diagram
	2. Use case diagram
	3. Sequence diagram
	4. Class diagram
	5. State diagram