Use-Case Diagram “Make A Sale”This use case documents the requirements for how the system needs to make a sale. A sale consists of many sale details (line items). Each line item is scanned so that the price can be looked up. Once the items are added to the sale, it is totaled and the tax is added. At this point, it is time to take in the payment. This can be in the form of cash, credit, debit, etc. Upon a successful sale, the product inventory is updated based on the quantities sold for this sale.
Description: |
Use Case scenario |
Author: |
Jon Kern |
Priority: |
high |
Difficulty: |
low |
Number: |
3.1 |
Note1: |
Right-click, choose
"Hyperlink To" menu,
select the hyperlink and
watch what happens. |
Diagram Node Summary |
|
Actor: The Cashier is the actor responsible for interacting with the customer and the point of sale system, ringing up the sale. |
|
Actor: This represents HAL, our inventory computer system. |
|
System Boundary: This represents the system we are building, the Point of Sale System. |
|
Use-Case |
|
Use-Case |
|
Use-Case |
|
Use-Case: This emplys bar code reader type of technology to let the system know what product is being purchased. |
|
Use-Case: Take in payment (in the form of cash, check, credit, debit, and work in kind). |
|
Use-Case: Total the items of the sale, apply taxation as well. |
|
System Boundary: The Product System boundary encompasses the entire inventory subsystem. |
|
Use-Case: Implement a set of tax algorithms for each state. |
|
Use-Case: Do a lookup of the current price for the item. |
|
Use-Case: Once the sale is complete, the inventory must be updated to reflect the transaction. |
Diagram Node Detail
Actor "Cashier"The Cashier is the actor responsible for interacting with the customer and the point of sale system, ringing up the sale.
URL Links
Actor "Inventory System"This represents HAL, our inventory computer system. Though he usually prefers XML messages, he can also read LIPS.
System Boundary "Point of Sale System"This represents the system we are building, the Point of Sale System. Use Cases appearing in this system boundary are to be considered as requirements to be supplied to the POS terminals.
Nested Nodes
Use-Case "Check"Nested in node:
Use-Case "Credit"Nested in node:
Use-Case "Debit"Nested in node:
Use-Case "Scan Product"Nested in node:
This emplys bar code reader type of technology to let the system know what product is being purchased. It may be better to call this "Identify Product" as a scan is merely a common technique (but by no means comprehensive).
Explanation: |
or "Identify" Product |
Pre-conditions: |
Product identifier must be obtained. |
Post-conditions: |
Product must be identified unambiguously. |
Normal Flow: |
- Manually select product
- Read identification label (generally UPC)
- wait for confirmation of proper scan
|
Alternate Flow: |
If confirmation not received for successful scan.
- Try again.
- Still no good, then invoke manual entry of UPC.
|
Use-Case "Take in Payment"Nested in node:
Take in payment (in the form of cash, check, credit, debit, and work in kind).
Use-Case "Total Items"Nested in node:
Total the items of the sale, apply taxation as well.
System Boundary "Product System"The Product System boundary encompasses the entire inventory subsystem. However, for the purposes of the POS system, we need only very little functionality.
Nested Nodes
Use-Case "Determine Tax"Nested in node:
Implement a set of tax algorithms for each state.
Use-Case "Price Lookup"Nested in node:
Do a lookup of the current price for the item. Need to take into account quantity discounts, date-based discounts, manufacturer specials, etc.
Use-Case "Update Product Count"Nested in node:
Once the sale is complete, the inventory must be updated to reflect the transaction.