One of the problems of large software development projects — especially distributed systems and integration — is managing the business rules. Mergers and acquisitions magnify the problem. Policy updates in one part of the system may not be seen elsewhere. Often the same rule may be "hard-wired" in many places, deep in application code. Your CEO cannot understand why urgently needed changes, that seem so simple, can take weeks and months to implement. Thankfully, with the uptake of Service Oriented and Component Based technologies, business rules can now be managed separately.
The risks of not doing this are:
|
Business Rules White Paper— version 2 You can download a white paper on business rule management systems here: |
||||
|
Service Oriented Business Rules Management System — version 2
|
||||
This downloadable report discusses business rules and business rules management systems (BRMS), especially those that use the Rete algorithm, are compatible with a service oriented architecture (SOA) and component based. There is also a focus on the way natural language is treated. Eleven products are described and three reviewed in detail. These are ILOG JRules, Fair Isaac Blaze Advisor Version 6 and Haley Systems HaleyAuthority (aka Authorete, Authority) and HaleyRules (Eclipse).
Note: this is Version 2 of the report. We intend to keep on expanding the report in the light of new products and product versions that come to our attention. New versions will be posted periodically.
Watch this space for version 3.
For advice on business rules from expert consultants please email us.