Tutorial 5 - Use Case Diagram / Documentation Part A: True or False
Tutorial 5 - Use Case Diagram / Documentation Part A: True or False
1. Use cases can be used to document both the current (As-Is) system and the future (To-
Be) system.
Answer: _True____
2. From a use case, you should be able to tell if the activity is computerized or
manual. Answer: ___True_______
4. The primary actor is the person or thing that starts the execution of a use
case. Answer: ____True______
5. The include relationship represents the optional inclusion of another use case.
Answer: ____False______
7. A very complex use case should be broken down into a set of use cases.
Answer: ___True_____
8. An include relationship is modeled in a use case diagram by an arrow with the word
<<include>> above it.
Answer: ____True______
10. A formal way of representing how a business system interacts with its environment is
called a use case.
Answer: _____True_____
1. A(n) _____ is a formal way of representing how a business system interacts with
its environment.
a. use case
b. physical model
c. relationship
d. system boundary
2. Which of the following diagramming symbols represents an actor in a use case diagram?
a.
b.
c.
d.
3. Which of the following diagramming symbols represents a use case in a use case diagram?
a.
b.
c.
d.
6. The _____ relationship in use cases allows use cases to support the concept of inheritance.
a. association
b. extend
c. include
d. generalization
7. The event that causes a use case to begin is called a(n) _____.
a. action
b. trigger
c. hammer
d. anvil
8. Which of the following relationships describe the communication between the use case and
the actors?
a. association relationship
b. extend relationship
c. include relationship
d. generalization relationship
9. Which of the following relationships represent the extension of the functionality of the
use case to cover optional behavior?
a. association relationship
b. extend relationship
c. include relationship
d. generalization relationship
10. Which of the relationship types in use cases enables functional decomposition?
a. association relationship
b. extend relationship
c. include relationship
d. generalization relationship
Part C: Structure Questions
1. Define actor in the Use Case Diagram. Identify THREE (3) types of actor.
An actor is a role that a user plays with respect to the system.
User
External system
Physical environment
2. Distinguish between <<extend>> and <<include>> relationships in Use Case Diagram. Give an
example for each of these relationships been used.
<<extend>> <<include>>
Represent exceptional or seldom invoked cases. Represents behaviour that is factored out of the
use case.
Exceptional event flows are factored out of the Represents behaviour that is factored out for
main event flow for clarity can extend more reuse, not because it is an exception.
than one use case.
Direction of a <<extend>> relationships is to the Direction of the relationship is to the using use
extended use case. case (unlike <<extend>> relationships).
Example: Can be used when showing Example: Can be used when factor out shared
precedence order (with exceptions). sub-processes.