tag:blogger.com,1999:blog-5869426.post469991269356336971..comments2024-01-16T10:48:25.428+00:00Comments on Drools & jBPM: SBVR vs If-Then-Action RulesMark Proctorhttp://www.blogger.com/profile/03304277188725220501noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-5869426.post-18735212619266606522014-01-02T13:55:30.553+00:002014-01-02T13:55:30.553+00:00Great article!! I enjoyed it so much. thanks for s...Great article!! I enjoyed it so much. thanks for sharing. <a href="http://www.aa5thavetransportation.com" rel="nofollow">Taxi</a>Anonymoushttps://www.blogger.com/profile/16458959458867887643noreply@blogger.comtag:blogger.com,1999:blog-5869426.post-41013006863723324102013-01-16T21:03:45.375+00:002013-01-16T21:03:45.375+00:00The if then vs Rulespeak approaches contrasted her...The if then vs Rulespeak approaches contrasted here do not seem all that new, especially if one thinks of the familiar publish subscribe pattern - atleast when it comes to declaration vs implementation of business rules and business actions.<br />With the rulespeak approach , it seems clearer that the business rule declaration should only recognize (maybe by publishing a 'conditions satisfied' message) when rule conditions are satisfied. Then multiple action subscribers/listeners would be activated to carry out consequences of the rules conditions being met.<br />This also clearly recognizes the decoupling of rules activation and actions/consequence taken.Peterhttps://www.blogger.com/profile/16348929764720873335noreply@blogger.comtag:blogger.com,1999:blog-5869426.post-31326159527549901262012-09-12T11:40:05.151+01:002012-09-12T11:40:05.151+01:00We wouldn't move away from engineering termino...We wouldn't move away from engineering terminology, such as classes and beans - because that's the bulk of our users. However there is no reason why we can't develop alternative approaches around say SBVR, and adopt the SBVR terminology for this. But so far we haven't had the resouces to take on SBVR yet.Mark Proctorhttps://www.blogger.com/profile/03304277188725220501noreply@blogger.comtag:blogger.com,1999:blog-5869426.post-17464054875065835142012-09-11T19:47:21.738+01:002012-09-11T19:47:21.738+01:00I'm in a quandary right now on how to proceed ...I'm in a quandary right now on how to proceed with a business rules effort with an organization that is rules-immature.<br /><br />Option A is to go down the Ron Ross path using a fact model and rules documented in RuleSpeak.<br />Pros:<br />Uses a business-driven approach<br />I can use Ron's book to teach the team the process.<br />Cons:<br />I've found few tools that support Ron's approach (two so far)<br />Testing the rules may be challenging due to the previous item<br /><br />Option B is to use a UML class diagram along with rules in Drools (using Guvnor).<br />Pros:<br />Free tools that are widely used<br />Easier ability to test the results<br />Cons:<br />Drools uses different terminology for things like facts and fact models (big issue). This is guaranteed to cause problems.<br />The tooling will be more techie and more confusing<br /><br />It would be really great if Drools would migrate more towards SBVR terminology.<br /><br />Thoughts or experiences from anyone on this topic?Gordienoreply@blogger.com