Tutorial - Use Case Diagram - Visio 2016 PDF

Preview

Summary

Tutorial for Use Case Diagram using Visio 2016...

Description

Drawing a Use Case Diagram – MS Visio 2016

Use case narratives are primarily textual descriptions of the interactions between your system and users or other external systems. We use a use case diagram to show the relationships between actors and a set of use cases. A use case diagram is a graphical overview of your users, external systems, and use cases. It is part of the Unified Modeling Language UML 2. It was originally part of object oriented modeling and now is popularly used by all SDLC methodologies. It provides, at a quick glance, who interacts with your system (represented as actors), their goals (represented as use cases), and any dependencies between the use cases. We will use Visio to duplicate the use case diagram for a simple address book system shown above. 1. File > New > o You may have to search for UML templates: type UML in the search box o You should receive a number of templates. Select use case diagram.

2. The screen now contains the following o On the left hand side, you will see a frame labeled SHAPES. There you will also find the main use case elements that you can use in your diagram. o The main drawing frame contains a 2-way ruled worksheet. 3. Click on Subsystem and drag it to the main drawing frame to draw the system boundary. o Click on the name and change it to Address Book System 4. Add an actor o Click on the actor symbol and drag it to the drawing frame. Drop it outside the system frame/boundary on the left side. o Name the first actor "User" by double clicking on it 5. Add a use case o You can do this in two ways  Click on the use case symbol and drag it inside the system frame.  Or you can click once on the actor that you have placed on your diagram. Blue arrows will appear. You can click on the use case symbol associated with the blue arrow to create a use case that the actor can use (or is associated with) o To rename the use case, double click in the center of the use case, and add text (remember to use verbs) o Create the nine use cases that are directly attached to the “User” actor 6. Add relationships between actors o Create the second actor, name it “Admin” o Click on the Generalization symbol and drag it to the child actor (Admin). The tip of the generalization arrow should always point towards the parent (User). Admin is the child here because it is a special kind of User. User is a parent or generalization. 7. Add relationships between use cases o To add a generalization relationship  First create the two child use cases (Sort entries by zip and sort entries by name)  Click on the Generalization symbol and drag it to one of the child use cases. The tip of the generalization arrow should always point towards the parent use case (Sort entries).  Repeat for the second child use case o To add an Includes relationship  Create the included use case (Save address book as)  Click on the Include symbol and drop it on the main use case (Save address book) and drag the tip of the arrow to the included use case  You will notice the stereotype is added to the relationship o To add an Extends relationship  Create the extending use case (Offer to save changes)  Click on the Extend symbol and drop it on the extending use case (Offer to save changes) and drag the tip of the arrow to the main use case that is extended. In our example, we have three such use cases that are extended (Quit program, Open existing address book, and Create new address book)  You will notice the stereotype is added to the relationship



NOTE: some other software diagramming/modeling UML tools support adding extension points to the extended use case to indicate what type of condition causes the extending use case to be invoked (discussed more in class)...