A business rules engine separates business logic from your mission-critical applications in order to gain agility and improve operational performance.
A BRE platform should support a variety of rule types, so that business rule creators aren’t left trying to fit square pegs into round holes. Rule types include:
A business rules engine empowers business users to create and manage business rules with minimal involvement from IT. It should complement your business workflow, integrate seamlessly with your existing IT assets, and scale for performance.
Best in class rules engines have the following characteristics:
Usability: Ensure it puts business users firmly in charge of creating and managing business rules, for maximum agility. Usability features include:
Power: Provides support for a wide range of rule types, including process rules that automate workflow management, decisioning rules of all types, declarative rules that compute values based on detected changes in other related property values, transformation rules that appropriately transform data as it passes across heterogeneous systems, and integration rules that determine the right system to invoke for each situation. It is also imperative that rules can call other rules. For example, a user leveraging a declarative rule in a decision table or tree.
Scalability: Ensure that the rules engine has distributed application nodes that can share a common rules database, for optimum scalability. Ideally the system employs an open Java and XML architecture, and can run any major operating system in conjunction with any major application server.
BRE solutions should all be compliant with the latest SOA, Web Services and other Architecture trends such as Open Source.
What it Includes
Business Rules Engine should include:
What it Does not Include
Does not include features and requirements that are contained in other components such as:
Applicable Standards and Documents