The Business Rules Approach
by David Wright
“The biggest risk to your company is not being able to change fast enough… Business Rules are the answer.” …Ron Ross
I am a great appreciator of Mr. Ross. He has written extensively on the topic of Business Rules, offers excellent training on the subject, and is the keynote speaker at each year’s International Business Rules Forum. I would like to start my own article on Business Rules with an ‘icebreaker’ he used on a seminar I attended.
| Attachment | Size |
|---|---|
| The Business Rules Approach.pdf | 165.55 KB |
IF/THEN/ELSE
Kimber,
Based on what you have written, I would suggest that your example is not a Business Rule, per se. First off, conditional logic like that is not considered declarative, and routing would seem to be a factor of your Business Process, not Rules. Granted, a Business Process can change frequently, probably more frequently than Rules, whick speaks to the need for Business Process Management; just like Rules should not be embedded in your application code, neither should your Process.
Essential data management belongs to the Data portion of systems I discussed--> making sure keys are unique, that all mandatory fields have values,etc. (although some people treat these as Rules as well.)
So, in your example, membership in a set/domain is something your data system would be able to determine, after which your BPM system would determine what happens next and where.
Does that help?
David Wright
Member, IIBA
"The Devil is in the Details." ...attribution unknown