Enterprise Process-Centric

The Enterprise Process-Centric pattern is relevant for end to end business processes where a business process manages the interactions between multiple intra-enterprise applications, services, sub-processes and users. Reliable integration of applications - be they legacy stovepipe applications, packaged software applications, or custom applications - requires the use of proven replicable patterns.

If you're not yet sure that your business problem can be solved by the functionality enabled through a Enterprise Process-Centric solution design, the Enterprise Process-Centric general guidelines page provides additional information on choosing this Business pattern. Business and IT drivers, the e-business context appropriate for this solution type, and additional solution details are discussed here.

If you've determined that the Enterprise Process-Centric business pattern can provide an appropriate solution design for your business need, the next step is to select an Application pattern. The Enterprise Process-Centric business pattern can be implemented using any one of four different Application patterns with a number of variations, providing solution flexibility so that the determined Business pattern can address the specific needs of the business process being automated.

• Patterns for e-business naming conventions

• New Application pattern

  Updated: 07-20-2010
  The Content-Centric BPM with ECM pattern has been added as a variation to the Enterprise Process-Centric::Parallel Workflow pattern.

• New Application pattern

  Updated: 03-12-2010
  The Content-Centric BPM pattern has been added as a variation to the Enterprise Process-Centric::Parallel Workflow pattern.

• New assignment

  Updated: 03-12-2010
  The Enterprise Process-Centric business pattern has been classified under the new Process-Centric business pattern.

• Introduction

  Updated: 03-12-2010
  The Enterprise Process-Centric business pattern has been introduced to P4eb.

• Feasibility:
  This material will help you determine the high-level shape of an Enterprise Process-Centric solution, and can ensure your approach looks similar to other successful implementations. Reuse of prior approaches can be an effective way to begin most major projects. Obviously, modifications will be needed for any unique requirements of a given set of partners. This pattern provides a drill-down from high-level architecture to low-level designs and guidance.

• Risk:
  Basing new projects on prior designs and ideas helps to lower the risk of failure. Creating or inventing approaches for each project tends to result in a lower success rate. Frequently, projects begun "from scratch" simply do not work and have major exposures in such areas as security, performance, availability, undefined requirements, and cost overrun.

• Cost-benefit:
  By starting with reasonably complete architecture you can save considerable development time and can obtain assurance that the end solution will have a much higher chance of success. Actual savings will vary, but project teams have realized a 10% to 50% reduction of work effort in their design and architecture phases alone.