After yesterday's post I guess I was bound to immediately find another reason to blog about decision management in the context of business process management (BPM) and composite applications. Sure enough an article on InfoQ caught my eye - BPM + SOA as a Composite Application Model is Gaining Mindshare. The article had some useful links and a nice summary of the way in which process-centric composite applications, assembled from existing and new services, can be developed using business process management tools. There were three comments that really caught my eye:
- "It has long been recognized that traditional application models are not geared towards changing business processes easily"
Nor do they allow decisions to be changed easily and real agility requires both process and decision agility. - "In a J2EE or .Net programming model, processes are hard coded. Charles Simonyi compares this type of coding to an "encryption" process"
I love this idea - coding as an encryption process! I blogged about not developing write-only code once before and had a comment about Charles previously too. - "critical pieces of the business process context ... are captured in notes or spreadsheets at best"
And decision logic is probably not captured at all!
Technorati Tags: agility, BPM, business agility, business process, business rules, decision automation, decision management, decision service
 Subscribe to this blog by RSS
thank you for your comments. I am currently reading your book on Enterprise Decision Management. This was definitely an eye opener. Framing it with the monikor EDM is certainly going to be very helpful to raise awareness of the importance of the rules in BPM and SOA.
I am currently working on an abstract SOA framework called wsper (http://www.wsper.org/primer.html) and I am looking at how to incorporate EDM in the application model. You are welcome to help too.
JJ-