Use Case Scenario + UML Activity Diagram

Goals

The main goal is to implement the WIC Card program to the existing system.

WIC functionality helps the end-users (Customers) to acquire the preferential goods by a specific WIC Card.

Also, WIC functionality helps the Employees (Managers and Cashiers) to divide the list of products by the type (WIC or non-WIC) and trade them separately.

Main Actors

Functional Requirements - "WIC Payment" Use Case Scenario

Main Success Scenario

1. The Employee scans all the products from the Customer's basket.
2. The system displays the scanned products in the POS application and identifies all the scanned products are WIC.
3. The Employee chooses the WIC payment method.
4. The Customer swipes the WIC card through a WIC-payment terminal, enters a PIN and presses 'Enter' button on the WIC-payment terminal.
5. The system prints two slips: Beginning Balance & Benefits Utilized.
6. The Customer reviews the slips and confirms their willingness to continue WIC sale.
7. The Employee presses the 'Continue' button in the POS application.
8. The system makes the WIC payment and prints the Ending Balance slip.
9. The Employee chooses not to print the final sale receipt.

Alternative Flows

2a. The system identified all the products were non-WIC.

2a.1. The Employee chooses any other non-WIC payment method.

2a.2. Start of the "Non-WIC Payment" Scenario.

2b. The system identified the part of the scanned products was WIC and another part was non-WIC. 

2b.1. The Employee chooses the WIC form of payment first.

2b.2. Follow Steps 4 - 7.

2b.3. The Employee chooses any other non-WIC form of payment.

2b.4. Start of the "Non-WIC Payment" Scenario.

3a. The Employee chose to 'Suspend' the process.

3a.1. The system gave the ability to Employee to serve another Customer.

3a.2. Return to Step 1.

3b. The Employee chose any other non-WIC form of payment.

3b.1. Start of the "Non-WIC Payment" Scenario. 

7a. The Employee pressed the 'Cancel' button in the POS application.

7a.1. Return to Step 2.

8a. The system was failed to make the payment.

9a. The Employee chose to print the final sale receipt.

9a.1. The system prints the final sale receipt.

9b. The Employee chose to send the final sale receipt via email.

9b.1. The system sends the final sale receipt via email.

9c. The Employee chose to send the final sale receipt via SMS.

9c.1. The system sends the final sale receipt via SMS.

Business Rules

• the POS application can work with different types of products and identify are they WIC products or non-WIC ones.
• the POS application doesn't show if the product is WIC or non-WIC on the UI. 
• after the Employee finishes scanning all products from the Customer's basket, the system displays the different payment methods for these products.
• each specific WIC card contains the specific amount of WIC-products that are available for the specific Customer (available = the Customer can "buy"/get them for free).
• the WIC-products should be "paid" separately and the Customer uses the separate WIC-payment terminal for the WIC-sale.
• if the list of the scanned products contains both WIC and non-WIC items, the WIC items should be "paid" firstly (before any other payment methods: debit, credit, cash).
• if the other payment method was chosen, the WIC-product prices should be summarised with the non-WIC-product prices, and the Customer should pay for them in its entirety. 
• the WIC-products can't have taxes or/and discounts.

UML Activity Diagram - "WIC Payment" flow

Questions & Suggestions

Below is a list of questions to be addressed as a result of this requirements document: