Drawing UML Use case diagrams with Visio

1. Use case diagram

Use case diagrams describe the system functions that the participants understand. The main elements are use cases and participants.

The 4 basic components of a use-case diagram: Actors, use cases, relationships (relationship), and systems.

The following is an example of a bank savings system.

(1) Use case: an interaction between users and computer systems, representing a complete function of the system, is a set of action sequences. When the system finishes executing this set of action sequences, it produces a result that is valuable to the participants.

Bank Savings System Use cases: deposit, withdrawal, input deposit information, print certificate of deposit, enter withdrawal information, print balance ...

The use case diagram is represented by an ellipse.

(2) Participant: person or thing interacting with the system.

A participant in a bank savings system: A clerk, a depositor.

The use case diagram is represented by a villain.

(3) Contact

Participants and use cases: communicating through <<communicate>> relationships. Communicate is an association relationship and is a one-way association. For example: salesman (role) and take money (use cases), salesman is the initiator of communications, the salesman started to take money use cases.

Participants and participants: if there is an association between the participant and the participant, it can be considered a generalization relationship. The generalization relation is the inheritance relation between the general class and the special class. Cars and ships, for example, have a generalized relationship with transportation. They belong to the same means of transport, with their own characteristics.

Use cases and use cases: there are generally generalizations, inclusions (uses), and extensions.

Use case generalization: a use case can be specifically enumerated as one or more child use cases. "Phone booking" and "online booking" are generalized to "bookings".

The representations that contain (use) and extend are constructed on a dependency relationship and are described in English as:<<include>> (<<use>>) and <<extend>>.

Bank Savings System:

<<include>> Relationship: A function of use case execution always includes the characteristics of the included use case. In, the action sequence of withdrawal includes the input withdrawal information, check the balance, verify the password and other behavior sequence, so the withdrawal use case "contains" the withdrawal information use case.

<<extends>> relationships: The execution of a use case may require additional use case functionality to scale, but the primary use is to make the functionality of the base use case independent of the extension use case. In, the withdrawal behavior sequence is extended to print the deposit slip, but the withdrawal behavior does not depend on printing the deposit slip. This means that even if a deposit slip is not printed, the deposit will be carried out, but the deposit slip is only printed when the deposit is carried out. An extension use case is activated by a basic use case.

2. Use Visio to draw a use case diagram

(1) Open Visio 2010 software

(2) Click "New", "Software and Database", "UML Model Diagram".

(3) In Model Explorer, right-click the top-level package or create a new subsystem, new, use case diagram

(4) in the left "shape", "UML use Case" drag "system boundary", double-click the system boundary in the drawing interface, change the system name.

(5) Below you can drag the participants and use cases to build their own use case diagram.

(6) When drawing a relationship, the diagram required by the use case diagram is found in the UML use case, and if <<communicate>> is not found, then UML, stereotype on the stand-alone menu, in the UML Stereotype dialog box that pops up, click New ", enter the information for the communicate. As shown in the following:

Drawing UML Use case diagrams with Visio