Scribd
Upload
3K views5 pages

Point of Sale Terminal Management System Construct A Design Element For Point

The document describes a point-of-sale terminal management system that allows customers to purchase goods. It includes: 1) A cashier who records item and price information for a customer's purchase and displays totals. 2) The customer choosing a payment type (e.g. cash, credit) and the cashier accepting payment. 3) The system generating a receipt, updating inventory, and handing the receipt to the customer.

Uploaded by

darshana gulhane
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
3K views5 pages

Point of Sale Terminal Management System Construct A Design Element For Point

The document describes a point-of-sale terminal management system that allows customers to purchase goods. It includes: 1) A cashier who records item and price information for a customer's purchase and displays totals. 2) The customer choosing a payment type (e.g. cash, credit) and the cashier accepting payment. 3) The system generating a receipt, updating inventory, and handing the receipt to the customer.

Uploaded by

darshana gulhane
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Point of Sale Terminal Management System Construct a design element for Point-of-sale

terminal management system that can be used for buying and selling of goods in the retail
shop.
When the customer arrives at the post check point with the items to purchase. The
cashier records each item, price and adds the item information to the running sales
transaction. The description and price of the current item are displayed. On completion of
the item entry the cashier informs the sales total and tax to the customer. The customer
chooses payment type (cash, cheque, credit or debit). After the payment is made the
system generates a receipt and automatically updates the inventory. The cashier
handovers the receipt to the customer.
Inclusion
• The customer chooses the payment type and the cashier will accept the payment and
initiates the transaction.
Exclusions
• No need to model secondary actor for inventory updates.
login

dashboard

record item record price

desk
price
displayed

payment

cash debit/credit cheque

generate update
receipt inventory

give receipt
to customer

ACTIVITY DIAGRAM
Use case diagram

SPECIFICATION DOCUMENT
Use Case Name
Check out
Summary
Customer finishes purchasing items and make payment
Actors
Store Customer and Cashier
Preconditions
Customer queue up to reach POS terminal and cashier is available
Description
1. Customer arrives at POS terminal with all items to be purchased
2. Cashier login and starts new sale
3. Cashier scans the items to be purchased using bar code scanner
4. System retrieves item specifications from catalogue and records sale line item, and
presents description, price, quantity and running total. Cashier repeat until last item is
scanned.
5. System calculates total price with taxes and display to customer
6. Cashier asks the mode of payment
7. Customer selects mode and make payment, and system handles the payment.
8. System records completed sale and sends sale information to the external Inventory
system for stock update.
9. System presents the receipt.
10. Customer leaves with receipt and all goods purchased.
Alternatives
1. Customer cancels the transaction
2. Cashier suspends the sale
3. Cashier login failed.
4. System hangs up or system crashes.
5. Customer chooses to pay by cash but don’t have enough cash
Post Conditions
Payment is approved. Sale is recorded and saved in the system. Receipt is printed and
inventory is updated.

General Use Case


Now I present to you the general use case of the POS (Point of Sale) System. This diagram
shows the general processes or function that the system could do that is based on the
transactions done from monitoring of product information and sales which are basis for the
POS management.
1. General use case is the most common application of a use case diagram. The
use case diagrams depict the system’s main components as well as the flow
of information between them.

With the help of this general use case, the programmer will have the basis on
what could be put into consideration in creating the Student Registration
system.

Monitor and Manage Purchasing’s Information and Status

This is where the admin manages the important information of the


purchasing that will serve as basis during the sales processing and
monitoring. These information will be based from the customers’ purchases.

1. As you can see the purchasing information should be encoded to the system.
The system then will monitor its details to validate it and then saves the data.

Manage Products Info and Status


This process involves the encoding of the basic information of each product offered to
determine the price and the count of the sales.

Manage Sales Information


This process explains about how the admin manages all the transaction that are related to
the sales and to determine the count of product sales in a certain date. It is essential to the
system to automate the monitoring of sales per purchase.

You might also like