CS731 POS RetailWeb System Professor: Heng Ji Student: Neil Acampa

1
CS731POS Retail/Web SystemProfessor Heng
JiStudent Neil Acampa

• Enter Here

2
Project Goal

• Create a fully integrated POS/Retail System with
  both in Store and remote (Web) access.
• Maximize product exposure through the Web (Global
  Electronic visibility).
• Integrated Web site and Database to instantly
  reflects changes to System.

3
Project Goal

• Provide tools for Managers to make changes
  without IT support.
• Add dimension to data collection by tracking web
  based browsing habits.
• Improve Customer relationship by providing secure
  access to Account Information.
• Increase sales by allowing users remote access to
  System.

4
Long term Goal

• Create a Data Warehouse with Sales History data
  for trend analysis and forecasting.
• Use information gathered by tracking Web
  navigating history for customer profiling and
  marketing strategy

5
Motivation

• In order for a business to be competitive in the
  rapidly changing Market place both local and
  global access to products and services need to be
  available.
• Managers need many tools to easily customize
  aspects of the web to reflect BI decisions
  without waiting for IT intervention.
• Data collection through data warehousing and Web
  Statistics on customer purchasing habits and
  interest can be used for targeting, forecasting
  and increasing sales.
• Remote access to Customer/Product information is
  a useful tool for Sales force.

6
Project Goal

• Features for Management
• Web integration with Database insures customers
  have correct up to date information (i.e. Price,
  Stock balance, AR balance orders shipped.)
• Easy of Maintenance of Web Displays such as the
  control of Product lists (New , Favorite, Classic
  Product, discontinued)
• Sales reporting (summary and detail).
• Backend data warehouse for OLAP and trend
  analysis.

7
Project Goal

• Features for Customer
• Provides secure access to Account information
  from the Web.
• Provide Recommender Lists based on product
  interest and prior purchases.
• Provide ability to make Account changes such as
  address information.
• New Account application from the web.

8
Method of Software Development

• The method of developing this software will be
  the Evolutionary Method.
• Focus on Quick releases rather than a full blown
  package.
• Each release Adds value to the customer through
  automation.
• Each release is driven both by the specification
  and Customer feedback.
• Emphasis is on Flexibility.

9
Evolutionary Method

• Emphasis on Flexibility and Response to..

10
Evolutionary Method

• To natural changes .

11
UML

• The preliminary or initial requirements will be
  identified from Stories (a dialogue between the
  customer and programmer).
• Stories are on going conversations that serve as
  a token for planning and implementation.
• An Input/Output model will be created.
• Then the system structure and relationships will
  be modeled using UML class diagrams

12
Use Case Scenariosfor the Web

• Customers logging into the web will use their
  customer number and zip code.
• One time customers can submit orders on the web.
• Customers with a valid log in to the web can view
  and change address information
• Customers with a valid log in to the web can view
  sales orders by date, product number and status.
• Product on the web will be displayed in many ways
  such as all products, new line products, classic
  products, discounted products, favorite products
  and Product type.
• Managers can control web product display lists by
  setting various thresholds.

13
Use Case Scenariosfor the Web

• Once a product is discontinued it is no longer
  available on the web.
• Customers will received a discount for products
  in closeout status.
• Customers will receive an additional discount if
  one is set up in the customer database.
• Customers that have either purchased closeout
  product or shown interest will be provided with
  recommender lists.
• Once product is selected it is added to the Order
  form.
• Products can be removed once added to form.
• A quantity must be entered for each ordered
  product.

14
Use Case Scenariosfor the Web

• Line item Quantities should be checked against On
  hand
• Line item totals will display for each product.
• One time Customer entering orders on the web
  must enter customer information.
• Users with a valid logon to the web can view any
  customer and order information (optional)
• Payment through the web is by credit card only.
• A valid credit card number and date must be
  entered.
• Once the order form is submitted, the customer
  will received an email notification.
• The Order is then entered at the store level.
• Once the Order is entered it is available on the
  Web in Order inquiry.

15
Use Case ScenariosRetail

• Stories for Local Retail Store
• User id and password need to access the system on
  retail side.
• Need differing levels to authorization.
• Need to maintain Product, Customer, User Info
• Need to maintain State Tax information
• Need to track product sales by type and category.
• Need to track customers sales by showroom.
• Need to be able to Print table data.
• Need Order entry Program to enter and Maintain
  Orders.
• Charge tax based on State
• Check stock availability in Order Entry

16
Use Case ScenariosRetail

• Shipping charges will be based on flat fee for
  ground, next, second day.
• Allow deposits to be entered on Orders
• Allow for both customer and product discounts.
• Calculate the order total
• Check Credit limit for Customers in system
• Validate credit card and expiration date

17
Use Case ScenariosRetail

• Update data in Customer, Product and Order tables
  such as account receivable balance, stock
  balance, order status. Update Database.
• Capture summary sales by Customer, Product,
  Product category, Product Type and Showroom.
• Need sales reports (Summary and detail) for
  customer, product and order by Number, Name, Date
  etc.

18
Use Case Scenarios OLAP

• Need Sales history on Sales dollars and Units for
  trend analysis on many dimensions.
• Periodically Update Invoiced Orders.
• Time (month , quarter, year)
• Location (Showroom, State)
• Product (Type, Category, Item)
• Customer (Customer number)

19
Store Login User ID, Password Web
Login Customer No, Zip Web One time -No login
Register Customer Input Product Input User
Input State Tax Input Ship method Input Supplier
Input Order Entry/Store and Web
DATABASE
server
20
Class ViewTables

• In order to do OLTP the system will need various
  Entry and Maintenance programs. One of the goals
  is fast and efficient transaction processing and
  record retrieval aiming to minimizing data entry
  errors, and duplicate data entry by the use of
  tables.
• 1. Customer 5. State tax 9. Product Category
• 2. Product 6. Showroom 10. Product Type
• 3. User 7. Shipping
• 4. Order 8. Web Manager

21
Class ViewTables

• Each Entry and Maintenance program will allow
  users with the proper privileged to add, delete,
  edit, print, and update the database.
• Tables are incorporated as needed.
• Entry/Maintenance programs should be complete
  before Orders can be placed.

22
Class View methods

• Web Start up
• Customer Login
• Order Form
• Basic Product Display
• Goal Just to Submit Order from web to be
  entered on Site.

23
Class View methods

• Enhancements to Order Entry in each release. Keep
  incorporating table lookups and methods.
• Add enhancements to web.
• For example Manager changes cutoff date for new
  product display. Product list on web site
  changes.
• Manager reduces Cutoff for Year to date sales
  threshold for favorites product. List changes on
  web.
• User (employee) has remote access to system

24
Reporting

• Daily Reporting
• Reports are needed by all Departments.
• Display Order information by Customer, Product,
  Order date and Order Status.
• Slowly incorporate these on the web.

25
Time Line for Software Release
26
Time Line for Software Release