CSC/ECE 517 Summer 2008/wiki3 7 SHOP PAT

Problem Definition

Shopper pattern. The idea of a "shopping cart" is ubiquitous in e-commerce. This idea lends itself to abstraction in the form of a Shopper pattern. Find examples and descriptions that are suitable for teaching this pattern, if possible, including some non-obvious applications. Write up your findings in the form of a narrative.

Introduction

One of the most popular activities on the Web is shopping. It has much allure in it that one can shop at ones leisure at anytime. Literally anyone can have their pages built to display their specific goods and services. Consumers can easily search through a large database of products and services. They can see actual prices, build an order over several days. Customers can compare prices with a click of the mouse and buy the selected product at best prices. An approach for all these is to adopt Shopper Pattern. The main purpose of Shopper Pattern is to assist the consumer to obtain a collection of items from a set of providers which is achieved by introducing low coupling between the consumer and the provider.

Participants

• Consumer :provide a list of items and user is allowed to choose item among them.Then the price is scanned and placed in the shopping bag.

• Shopper: Browse through the item from the shopping list and search for the muliple provider for that particular item.Shopper may search the item on diffent basis ex: Brand name, lowest price.highest price etc.

• Provider:It keeps multiple items and make it available to shopper. At the same time assist the shopper in locating the other providers.

• ItemRequest: Requested item by th eshopper is identified.

• Item:The things that are a provider owns,described by an item request,a consumer request, and a shopper obtains.

Consequences

• Shopper pattern helps in decoupling the requesting object from the object that provide the requested items.
• The responsibilities can be moved for provider objects.the requesting application will not nee dto be modified.
• The provider objects can be rearranged without modyfying the requesting application.
• Optional items can be optimized in such a way so that the processing time will be required only if th eitem is present in the list.

Steps to remember in designing

• Standard icons and conventions:
• Avoid irrelevant links:
• Reveal structure:
• Leave breadcrumbs:
• Don't bury information
• Don't be mysterious:
• Provide help:

Reference

DesignSteps