Presentation Transcript

1. Point of Sale (POS)

   Presented By : Hieu Nguyen KanjanaPatcharaprasertsook AchirayaHusadinvichai SasapinWatanesk for cosmetic store
2. Table of Contents Project Overview Use Cases Context Diagram Domain Model List of Requirements
3. Project Overview
4. Use Case Overview UC1 : Checkout Item UC2 : Process Credit Card Payment UC3 : Register Membership UC4 : Refund Item UC5 : Process Sales Report
5. USE CASE1: Check-out Item Goal: Sales transaction is accurately processed. Scope: POS system Level: User goal Primary Actor: Cashier Main Success Scenario: Cashier enters item ID. System displays item description, price, and running total. Cashier repeats step 1-2 until the ID of all items are entered. Cashier enters membership ID or discount coupon code. System calculates tax and displays total. Cashier selects payment method. System processes payment. System saves sales transaction. System updates accounting, commission, and inventory. System generates receipt.
6. USE CASE 2: Process Credit Card Payment Goal: Credit card payment is approved Scope: POS system Level: Sub-function Primary Actor: Cashier and Customer Main Success Scenario: System displays the sales amount and a payment confirmation. Customer selects "yes” System displays "Swipe your card.” Cashier swipes a customer's credit card at the card reader. System submits the request credit card authorization with credit card data, sales amount and a terminal id to the bank. System receives an approval code from the bank. System displays "Enter your signature" at the monitor. Customer signs at the monitor and selects "Enter". System displays "Transaction is processed”.
7. USE CASE 3: Register Membership Goal: New member is added to the system successfully. Scope: POS system Level: Sub-function Primary Actor: Cashier Main Success Scenario: Cashier enters customer's information: name, address, birth date, and email address. Cashier brings out a new member card and enters the card id into system. System records the new member. System sends  the welcome letter to customer's email. System displays "record is added successfully". Cashier gives the customer the member card.
8. USE CASE 4: Refund Item Goal: Refund for the items from previous sales transaction has been successfully processed. Scope: POS system Level: Sub-function Primary Actor: Cashier Main Success Scenario: Cashier enters receipt ID. System displays sales transaction. Cashier enters item ID.Cashier repeats step 3 until the IDs of all items are entered. Cashier selects "complete". System displays total. Cashier selects "process". System processes the refund. System saves sales transaction. System updates accounting, commission, and inventory. System generates receipt.
9. Use Case 5: Process Reports Goal: Reports are generated accurately and timely. Scope: POS system Level: User goal Primary Actor: Store Manager or Owner Main Success Scenario: Owner or Store Manager logs into the system with special access permission in order to see the menu for generating the report. Owner or Store Manager selects among the available reports to generate. Owner of Store Manager inputs the date range for the report to be produced. System generates and presents the report on the screen displaying title, description, total, revenue, expense, profit, tax summary. Owner or Store Manager selects to print the report System reminds the Owner or Store Manager to log out of the system.
10. Other potential use cases check-out item, refund item, discount sale, process payment, add member, edit member, remove member, add user, edit user, remove user, user login, user logout, admin login, admin logout, add commission, update accounting, update inventory, search inventory, print receipt, view sales report, view commission report, view sales trend, view sales statistics,
11. Context Diagram
12. Domain Model
13. Requirement List Functional Requirements POS services: sales transaction The cashier shall be able to search for the item by product number or/and product name The cashier shall be able to add item to the shopping cart The cashier shall be able to remove item from the shopping cart. The system shall calculate and apply taxes, and discounts when add or remove item The cashier shall be able to cancel the sales The system shall decrease inventory on sales The cashier shall be able to insert the customer membership number The system shall calculate changes when customer pays by cash. The system shall print the receipt with the list of sales item, quantity, price and total payment authorization The system shall verify the credit card information with the bank When paying by credit card, system shall provide form for customer to sign the authorization.
14. Requirement List (cont.) return handling The system shall increase inventory when receive return The system shall make a store credit refund to the customer when the item is returned membership management The cashier shall be able to add, edit or remove customer information The store manage shall be able to send promotional email to customer discount management The store manager shall be able to add, edit or remove the discount Inventory management: inventory availability The cashier shall be able to view the product quantity Reporting services: sales statistics analysis The system shall generate the top sales item and category based on the last year sales sales and financial reports The store manager shall be able to generate sales report with the sales item, total. The system shall display the differences of cost and sales price of the item
15. Requirement List (cont.) Administrative management: user roles (owner, store manager, cashier, etc) The system shall allow the system administrator with an account to log into the POS system to add, edit, and remove the users security levels  The system shall allow the cashier with an account to log into the POS system to process the sales The system shall allow the store manger or the owner with an account to log into the POS system to view reports, create discount, and manage users. sales and commission tracking The manager shall be able to view the sales and the name of cashier on each sales daily, weekly, monthly, and yearly The system shall calculate the sales commission for each cashier The manager shall be able to set the commission rate.
16. Requirement List (cont.) Non-functional Requirements Availability The system shall be 99.9% available during the store’s opening hours. The system shall be able to recover from system crash or hang within 5 minutes. Performance Data retrieval time when scanning item shall not exceed 2 seconds. Sales transaction shall be updated within 5 seconds. Security Credit card information shall be validated with payment authorization system to ensure that the card owner is authorized to use the card. Data that are transferred to/from other systems shall be encrypted. Usability Each button on the screen shall be represented using straightforward term or icon. The system shall provide meaningful error messages. Each task or activity shall be carried out by user within 10 steps.
17. Requirement List (cont.) Maintainability Each error or exception message shall include a unique identifier to help specify what the problem is and where it was found. Each software module shall have comment section at the beginning of the module for describing the functionality of that module. Function calls shall be nested at most 3 levels deep. Naming convention shall be maintained throughout the entire program. Testability The system shall offer the ability to change setting and configuration. Real-time monitoring of the system shall be provided. Other non-functional requirements The hardware materials shall be bio-degradable, environmental friendly, and energy efficient.
18. Question ?