#BRF Business Event Driven Enterprises Rule!

Brian Dickinson of Logical Conclusions is leading this session.

He explains his own definition of events (being an author) and says that he is happy to see how many talks mention events at this conference. Being an event driven enterprise will set you apart from your competition.

An event is anything that happens beyond the are of study that requires or produces a response inside the area of study. – B. Dickinson

All systems have a stimulus-response mechanism. Events make the world go round. In one process view the world consists of a mass of things (events) happening through time. We select the ones we are interested in (sounds like patterns to me).

In the business world and event is what it wishes to respond to from the outside world. The enterprise has no control over theses external customer event, it simply responds to the arrival of the stimuli from the events.

Each external need to which we respond is called an event. An enterprise’s response to an event is a 3 tiered structure: selected events, business analysis, system design and implementation.

There has been a fragmentation of the systems at the implementation which created boundaries at the design level based on the departments, but that is not how things should. The groupings were based on skills of the people that needed the systems.

The boundaries are “historical” (he used hysterical) and using events should allow business to see through these old and outdated boundaries. Engineering the enterprise should be based on events.

Flavors of event:

  • Business Events: to which the business wishes to respond
  • Dependant Events: to which and enterprise responds to satisfy its business events
  • Regulatory Events: To which an enterprise is required to respond

System events are invented at design time. Strategic events are those that dictate the contents of the enterprise’s policy.

Gather 6 things for analysis of events

  • Source
  • Stimulus
  • Processing
  • Memory
  • Response
  • Recipient

You can get rid of “files”  if there is not “intersection” between 2 events.

Let the “data” flow through with no slow down and do your analysis to allow this. The boundaries should not slow down the processing of the events.

If it takes more than “minutes” to get through your company, he says that you are not using event driven partitioning. Don’t combine events, Don’t break events.

Very interesting talk although I wish it would have been longer because we barely skimmed the surface of his topic.

Series Navigation<< #BRF Keynote: Smarter Systems for Uncertain Times#BRF Standards for Business Rules >>

Leave a Reply

Your email address will not be published. Required fields are marked *