High-Level Use Case

Prepared by: [Your Name], [Your Title]

[Your Company Name]

Primary Actor

Registered Customer

Stakeholders and Interests

• Customer: Wants to purchase products quickly and effortlessly.

• System: Ensures the process is secure and efficient.

• Retailer: Wishes to maximize sales and customer satisfaction.

Preconditions

• Customer is logged into the system.

• Customer has registered with valid payment information.

Postconditions

• Product is purchased and order confirmation is sent to the customer.

• Inventory is updated to reflect the purchase.

Basic Flow

1. Customer searches for the desired product.

2. Customer selects the product from the search results.

3. System displays the product details.

4. Customer adds the product to the shopping cart.

5. Customer proceeds to checkout.

6. System prompts for shipping and payment information.

7. Customer enters the required information and confirms the purchase.

8. System processes the payment and updates the order status.

9. System sends an order confirmation email to the customer.

Alternative Flows

AF1: Product Not Found

• 1a. If the product is not found, the system displays an error message.

• 1b. Customer may refine the search criteria or browse categories.

AF2: Payment Declined

• 7a. If the payment is declined, the system displays an error message.

• 7b. Customer may provide alternative payment details or contact customer support.

Special Requirements

• The system must comply with PCI DSS for payment processing.

• The web interface should be responsive and accessible.

• Order processing should be completed within 2 seconds.

Frequency of Use

Multiple times per day for an active online shopping site.

Assumptions

• Customers have stable internet connections.

• The product is in stock.

Use Case Templates @ Template.net