For further background and definitions click here
Scope
The scope of business requirements addressed by the P4eb architectural process has always included end-to-end subsystems, integration subsystems and combined subsystems as defined here.
Process
The P4eb solution architecture process has always been closely aligned with the classic architectural techniques of problem decomposition, solution abstraction (using reusable patterns), solution composition, solution refinement (using a reusable pattern hierarchy), and solution deployment planning.
Original Process
The original P4eb solution architecture process for new IT solutions applied these techniques in a simple linear fashion
Revised process
In order to update the P4eb solution architecture process for business requirements including new and enhanced IT solutions it has been necessary to develop additional patterns and visual decomposition/integration frameworks.
Applying the revised P4eb
The combined patterns and visual frameworks can be used by architects in many disciplines. Recommendations on their use by solution and integration architects can be found here.
Scenario decomposition summary
Step 1 applies these classic architectural techniques to analyze and decompose a business scenario into a number of subsystems characterized by a combination of existing and new Foundation E2E Business patterns and Front-end & Back-end Integration patterns. For each subsystem characterized by a new Foundation E2E Business pattern, the Foundation E2E patterns and asset hierarchy can be used to refine the subsystem resulting in a proposed product list (Iteration 1)
This step is more fully described together with a worked example on the Step 1 Scenario decomposition 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.
