I was reading Ron Ross' book Principles of the Business Rules Approach (reviewed here) and thought his basic principles deserved both an airing on this blog and some additional "sub principles" when applied to the automation of decisions using business rules technology. The main list is Ron's with my comments and additions
below each one.
Rules should be expressed in plain language
Rules should exist independent of procedures and workflows
Rules should build on facts and facts should build on concepts as represented by terms
Rules should guide or influence behavior in desired ways
Rules should be motivated by identifiable and important business factors
Rules should be accessible to authorized parties
Rules should be single-sourced
Rules should be specified directly by those people who have relevant knowledge
Rules should be managed
- Rules should be written and made explicit
- Rules are not the same as other requirements
- Rules should not be buried in code or SQL
- Rules your operational systems need should be in a Business Rule Management System
- Rules should be as expressed in language as plain as possible and no plainer (with apologies to Albert Einstein)
- If you can hide complexity to make rules easier to understand, do so
- Don't bury your rules in your BPMS, keep them separate
- Write your rules against the objects you are managing already
- Rules that don't do anything are not very helpful
- Rules can take or recommend action
- Policies, procedures, regulations, strategies
- Remember these should be business rules and so should matter to your business
- Rules need to be managed in a real repository
- A rule repository needs version control, access control, auditing etc
- "One rule to rule them all"
- If you can empower the business users to write the rules do so
- If you can't get the business users to own the rules, make sure they can collaborate on them
- Remember they don't want to write rules, they want to run their business (so make it easy for them)
- Putting rules in a BRMS is the first step. Treating them as an asset to be managed, reused and exploited is where the value comes
- Management requires technology and procedures and policies.
Subscribe to this blog by RSS
Leave a comment