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
- Getting started - selected tab,
- User requirements
- Using the web site
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:
- Business patterns identify the interaction between users, businesses, and data. Business patterns are used to create simple, end-to-end e-business solutions. These have been revised to include new Business patterns enabled by modern middleware (see this article for an explanation).
-
Integration patterns
(both Front-End and Back-End) connect other Business patterns together to create solutions with advanced functionality. Integration patterns are used to combine Business patterns in advanced e-business solutions.
- Composite patterns are combinations of Business patterns and Integration patterns that have themselves become commonly used types of e-business solutions. Composite patterns are advanced e-business solutions.
- Custom designs are similar to Composite patterns, as they combine Business patterns and Integration patterns to form an advanced, end-to-end solution. These solutions, however, have not been implemented with the frequency of Composite patterns, but are instead developed to solve the e-business problems of one specific company, or perhaps several enterprises with similar problems.
- Application and Runtime patterns are driven by the customer's requirements and describe the shape of applications and the supporting runtime needed to build the e-business solution.
- Product mappings to populate the solution. The product mappings are based on proven implementations.
- Guidelines for the design, development, deployment, and management of e-business solutions.
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.
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").
Begin the process
Depending on your experience with the P4eb web site and the progress of the application development process, review:
- "Using the web site"
- Select a pattern appropriate to your needs
- Use the shortcut links on the navigation menu to quickly jump to any area you have determined you would like to explore.
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.
