tag:blogger.com,1999:blog-6794234910187525180.post777299609949273112..comments2008-04-25T12:30:45.554-07:00JBoyhttp://www.blogger.com/profile/00147585132386859260noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-6794234910187525180.post-89442106629273737562008-04-04T03:25:00.000-07:002008-04-04T03:25:00.000-07:00that's a great and usefull sheet - it's quite simple but this is exactly what I'm looking for. to show things simple they're a little bit more complicated but difficult to handle it.<BR/>thx for the post. I want to get your overview and drag it to my next customer meeting. - ;)Schaueckerhttp://www.businessrules.ch/noreply@blogger.comtag:blogger.com,1999:blog-6794234910187525180.post-91002547939300263442008-04-03T16:46:00.000-07:002008-04-03T16:46:00.000-07:00James<BR/>You are right I try to make the schema simple. The main point was as you quoted :"changes in genuine requirements is slowest, process changes slower and rules changes most frequent"<BR/><BR/>Then I also agree the analysis team needs to focus on decision step of the business process which at the implementation point of view will call a decision service using business rules. This was not really the purpose of this post. I'm preparing an example of BPM- BR modeling for the future that should describe this.JBoyhttp://www.blogger.com/profile/00147585132386859260noreply@blogger.comtag:blogger.com,1999:blog-6794234910187525180.post-54519852738100368102008-04-03T09:34:00.000-07:002008-04-03T09:34:00.000-07:00Thanks for an interesting post - I blogged about it <A HREF="http://www.ebizq.net/blogs/decision_management/2008/04/dont_forget_decisions_when_usi.php" REL="nofollow">here</A> as I had a couple of things to add.<BR/>JT<BR/><BR/>James Taylor<BR/>Author of Smart (enough) Systems<BR/>Blog at <A HREF="http://www.smartenoughsystems.com/wp" REL="nofollow">smartenoughsystems.com/wp</A>James Taylorhttp://www.blogger.com/profile/04589456040368641147noreply@blogger.com