Dynamic Business Rule Engine

8/8/2019 Dynamic Business Rule Engine

1/19

By:

Parag ChaudhariSheetal KaulTushar Humbe


2/19

OUTLINEy INTRODUCTION

y GOALS

y TECHNOLOGYy SYSTEM ARCHITECTURE

y BASIC WORKFLOW

y ALTERNATIVE SOLUTION

y ADVANTAGES

y CONCLUSION


3/19

INTRODUCTIONPROBLEM IN CURRENT SYSTEM:

y Business Rules change over time.

y

To apply modified rules:y Develop new rule

y Shut down servers

y Deploy rule

y Test rule

y Update the systemy System is down for 2-4 hours.

y Results in loss of business and customerdissatisfaction


4/19

PROPOSED SOLUTION

y Design plug in into existing system

y No need to shut down server

y Storing rules in Rule Engine

y Change in the rule is made on flyy Administrator performs desired changes at run time

y Loss associated due to server shut down is thuseliminated


5/19

GOALS

y Functional goalsy User authentication

y Add/modify/delete rules

y

System consistence checky Technological goals

y Easy of maintenance in case of application redeployment.

y File security.

y Clustering and exclusive lock while modifying the script.

y Ease of executing the rule set.

y QualityGoalsy Pluggable with the existing software.


6/19

TECHNOLOGYTECHNOLOGY VERSION

ECLIPSE 3.4+

JAV

A SDK 5+IBATIS 2.3.4

STRUTS 1.1

GROOVY 1.6

JUNIT 4.4+


7/19

CORE COMPNENTS

y GROOVYRULE ENGINE

To store rules in the form of scripts and manage rulescripts related functionality

y IBATIS

To manage database connectivity framework

y STRUTS

To follow MVC architecture


8/19

SYSTEM ARCHITECTURE


9/19

y System architecture of rule engine supports ServiceOriented Architecture(SOA)

y Model frequently changing business logicy Agile solutions achieved related to business

y Separate business logic from application logic

y Rule engine basic principle: Its all about conditions

and actions called in certain order


10/19

INTERFACE


11/19

y DBR System receives and accepts the specificationsand parameters from a target system and reads and

processes the inputs which are stored in the repositorycomponent through the business rules buildercomponent.

y The system creates and constructs a specific-domain

DBR engine based on the target system's parameters atthe end.

y Statements in the DBR's format and are semanticallyspecified regarding the target system.


12/19

BASIC WORKFLOW


13/19

USE CASE-:ADD RULE


14/19

DELETE RULE


15/19

MODIFY RULE


16/19

ALTERNATE SOLUTIONSy Instead of saving rule in rule engine, store it in

database in the form of individual scripts

yProcess Engines : allow you to graphically describesteps in a process - those steps can also involvedecision point which are in themselves a simple rule.

y Data-driven systems: control tables that store meta-

data that changes your applications behaviour


17/19

ADVANTAGESy Declarative Programming

y Logic and Data Separation

y Speed and Scalabilityy Centralization of Knowledge

y Tool Integration

y Explanation Facility

y Understandable Rules


18/19

CONCLUSION

y Business Rules: logic that are captured bybusiness/system analyst, and put into applicationprogram code by programmers.

y

Major problems: Traditional systems developmentmethodologies tend to create applications that are"Black Boxes", whose inner workings are oftenunknowable, and which are difficult to change.

y

Tools and techniques are being developed forcapturing rule definitions. In this project we arebuilding the system which based on rule engine whichkeeps all the business rule altogether for specificbusiness domain in our case its banking


19/19

THANK YOU..

Documents

Dynamic Business Rule Engine