You are on page 1of 3

USE CASE # 4

Scan item

Goal in Context

Allow customers to check price of items and keep a running total of the
price

Trigger event &


Type

Customer finds an item they require


external

Primary actor(s) &


Secondary actor(s)

customer
<other actors required to complete the use case>

Related use cases

Include: 5,3, 9
Extend: 6,7

Preconditions

Successful login into the system

Success post
condition

Price and running total provided, data retrieved

Failure post
condition

No information is provided or collected

NORMAL FLOW
steps (NF)

Priority: High

Action

NF1

Trolley interface prompts user to scan item

NF2

Customer scans item on the omnidirectional scanner

NF3

Trolley interface processes item barcode into system

NF4

System updates scan history on user account

NF5

System retrieves price from database

NF6

System returns price to trolley interface

NF7

Customer obtains price

NF8

Interface prompts user if they want to add item to cart

NF9

Customer selects yes

NF10

Interface returns trolley total

NF11

System prompts user if they have finished shopping

NF12

Customer selects yes

NF13

Executes UC# 7 prompts payment

ALTERNATE
FLOW steps (AF)
AF1#.a

Action
Incorrect scan of item

AF1#.a.1

System logs scan attempt

AF1#a.2

Customer shown scan error on display

AF1#a.3

System prompts customer to re-scan item

AF1#a.4

Return to NF1

AF7#a.1
AF7#a.2
AF12#a.1
AF12#a.2

Customer selects no
Return to NF1
Customer selects no
Return to NF1

EXCEPTION
FLOW steps (EF)
EF1#.a
EF1#.a.1

Action
System has logged 3 consecutive scan errors
System prompts user to seek assistance from staff. The UC ends

USE CASE #10

Customer personalized email

Goal in Context

Send customer specific promotional emails using data gathered from the
smart trolleys

Trigger event &


Type

Emails are send periodically on a week by week basis


Temporal

Primary actor(s) &


Secondary actor(s)

Time
server

Related use cases

Include:
Extend: 9

Preconditions

Customer has used the smart trolley system and recorded data for at
least a week

Success post
condition

An email is sent with appropriate promotions

Failure post
condition

Promotional material does not reach customer

NORMAL FLOW
steps (NF)

Priority: High

Action

NF1

System algorithm processes customer data

NF2

System identifies regular purchases

NF3

System checks if most recent shopping date is more than 3 months

NF4

System returns no

NF5

System checks customers regular shopping date

NF6

System checks if current date is the day previous to the regular shopping
date

NF7

System returns yes

NF8

System verifies email is on subscriber list

NF9

System returns yes

NF10

System sends email to customer with personalized promotions

NF11

Customer receives email

NF12

Customer opens email

NF13

System logs email read

ALTERNATE
FLOW steps (AF)
AF1#.a
AF4#.a.1

System returns yes

AF1#a.2

System sends special exclusive deals to customer based on


regular purchases
UC ends

AF7#a.1

System returns no

AF1#a.2

System breaks process until next active day

AF1#a.3

Return to NF1

AF11#a.1

Customer has a choice to open the email

AF11#a.2

Customer does not open email

AF11#a.3

UC ends

EXCEPTION
FLOW steps (EF)
EF2#.a
EF2#.a.1
EF8#.a

System has insufficient data on customer


UC ends
Customer needs to be on subscriber list to send emails to

EF8#.a.1

System returns no

EF8#a.2

UC ends

EF12#a

System needs to keep track of read emails

EF12#a.1

Customer does not read email

EF12#a.2

UC ends

You might also like