Filter by:

Use Case Presentation

Use Case Presentation

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


1. Use Case Title:

Purchase Product

2. Use Case ID:

UC-01

3. Actor(s):

  • Primary Actor: Customer

  • Secondary Actor: Payment Gateway, Inventory System

4. Stakeholders and Interests:

  • Customer: Wants to purchase products easily and securely.

  • Retailer: Wants to ensure transactions are processed smoothly and inventory is updated.

  • Payment Gateway: Ensures secure and successful payment transactions.

5. Preconditions:

  • Customer is logged into the platform.

  • Customer has a valid payment method on file.

  • Product is available in inventory.

6. Postconditions:

  • Product is purchased and payment is processed.

  • Inventory is updated to reflect the purchase.

  • Customer receives an order confirmation.

7. Basic Flow (Main Success Scenario):

  1. Customer browses the online catalog.

  2. Customer selects a product and adds it to the shopping cart.

  3. Customer reviews the shopping cart and proceeds to checkout.

  4. Customer enters shipping and payment information.

  5. System validates the payment information and processes the payment.

  6. Payment Gateway confirms the payment.

  7. System updates inventory to reflect the purchased product.

  8. System sends an order confirmation to the customer.

  9. Customer receives the order confirmation email.

8. Alternative Flows:

Invalid Payment Information:

  1. Customer enters incorrect payment details.

  2. System prompts customer to correct payment information.

  3. Customer re-enters payment details and resubmits.

  4. Return to step 5 of the Basic Flow.

Product Out of Stock:

  1. Customer attempts to purchase a product that is out of stock.

  2. System notifies customer that the product is out of stock.

  3. Customer may choose to remove the product or select an alternative.

  4. Return to step 2 of the Basic Flow.

9. Special Requirements:

  • The system must ensure payment information is encrypted and secure.

  • The platform must be compliant with relevant e-commerce regulations.

10. Assumptions:

  • The customer has internet access and a compatible device.

  • The platform is operational and accessible.

11. Related Artifacts:

  • Wireframes of the checkout page.

  • Payment gateway integration documentation.

  • Inventory management system specifications.

12. Glossary:

  • Payment Gateway: A service that authorizes and processes payment transactions.

  • Inventory System: A system that manages and tracks product stock levels.

Use Case Templates @ Template.net