IS 401 Use Case Diagram

Question 1

use case diagram

Answer 1

is the UML model used to graphically show the use cases and their relationship to users.

Question 2

User/Actor/Agent

Answer 2

Implied in most use cases is a person who uses the system, which we have referred to up to this point as the user. In UML, that person is called an actor. An actor is
always outside the automation boundary of the system but may be part of the manual portion of the system. Sometimes, the actor for a use case is not a person;
instead, it can be another system or device that receives services from the system.

Question 3

Stick figure represents…

Answer 3

A simple stick figure is used to represent an actor. The stick figure is given a name that characterizes the role the actor is playing.

Question 4

Oval represents…

Answer 4

The use case itself is represented by an oval with the name of the use case inside. The connecting line between the actor and the use case indicates that the actor is involved with that use case.

Question 5

Automation boundary…

Answer 5

which defines the border between the computerized
portion of the application and the people operating the application, is shown as a rectangle containing the use case. The actor’s communication with the use case
crosses the automation boundary.

Question 6

> relationship

Answer 6

a relationship between use cases in which one use case
is stereo-typically included within the other use case

The relationship is read Fill shopping cart includes Search for item. Sometimes, this relationship is referred to as the > relationship or the > relationship. Note that the word “includes” is enclosed within guillemets in the diagram; this is the way to refer
to a stereotype in UML. It means that the relationship between one use case and another use case is a stereotypical > relationship.

Question 7

> relationship example

Answer 7

Therefore, one use case uses, or “includes,” another use case. Fill shopping cart also includes Search for item, View product comments and ratings, and View accessory
combinations. Thus, the Customer can view comments initially and also while carrying out the Fill shopping cart use case.

Question 8

Developing a Use Case Diagram

Answer 8

1. Identify all the stakeholders and users who would benefit by having a use case diagram.
2. Determine what each stakeholder or user needs to review in a use case diagram. Typically, a use case diagram might be produced for each subsystem, for each type of user, for use cases with the > relationship, and for use cases that are of interest to specific stakeholders.
3. For each potential communication need, select the use cases and actors to show and draw the use case diagram. There are many software packages that can be used to draw use case diagrams.
4. Carefully name each use case diagram and then note how and when the diagram should be used to review use cases with stakeholders and users.