Agile IT Architecture

I just had a look to the presentation from Sandy Kemsley done at the business rule forum: " Mixing Rules and Proces s" and her blog entry on BPMS and BRMS integration. I can quickly summarize the points she made that I love and share some feedback: Does BPM has Rules? yes but typically not full-features BR. Rule changes may require redeploying processes with IT involvement. Separate rules from process: externalize decision from process. Call BRE from BPE. Benefits from separation: compext rules automate manual process, reuse rule across processes, change rule without processes. In her blog entry "As a BPM bigot, I see rules as just another part of the services layer... but I didn’t hear that from any of the vendors." It may be because ILOG team was not speaking... ;-) We are pushing, saying and we are delivering projects since 4 to 5 years where we have a clear separation between decisions done by business rules from process flow, and designing solution where the bu

Recently I had to re-do some JSR94 code and I'm still interested by this work done some years ago and I'm still supportive of it. But as Roy Johnson was saying recently during one of his presentation "Where will tomorrow's enterprise innovation come from?". Does JSR94 is one of this "unhealthy Java standard" like JDO was? Done in a period where the Java community wanted to standardize everything ? For the recall JSR-94 is an industry standard that defines how Java programs deployed in J2SE or J2EE can acquire and interact with a rule engine. Being able to change engine implementation is a nice design approach, but as of today this specification is limited by the fact that there is still no standard to exchange rule definition between engines. So rule written for one engine can not be used by another one. This dramatic limitation is undermining the use of JSR94. And i'm still surprise to see architect asking compliance to it. Although the horizon is