Skip to main content

Patterns for e-business
for new and enhanced IT solutions

Tab navigation

Combine Subsystems summary

Step 3 applies the classic architectural techniques to analyze every integration subsystem and identify the Atomic integration patterns required to combine two or more end-to-end subsystems. Then we use the Atomic integration pattern and asset hierarchy to refine the subsystem resulting in a revised proposed product list (Iteration 3).

This third step allows the architect to visualize and validate all the changes necessary to integrate the flows between every pair of subsystems.

It is hoped to update the P4eb web site over time to provide the Atomic integration pattern hierarchy to enable solution refinement of the Integration patterns down to candidate product mappings and related assets as shown below.

Process of using the patterns

This step is more fully described together with a worked example on the Step 3 Combine Subsystems page.

© 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