Purchase Mechanism Use case
Purchase Mechanism Use Case
Created by: [YOUR NAME]
Company: [YOUR COMPANY NAME]
I. Use Case Overview
This Use Case describes the process by which customers of [YOUR COMPANY NAME] can purchase products or services through an online platform. This document aims to outline the steps involved from selecting a product to completing the purchase.
-
Use Case Name: Purchase Mechanism
-
Use Case ID: GO-007
-
Created by: [YOUR NAME]
-
Date Created: [Date]
-
Last Updated: [Date]
-
Version: 1.6
II. Actors
-
Primary Actor: Customer
-
Supporting Actors: Payment Gateway System, Inventory Management System
-
Secondary Actor: Customer Support
III. Preconditions
Before the purchase process begins, the following conditions must be met:
-
The customer must be registered and logged into the [YOUR COMPANY NAME] website.
-
All systems, including the Payment Gateway and Inventory Management, should be operational.
-
The product the customer wishes to purchase must be available in the inventory.
-
The customer must have an active internet connection.
IV. Postconditions
Upon successful completion of this use case, the following should be true:
-
The customer receives a confirmation email detailing their purchase.
-
The inventory is updated to reflect the purchased items.
-
The Payment Gateway successfully processes the payment without errors.
-
The system updates the inventory to reflect the purchased items.
V. Main Flow
|
Step |
Action |
Actor |
|---|---|---|
|
1 |
Customer browses the products on the [YOUR COMPANY NAME] website. |
Customer |
|
2 |
Customer selects the desired product. |
Customer |
|
3 |
Customer adds the selected product to the shopping cart. |
Customer |
|
4 |
Customer proceeds to checkout. |
Customer |
|
5 |
Customer provides shipping and payment information. |
Customer |
|
6 |
System processes the payment securely. |
System |
|
7 |
System generates an order confirmation. |
System |
VI. Alternate Flows
I. Order Modification
|
Step |
Action |
Actor |
|---|---|---|
|
1 |
Customer modifies the order by adding, removing, or changing the quantity of items in the shopping cart. |
Customer |
|
2 |
Customer proceeds to update the shopping cart. |
Customer |
|
3 |
Go back to Step 4 in the Main Flow. |
Customer |
II. Order Cancellation
|
Step |
Action |
Actor |
|---|---|---|
|
1 |
Customer cancels the order before it is shipped or delivered. |
Customer |
|
2 |
System cancels the order and refunds the payment. |
System |
VII. Exception Flows
-
If the selected product is out of stock after adding it to the cart, the customer is notified and prompted to either select a different item or cancel the order.
-
If the Payment Gateway system is down, the checkout process is paused and the customer is informed to try again later.
VIII. Extensions
-
Inventory Management: The system updates the inventory to reflect the purchased items, ensuring accurate stock levels.
-
Shipping and Delivery: The system arranges shipping and provides tracking information to the customer.
-
Return and Refund: The system manages the return and refund process if the customer is not satisfied with the purchased items.
IX. Special Requirements
-
The website must be accessible on both desktop and mobile devices.
-
All transactions must be secured with SSL encryption.
X. Assumptions
-
Customers have a basic understanding of online shopping processes.
-
Inventory levels on the website are updated in real-time.
XI. Notes and Issues
Pending issues to be resolved include the handling of high-volume traffic during sales or promotions and integrating more robust fraud detection mechanisms.
