• Share
  • ?
  • Profiles ▼
  • Communities ▼
  • Apps ▼

Blogs

  • My Blogs
  • Public Blogs
  • My Updates
  • Administration
  • Log in to participate

▼ Tags

 

▼ Similar Entries

Support Search delta...

Blog: Websphere Com...
Jacky Yan 50JTYSWH2S
Updated
0 people like thisLikes 0
No CommentsComments 0

Single sign-on with ...

Blog: IBM BPM Conte...
SaschaSchwarze 270000UQG4
Updated
1 people likes thisLikes 1
No CommentsComments 0

IBM Business Automat...

Blog: ECM Community...
Dave Perman 2700007Y91
Updated
1 people likes thisLikes 1
No CommentsComments 0

Announcing the Avail...

Blog: ECM Community...
Dave Perman 2700007Y91
Updated
3 people like thisLikes 3
No CommentsComments 0

SOA BOD - Rest Respo...

Blog: Websphere Com...
Jacky Yan 50JTYSWH2S
Updated
0 people like thisLikes 0
No CommentsComments 0

▼ Archive

  • June 2018
  • May 2018
  • November 2017
  • October 2017
  • September 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • March 2016
  • May 2015
  • February 2015
  • January 2015
  • January 2014
  • November 2013
  • February 2013
  • October 2010
  • August 2010
  • July 2010
  • April 2010
  • March 2010
  • December 2009
  • November 2009
  • October 2009
  • July 2009
  • May 2009
  • April 2009

▼ Blog Authors

Marc Fiammante #ibmaot

View All Entries
Clicking the button causes a full page refresh. The user could go to the "Entry list" region to view the new content.) Entry list

Fourth of Seven practices for Dynamic Process: Separate Behavioral and Design patterns

fiammante 100000A8UA | | Tags:  bpm busines_process soa pattern ‎ | 11,490 Views
When business analysts model business process they tend to capture the sequence of tasks and events without trying to structure into patterns. As an example sequential workflows that usually happen between different actors are mixed with very dynamic interactions such as screen navigations with lots of back & forth or context switch actions. Event driven reactive processing is mixed with service proactive sequence handling. The risk of such mix is to face modeling limitations, and to lead implementation team to the wrong technology selection with an induced higher cost. The following picture describe the essential patterns and the corresponding technology. 
  • The top layer captures the interactions between different business domains, or to take an APQC classification terminology for level 3 decomposition "processes".
  • The next layer is workflow between different actor belonging to the same business subdomain .
  • One layer below captures the interactions of a single human actor with the system for a particular task of the above workflow.
  • The bottom layer addresses the matchmaking usually implemented in ESBs, to expose the appropriate services using adaptation or combination of existing interfaces.
 
image 

To differentiate Service Oriented Architecture and Event Driven Architecture the classical gang of four work on Design Patterns  can be used as described by the following picture.
 image
  • Add a Comment Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry
Notify Other People
notification

Send Email Notification

+

Quarantine this entry

deleteEntry
duplicateEntry

Mark as Duplicate

  • Previous Entry
  • Main
  • Next Entry
Feed for Blog Entries | Feed for Blog Comments | Feed for Comments for this Entry