Scribd
Upload
49 views4 pages

Ooad Ass2

This document summarizes an online shopping system by providing an introduction to next gen POS systems, describing the online shopping system class diagram and key entities such as customers, accounts, orders and payments. It also discusses future aspects such as a cashless society and challenges with traditional POS systems. The conclusion states that class diagrams are useful for understanding relationships between classes and finding mistakes.

Uploaded by

Ajithkumar S / CSE
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
49 views4 pages

Ooad Ass2

This document summarizes an online shopping system by providing an introduction to next gen POS systems, describing the online shopping system class diagram and key entities such as customers, accounts, orders and payments. It also discusses future aspects such as a cashless society and challenges with traditional POS systems. The conclusion states that class diagrams are useful for understanding relationships between classes and finding mistakes.

Uploaded by

Ajithkumar S / CSE
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/ 4

Synopsis:

1. Introduction to Next GenPOS System


2.Online Shopping System
3. Class diagram of Online Shopping System
4. Future aspect
5. Conclusion

Introduction to Next GenPOS System: -


Next-gen POS solutions are built on common mobile
technologies, often using Apple iPads as the core platform. iPads have
proven to be strong and resilient devices, able to withstand sustained
usage, particularly when coupled with supporting hardware such as
stands and cases.
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,
and software to run the system
This section presents a sample layers of classes diagrams.

Online Shopping System: -


Each customer has unique id and is linked to exactly
one account. Account owns shopping cart and orders. Customer could
register as a web user to be able to buy items online. Customer is not
required to be a web user because purchases could also be made by
phone or by ordering from catalogues. Web user has login name which
also serves as unique id. Web user could be in several states - new,
active, temporary blocked, or banned, and be linked to a shopping cart.
Shopping cart belongs to account.
Account owns customer orders. Customer may have no orders.
Customer orders are sorted and unique. Each order could refer to
several payments, possibly none. Every payment has unique id and is
related to exactly one account.

Each order has current order status. Both order and shopping
cart have line items linked to a specific product. Each line item is
related to exactly one product. A product could be associated to many
line items or no item at all.

Class diagram of Online Shopping System: -


Purpose: Provide top level use cases for a web customer making
purchases online.

Summary: Web customer  uses some web site to make purchases


online. Top level class diagram are View Items, Make
Purchase and Client Register.
Future aspect: -
A future of Next Generation Point Of Sale(POS) Software
provides a huge range of capabilities such as billing and order processing
sales monitoring and reporting, inventor, tracking, returns, analytics,
mobile connectivity, customer data management, and Loyalty programs.
Cashless society, cashier less shopping.
Challenges faced with traditional POS systems:
Capital intensive physical deployments, replacements and upgrades
High Installation, support, and maintenance costs
Limited interoperability with modern payment solutions

Conclusion: -
I conclude that the class diagram is a very useful for
understanding the relationship between the classes and an easy way to
find mistakes.
We model the objects that make up the system to display the
relationship between the objects, and to describe what those objects do
and the services that they provide.

You might also like