Skip to main content

Patterns for e-business
for new IT solutions

Attention - major enhancements to P4eb

The original P4eb web site design was built to support solution architectures for new IT solutions. This approach is still supported by using the left hand navigation bar on this and subsequent pages.

The 2010 revision of the P4eb web site design was built to support solution architectures for re-engineered or enhanced as well as new IT solutions. To learn the new approach please follow (and perhaps bookmark) the link to the revised home page.

Tab navigation

Navigating you to the next generation of e-business solutions

Patterns for e-business are a collection of reusable assets that can help speed the process of developing new e-business solutions. They provide solution architecture patterns at different levels of abstraction. These different levels are relevant to different viewpoints - business view, developer view, system view, implementor view. This site breaks down these reusable assets into the following elements:

The Patterns leverage the experience of IBM architects to create solutions quickly, whether for a small local business or a large multinational enterprise. As shown in the following figure, customer requirements are quickly translated through the different levels of Patterns assets to identify a final solution design and product mapping appropriate for the solution being developed.

Process of using the patterns

Select a Business/Integration/Composite pattern that meets the customer requirements and pick then the appropiate Application pattern, Runtime pattern and Product mapping.

The seven Business patterns have been revised. See the article 'The revised P4eb Business patterns and the scenario decomposition framework' on the explanation of the revised scenario decomposition framework.

For a full understanding of the relationships between the Composite, Business and Integration patterns, review the book Patterns for e-business: A Strategy for Reuse (See right column "New or updated").

Business patterns

Business patterns highlight the most commonly observed interactions between Users, Businesses, and Data. They are the fundamental building blocks of most e-business solutions, and describe the interaction between the participants in an e-business solution. For the seven revised Business patterns see Business patterns for Simple Implementations or 'The revised P4eb Business patterns and the scenario decomposition framework'.

Integration patterns

Complex e-business solutions can be built by combining multiple Business patterns together. This is accomplished by using Integration patterns as the "glue" between Business patterns. Integration patterns are differentiated from Business patterns in that they do not themselves automate specific business problems. Rather, they are used within Business patterns to support more advanced functions, or to make Composite patterns feasible by allowing the integration of two or more Business patterns.For the two Integration patterns see Integration patterns for Advanced Implementations.

Composite patterns

Composite patterns combine Business patterns and Integration patterns to create complex, advanced e-business applications. Of course, there are numerous potential combinations of Business patterns and Integration patterns, but only a limited number of Composite patterns documented on this Web site. A solution design composed of these multiple building blocks is only considered a Composite pattern when it is recurrently employed to solve the problems of businesses across a wide range of industries. Examples of such Composite patterns include the four documented on this site:

  • Electronic Commerce
  • e-Marketplace
  • Portals
  • Account Access

Custom designs

Custom designs, like Composite patterns, combine Business patterns and Integration patterns to create complex, advanced e-business applications. Custom designs are solutions that have not been implemented to the extent of Composite patterns, however. Custom designs can be developed to solve one specific company's e-business problems, or perhaps several enterprises with similar problems. This purpose can prove incredibly valuable, of course. But, Custom designs do not meet the higher qualifications of a Composite pattern, and do not give as great a reassurance of reusability, because they have not been "recurrently employed to solve the problems of businesses across a wide range of industries." However, as the Custom designs detailed on the Patterns for e-business Web site are used more and more by diverse developers, vocal about the benefits and limitations of these solutions, these custom designs might eventually achieve the status of Composite patterns.

Application pattern

Atomic application patterns provide a further decomposition of eleven of the Logic patterns.

These more specific patterns can be used to perform both a decomposition of the existing IT subsystem and a decomposition of the planned enhanced IT subsystem. In the latter case the Atomic application patterns can provide a linkage to discover possible product mappings and related assets for implementing these products as part of an enhanced new or existing subsystem being developed.

Runtime pattern

The Runtime pattern uses nodes to group functional requirements. The nodes are interconnected to solve a business problem. An Application pattern leads to an underpinning Runtime pattern.

Begin the process

Depending on your experience with the P4eb web site and the progress of the application development process, review:

A note on reusing graphics or content

You're welcome to reuse the pictures or content from the developerWorks Patterns for e-business Web site if you display the IBM copyright notice with them.


© IBM Corporation 2004, 2010. All rights reserved. Java and all Java-based trademarks and logos used on this site are trademarks of Sun Microsystems, Inc. in the United States and/or other countries. All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

New or updated

Resources

Content navigation