0% found this document useful (0 votes)
41 views

Slide 3 - Use Cases

This document discusses use cases, which are text stories that describe how actors interact with a system to achieve goals. It defines actors as things with behavior like people or systems. Use cases are collections of scenarios that depict an actor using a system. Scenarios are specific sequences of actions between actors and the system. An example use case of a customer purchasing items at a checkout is provided to illustrate these concepts.

Uploaded by

dR_nech
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
41 views

Slide 3 - Use Cases

This document discusses use cases, which are text stories that describe how actors interact with a system to achieve goals. It defines actors as things with behavior like people or systems. Use cases are collections of scenarios that depict an actor using a system. Scenarios are specific sequences of actions between actors and the system. An example use case of a customer purchasing items at a checkout is provided to illustrate these concepts.

Uploaded by

dR_nech
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 8

Use Cases Part 1

OOAD - IF
Introduction

 Use cases are text stories


 used to discover and record requirements

“use cases are not diagrams, they are text “


What are Actors?

 an actor: something with behavior, such as a


person (identified by role), computer system,
or organization;
What are Use Cases?

 a use case: a collection of related success


and failure scenarios that describe an actor
using a system to support a goal
What are Scenarios?

 A scenario: a specific sequence of actions


and interactions between actors and the
system; it is also called a use case instance.
Best Practice:

 Process Sale: A customer arrives at a checkout with


items to purchase. The cashier uses the POS
system to record each purchased item. The system
presents a running total and line-item details. The
customer enters payment information, which the
system validates and records. The system updates
inventory. The customer receives a receipt from the
system and then leaves with the items.
Scenario example
 Main Success Scenario:
– A customer arrives at a checkout with items to return. The
cashier uses the POS system to record each returned item

 Alternate Scenarios:
– If the customer paid by credit, and the reimbursement
transaction to their credit account is rejected, inform the
customer and pay them with cash.
– If the item identifier is not found in the system, notify the
Cashier and suggest manual entry of the identifier code
(perhaps it is corrupted).
– If the system detects failure to communicate with the
external accounting system, …
Best Practice: Use case

You might also like