Event-Centric

The Event-Centric business pattern (aka Data-to-Business, Data-to-User, Data-to-Data) captures the essence of data events (which may have initially originated from a device, application, user, data store or clock) and event detection logic which may conditionally discard the event, initiate an event-related process, alert a user or update a data store.

• Cross Industry Examples
  • Device threshold management
  • Error detection and support
• Industry-Specific Examples
  • Retail
    • Data-driven stock replenshment
    • RFID applications
  • Financial
    • User stock price alerts
    • Fraud detection
    • Online customer behaviour
  • Manufacturing
    • Sensor and control solutions

If you're not yet sure that your business problem can be solved by the functionality enabled through a Event-Centric solution design, the Event-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 Event-Centric business pattern can provide an appropriate solution design for your business need, the next step is to select an Application pattern. The Event-Centric business pattern can be implemented using any one or more of three different Application patterns, 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

• Introduction

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

• Feasibility:
  This material will help you determine the high-level shape of a Event-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.