« Why you SHOULD loosely couple processes and rules | Main | Reducing maintenance with business rules »

Thanks to my friends at Yasu I just came across an interesting piece by Narayan Devanathan of Wipro for ITtoolbox - BRMS and Business Users. One of the things the paper does not discuss is how to tell that it would make sense to have business users maintain their rules. In our book, Neil and I suggest that there are several reasons to do this:

• Rules that change often
  When rules change regularly, or irregularly but often, the drivers for those changes are going to be business drivers. If the business users can see the driver for change and respond to it themselves, you will get quicker time to market and greater agility
• Rules that have business complexity
  When the rules are complex, in business rather than in technical terms, or have complex interactions it is likely that the business users will be able to work through the business implications of change more effectively than a programmer. Of course the reverse is true when rules have technical or systems complexity.
• Rules that require domain knowledge to understand
  If you are managing rules like drug interactions where the rule is just a rule to a programmer but where a business user has a real feel for rightness and wrongness, having the business users manage the rules directly will result in few errors and more accurate rules.
• Rules that the business wants or expects to own
  Lastly, of course, you may be replacing a system or a manual decision that the business is used to controlling and the continued control of these rules may be a requirement of the system.

Posted by jtaylor in Business Rules |Digg This|Add to del.icio.us

Trackback Pings

TrackBack URL for this entry:
http://www.ebizq.net/mt/mt-tb.cgi/2375