21-04-2014, 05:00 PM
E-Patterns
E-Patterns.docx (Size: 35.6 KB / Downloads: 18)
Abstract
In this paper we present some patterns we found in well known e-commerce applications. First, we briefly characterize these applications as a particular case of Web software. We next review some Web patterns that can be used in E-commerce applications. Finally, we present five new patterns: Opportunistic Linking, Advising, Explicit Process, Easy Undo and Push Communication.
E-commerce applications present new challenges to the designer: we not only need to help the user find what he wants (a product he will buy) but also ease the shopping process. For example we should keep him informed about new releases and, last but not least, keep him in the electronic shop for a longer time.
Summary
The paths to creating e-businesses are repeatable. Many companies assume that they are unique and that therefore very creation of an e-business has to be learned as you go. While this may be encouraged by some service providers and programmers (because it is both profitable and allows programming artistic flair), IBM has learned that in fact, there are lessons and architectural paths or patterns that can be discerned from all these engagements. Whether your company is a startup or has extensive legacy applications, these patterns allow you to reuse existing technologies so that your projects can be completed quickly.
History of Pattern
They decided to try out the pattern stuff they'd been studying. Like Alexander who said the occupiers of a building should design it, Ward and Kent let representatives of the users (a trainer and a field engineer) finish the design.
Ward came up with a five pattern "language" that helped the novice designers take advantage of Smalltalk's strengths and avoid its weaknesses:
Window Per Task
Few Panes
Standard Panes
Nouns And Verbs
Short Menus
Ward and Kent were amazed at the (admittedly Spartan) elegance of the interface their users designed. They reported the results of this experiment at OOPSLA 87 in Orlando [4]. They wrote up a panel position, and presented at NormKerth's workshop on where do objects come from? They talked patterns until they were blue in the face, and got a lot of agreement, but without more concrete patterns nobody was signing up.
Meanwhile, ErichGamma was busy writing and reflecting about object-oriented design in ET++ as part of his PhD thesis. Erich had realized that recurring design structures or patterns were important. The question really was how do you capture and communicate them.
BruceAnderson gave a talk at TOOLS 90 at which ErichGamma was present; Erich liked the talk. Bruce gave a paper at EcoopOopsla90 (Ottawa) and ran a BOF called Toward an Architecture Handbook where he, ErichGamma, RichardHelm, and others got into discussions about patterns. That was the first time that Richard and Erich met, and they realized they shared common ideas about the key ideas behind writing reusable OO software.
E-channel Compression
As the name itself suggest that the channel is compressed the meaning the unwanted and redundant steps in the channel are eliminated. A step in the channel becomes redundant when the cost incurred on it is more than the value added by the channel.
In such a case it prudent to eliminate such a step and compressed the channel. the advantage of eliminating the undesired steps in the channel is that a relationships with the end users become more direct which help him forging a relationship with them which proves to be beneficial in the long run of the business. Traditional channel have given way to e-channels which have enhanced the channel efficiency by managing enquires, resolving conflicts and monitoring sales. e channel also help customers by enabling them to help themselves. The biggest advantage is that e-channels are available every time. Which is very much the need of the market and leads to satisfied customers?
CONCLUSION
The most significant contributing factor to this complexity is the high degree of integration required by virtually all the systems that contribute to the basic act of buying and selling goods and services. This integration is not confined to systems within the enterprise, but increasingly includes systems belonging to trading partners, third-party trading exchanges and perhaps most importantly those that face out to the customer.
The Patterns development process is a live project, ever-evolving and being updated as new products are released and are used in the building of real applications. IBM has constructed the Patterns and the Patterns Web site to enable development teams to work through the development process using their preferred methodology or the methodology suggested by consultants engaged to assist in the project. Application development, regardless of the complexity of the project or the methodology, will benefit greatly by employing a best-practice approach to the process.