A01 chaf6542 06 se fm indd

4 

The customer will select ‘submit’.

5 

The system will check all fields are present and the customer information will be passed to 

the CRM system.

Scenario

A particular path or flow 

of events or activities 

within  a   use-  case.

Figure 11.13

Primary  use-  case scenario for an entire e-commerce purchase cycle

Place repeat / modify rebuy order

Place repeat / modify rebuy order

Place support enquiry

Check order history

Check order status

Post-order activities

Pre-order activities

Key

Receive dispatch confirmation

Receive order confirmation

Place order

Register on-site

Review product specification

Catalogue search

M11_CHAF6542_06_SE_C11.indd   549

7/23/14   1:26 PM

---

550

Part 3  Implementation

Figure 11.14

Primary scenario for the Register  use-  cases for a B2C company

Confirmation

Info sent to CRM

Submit

Enter details

Cancellable

[data valid]

Press register

6 

A redirect page will be displayed to thank the customer for registering and provide an 

option to return to the home page, and the  use-  case ends.

 Post-  condition: The customer details have been saved.

Alternative paths: The customer can cancel at stages 2 to 4 before pressing ‘submit’ and 

the   use-  case  ends.

It can be seen that by stating the  use-  case in this way different issues can be clarified. After 

the primary scenario is complete, second or alternative scenarios can be developed and 

added to the primary scenarios as alternatives. For the register scenario, cancel is a second-

ary scenario; others could include error conditions such as whether the postcode is invalid. 

Figure 11.15 illustrates an e-commerce site with clear menu options which is consistent with 

 use-  case  analysis.