Online Clothing Shop

Document Type: Use Case Document

Version Description Changed By Date

1.0 First draft Fagoroye 02/11/201
Ayodeji 0

Introduction
Use Case design, or usability design has been around for quite a while in the arena of general software design
methodologies. One place it hasn’t penetrated very deeply is in the area of website design. As websites have
grown in complexity and in the number of different tasks they perform, they come close to and often cross
over into true software applications, rather than dressed up content formatting. This generally means that
keeping a firm grasp on how a website will actually be used will make your websites more effective for
customers and users, and easier to implement and maintain for you as the software engineer. The best way to
accomplish this is through usability design practices.

Because most websites are designed to be used by the general public, how a user interacts with a website is
often more important than with other applications. True Web applications must be more intuitive, more
streamlined, and more fail-proof than almost any other piece of software that is commonly used or deployed
by most businesses. Through doing usability design on a website, and especially through maintaining that
design during the implementation of a Web application, the programmer will be forced to keep the usability
of that Web application as his or her first design priority throughout the implementation process.

A use-case is, simply, a detailed, written description of a user’s interaction with a system or application to
accomplish one simple task. Generally, use-cases are titled with the name of the action the user is
accomplishing. For instance, a use-case title might be something like “User orders a product.”

Specifically, the title is usually some sort of active tense statement about what a user is trying to do. From this
title, a software engineer or designer writes the series of actions the user must go through to accomplish this
task. He or she details the data the user provides to the system, what data the system provides in return, the
possible branches the path can take, and any error conditions that might occur along the way.

These are useful for design because they focus entirely on how a user interacts with a system, detailing what
exactly the system must provide to and receive from a user. These are the things that are important for

Author: Fagoroye Ayodeji Page 1 of 8 Printed: 04/11/2010

Online Clothing Shop

Document Type: Use Case Document

programmers to focus on, but often they get forgotten in the process of actual programming. Use-cases are
also a central aspect of UML design processes.

Brief Description: The aim is to develop a web-based online shop to sell polo shirts, trousers and shoes
that are customizable to a customer.

A customer comes to the website, browses items on display and upon selecting
preferred item adds it to his/her shopping cart. When done with the shopping,
customer checks out cart items. Customer will be required to register i.e. provide basic
details about themselves and login upon successful registration, after which they can
continue to process their orders. A sales assistant processes a customer order. The
customer pays for the order by credit card. An invoice and a picking list or delivery
note are produced/
Business Trigger: A customer asks to purchase some goods
Preconditions: The system is displaying the main menu

Basic Flow
The basic flow or primary success scenario describes what happens when everything goes right. It is the path
that gives the best overall understanding of the use case. It begins with the event coming across the system
boundary from the active actor to the system that starts the use case.

Basic Flow:
Line System Actor Action System Response
1 The customer browses displayed items on the
website
2 The customer add items to shopping cart
3 Customer proceed to checkout The system asks the customer for identification
4 Customer enter login information The system displays a confirm order screen with
the selected items for customer confirmation
5 The customer confirms order and required The system asks customer to provide shipping
quantity and billing information
6 Customer provide shipping and billing The system confirm the shipping information,
information process order and ship out the items
7 Customer receive the items

Author: Fagoroye Ayodeji Page 2 of 8 Printed: 04/11/2010

Online Clothing Shop

Document Type: Use Case Document

Post Condition: The system display order and transaction history to customer

Alternate Flow
An alternate flow describes a sequence that is different to that specified in the alternate flow. It always
contains four elements:
1 The place where the alternate flow inserts itself e.g. ‘If at line 3 in the basic flow’

2 The condition under which the flow inserts itself e.g. ‘the card is found to be invalid, then:’
3 The alternate flow written in the normal way e.g. ‘the system displays the message “invalid card”
and ejects the card. The customer takes the card. The system displays the message “enter card”.’
4 What happens next which is ether ‘The use case terminates’ or ‘The use case restarts at ….’

The use case can restart at an earlier line than the one from which it was invoked creating a loop, the same
line, or at later line.

Alternate Flow (AF1): Handle Invalid Customer

Alternate Flow (AF2): Handle Invalid Order

Alternate Flow (AF3): Handle Out of Stock

If at line 5 in the basic flow the quantity required is greater than the quantity available from stock, then
Line System Actor Action System Response
1 The system informs customer item is out of
stock.
2 The customer subscribes item notification
using email address, to be informed when
product is available
The use case terminates / The use case restarts at line 2

Alternate Flow (AF4): Delete/Update an Cart Item

If between line 3 and 5 of the basic flow , the customer updates the quantity of item, then
Line System Actor Action System Response
1 The system deletes/updates currently selected

Author: Fagoroye Ayodeji Page 3 of 8 Printed: 04/11/2010

Online Clothing Shop

Document Type: Use Case Document

item in cart/order
The use case terminates / The use case restarts at line 2

Alternate Flow (AF5): Handle Credit Card Failure

If at line 5 of the basic flow, the card s found to be invalid
Line System Actor Action System Response
1 The system displays the message ‘Invalid Card’
to the customer
The use case restarts at line 5

Alternate Flow (AF5): Cancel Order Processing

Alternate Flow (AF5): Add Charge for Delivery

Business Rules:
1 Out of Stock items must be displayed in red.

2 The system must show any changes that occur to available stock whilst the order is being created

Non Functional Requirements:

1 The use case must complete in the fewest possible number of keystrokes - usability

Data Issues:
1 It must be possible to enter the product number either using a barcode scanner or via the keyboard

Author: Fagoroye Ayodeji Page 4 of 8 Printed: 04/11/2010

Online Clothing Shop

Document Type: Use Case Document

Activity Diagram

Author: Fagoroye Ayodeji Page 5 of 8 Printed: 04/11/2010

Online Clothing Shop

Document Type: Use Case Document

Normal Scenario
1. Customer enter login information

2. System display product menu

3. Customer add items to shopping cart

4. System display message indicate the item added to shopping cart

5. Customer proceed to checkout

6. System ask user provide shipping and billing information

7. Customer provide shipping and billing information

8. System confirm the shipping information, process the order and ship out the items
9. Customer receive the items

Author: Fagoroye Ayodeji Page 6 of 8 Printed: 04/11/2010

Online Clothing Shop

Document Type: Use Case Document

Author: Fagoroye Ayodeji Page 7 of 8 Printed: 04/11/2010

Online Clothing Shop

Document Type: Use Case Document

Author: Fagoroye Ayodeji Page 8 of 8 Printed: 04/11/2010