...........

1. The Next GEN POS
System
GROUP PRESENTATION
SUBJECT NAME : Object-Oriented Analysis and Design
SUBJECT CODE : 191CSC502T
GROUP NUMBER : 08
GROUP MEMBERS :
* SRIRAM.R
* YASWANTH
* YOGESHWAR
* SASWATH
* THOTHIT HEWIN
* YUVAN

2. About this template
INDEX :
2
 Next Gen POS System
 Important Features
 User Level Goals
 Case Study Focus
 Types Of POS System
 Case Study

3. About this template
Next Gen POS System
3
 The case study is the Nextgen point-of-sale(POS)
system.
 There are very interesting requirement and design
problems to solve.
 A POS system is a computerized application used (in
part) to record sales and handle payments; it is typically
used in a retail store.
 It includes hardware components such as a computer
and bar code.
 Scanner, printer and software to run the system.

4. About this template
Next Gen POS System
4
 These systems must be relatively fault-tolerant.
 It interfaces to various service applications, such
as a third-party tax calculator and inventory
control.
 we will need a mechanism to provide this
flexibility and customization.
 Applications generally can be divided into 3 layers
 User interface
 Application logic
 Other components/layers

5.  A POS system increasingly must support multiple and variedclient-side
terminals and interfaces.
 These include a thin-client Web browser terminal, a
regular personalcomputer with something like a Java Swing
graphical user interface,touch screen input, wireless PDAs, and so
forth.
 This commercial POS system that we will sell to different clientswith
disparate needs in terms of business rule processing.
Each client will desire a unique set of logic to execute at
certainpredictable points in scenarios of using the
system, such as when a newsale is initiated or when a new line item
is added. 5
Important Features

6. You can also split your content
User Level Goals
6
•Cashier: process sales, handle, returns, cash in, cash out.
•System administrator: manage, users, security, system tables.
•Manager: startup, shut down.
•Sales activity system: analyze sales data.

7. In two or three columns
 A typical object-oriented information system is designed in terms of several
architectural layers or subsystems
 User Interface — graphical interface; windows.
 Application Logic and Domain Objects — software objects representing
domain concepts (for example, a software class named Sale) that fulfil
application requirements.
 Technical Services — general purpose objects and subsystems that provide
supporting technical services, such as interfacing with a database or error
logging. These services are usually application-independent and reusable
across several systems
7
Case Study Focus

8. In two or three columns
◉ Mobile POS
A Mobile POS system or MPOS uses an electronic device such as a
smartphone, tablet, or another mobile device as a terminal at which you can attach a credit
card reader. It is highly portable and allows you to attach other peripheral devices such as
barcode scanners and receipt printers.
◉ Terminal POS
A terminal POS is a software/hardware-based system that carries add-on
peripherals such as barcode scanners, credit card readers, receipt printers, and cash
drawers.
◉ Cloud POS
A cloud POS is an online or web-based POS which can be easily used
with your existing hardware such as a computer, tablet, and printer.
8
Types Of POS System

9. In two or three columns
 Stakeholders and Interests:
• Cashier: Wants accurate, fast entry, and no payment errors, as cash drawer shortages
are deducted from his/her salary.
• Salesperson: Wants sales commissions updated.
• Customer: Wants purchase and fast service with minimal effort. Wants easily visible display
of entered items and prices. Wants proof of purchase to support returns.
• Company: Wants to accurately record transactions and satisfy customer interests. Wants to
ensure that Payment Authorization Service payment receivables are recorded. Wants some
fault tolerance to allow sales capture even if server components are unavailable.
9
Case Study

10. In two or three columns
• Manager: Wants to be able to quickly perform override operations, and easily debug
Cashier problems.
• Government Tax Agencies: Want to collect tax from every sale. May be multiple
agencies, such as national, state, and county.
• Payment Authorization Service: Wants to receive digital authorization requests in the
correct format an protocol. Wants to accurately account for their payables to the store.
• Success Guarantee: Sale is saved. Tax is correctly calculated. Accounting and
Inventory are updated. Commissions recorded. Receipt is generated. Payment authorization
approvals are recorded.
10
Case Study

11. In two or three columns
 Customer arrives at POS checkout with goods and/or services to
purchase.
 Cashier starts a new sale.
 Cashier enters item identifier.
 System records sale line item and presents item description, price,
and running total. Price calculated from a set of price rules. Cashier
repeats steps 3-4 until indicates done.
 System presents total with taxes calculated.
11
Main Success Scenario (Basic Flow)

12. In two or three columns
 Cashier tells Customer the total, and asks for payment.
 Customer pays and System handles payment.
 System logs completed sale and sends sale and payment
information to the external Accounting system (for accounting and
commissions) and Inventory system (to update inventory).
 System presents receipt.
 Customer leaves with receipt and goods (if any)
12
Main Success Scenario (Basic Flow)

13. In two or three columns
13
Use Case Diagram

14. 14