Another article which I found on Gartner describing interesting systems and their architectures in business, at this time Business Rule Management Systems (BRMS).
What is a BRMS ? - Collection of technologies for processing rules, policies and executing scenarios.
Why BRMS ? - Similar to development of business process management (BPM) technologies, similar shift occurs in the rule market. Business rule engine (BRE) is currently evolving int BRMS by providing richer rule managament ecosystem and additional functionalities in relation to BRE.
Core components of BRMS
1. The Rule Execution Engine - execution and management of rules in efficient manner. Inference based rule execution based on the RETE algorithm (processing similar to Prolog like languages evaluation) which infers new facts. There are also some some solutions which does not support forward and backward chaining but select rules on use cases (event processing, BPM flow management decisions , data transformation rules or other heuristics).
2. Rule Repository - a database storing various business rules, often offers robust versioning to create different variants of rules according do different rule projects varying on levels of security. They provide administrative tools, search features, check-in/check-out mechanism, marking rule as final.
3. Rule Integrated Development Environment- graphical, model driven programming IDE for authoring, sequence test and debug rules. Rich role-based development environment. Often provides complex WYSIWYG to simplify the development.
4. Rule-Model Simulation - set of rule simulation tools providing what if analytics to analyze interrelated rule models. They could crate rule dependency relationships and simulate rule sets with runtime data or historical data.
5. Monitoring and Analysis - offers historical and runtime analytics, rule usage reports and complete audit trails showing how rule was executed in a particular transaction or decision. Reports provide information on who accessed a rule, what rules were executed to perform decision etc.
6. Rule Management and Administration- set of tools to deploy rules into environments, security management, promotion of new set of rules, tracking system health and performance.
What is a BRMS ? - Collection of technologies for processing rules, policies and executing scenarios.
Why BRMS ? - Similar to development of business process management (BPM) technologies, similar shift occurs in the rule market. Business rule engine (BRE) is currently evolving int BRMS by providing richer rule managament ecosystem and additional functionalities in relation to BRE.
Core components of BRMS
1. The Rule Execution Engine - execution and management of rules in efficient manner. Inference based rule execution based on the RETE algorithm (processing similar to Prolog like languages evaluation) which infers new facts. There are also some some solutions which does not support forward and backward chaining but select rules on use cases (event processing, BPM flow management decisions , data transformation rules or other heuristics).
2. Rule Repository - a database storing various business rules, often offers robust versioning to create different variants of rules according do different rule projects varying on levels of security. They provide administrative tools, search features, check-in/check-out mechanism, marking rule as final.
3. Rule Integrated Development Environment- graphical, model driven programming IDE for authoring, sequence test and debug rules. Rich role-based development environment. Often provides complex WYSIWYG to simplify the development.
4. Rule-Model Simulation - set of rule simulation tools providing what if analytics to analyze interrelated rule models. They could crate rule dependency relationships and simulate rule sets with runtime data or historical data.
5. Monitoring and Analysis - offers historical and runtime analytics, rule usage reports and complete audit trails showing how rule was executed in a particular transaction or decision. Reports provide information on who accessed a rule, what rules were executed to perform decision etc.
6. Rule Management and Administration- set of tools to deploy rules into environments, security management, promotion of new set of rules, tracking system health and performance.
7. Rule Templates - pre-built, abstract sets of rules to improve time to value ratio.
If you are interested - whole article discusses each component in much greater detail, it touches on distinction between BRE and BRMS and describe the evolution from BRE as adoption to the market.
No comments:
Post a Comment