Graphical Business Rules Management


Published on

This presentation shows how to graphically model, manage and deliver business rules with the Eclipse-based tool Visual Rules. The business case used is Master Data Management at Eurex. The presentation also explains the business impact of this approach.

Published in: Technology, Travel, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Graphical Business Rules Management

    1. 1. Shown with the Business Case Master Data Management at EUREX Graphical Business Rules Management Volker Grossmann, Innovations Jan Trnka, STABIL IT
    2. 2. Business Rules <ul><li>change most frequently </li></ul><ul><li>are difficult to reconcile </li></ul><ul><li>bear a high risk </li></ul><ul><li>are error-prone </li></ul><ul><li>hazards: incompleteness, contradiction, redundancy </li></ul><ul><li>are hard-wired </li></ul>Business IT Systems Rules Rules Rules Rule changes are tedious, risky and expensive
    3. 3. How to Solve This Dilemma? <ul><li>separate from program code </li></ul><ul><li>do not hard-wire </li></ul><ul><li>make them easy to reconcile </li></ul><ul><li>manage by Business and IT </li></ul><ul><li>test separately </li></ul><ul><li>apply changes automatically </li></ul><ul><li>manage centrally </li></ul>Business IT Systems Rules Rules Rules Rules All this is accomplished by a BRMS that makes rule changes fast, safe and easy BRM
    4. 4. Cooperation between Business and IT Business IT Results from using Visual Rules <ul><li>Architecture </li></ul><ul><li>Integration </li></ul><ul><li>Deployment </li></ul><ul><li>Infrastructure </li></ul><ul><li>Focus on technical aspects </li></ul><ul><li>Clear specs from business </li></ul><ul><li>Less maintenance efforts </li></ul>Agile software Less costs Better quality <ul><li>Focus on business aspects </li></ul><ul><li>Fast and easy changes </li></ul><ul><li>Business logic ownership </li></ul>Target <ul><li>Define, </li></ul><ul><li>Simulate, </li></ul><ul><li>Test and </li></ul><ul><li>Document business rules </li></ul>Tasks
    5. 5. Visual Rules
    6. 6. Rule Elements Decide Make a decision Assign Calculate values and update data Fire Action Execute an action Call Flow Rule Call a flow rule Call Decision Table Call a decision table Call Service Call a service Done & Return Immediately return to the calling rule Repeat Repeat the following part of the rule End Repeat Immediately exit a Repeat Return Exception Create exception and continue at exception handling Handle Exception Specify what to do when an exception is thrown
    7. 7. Flow Rules <ul><li>Flow rules are created using simple drag&drop </li></ul><ul><li>Flow rules consist of decisions, assignments, actions and exceptions </li></ul>
    8. 8. Decision Tables <ul><li>Decision Tables can also be created via drag & drop </li></ul><ul><li>Decision Tables can contain decisions, assignments, actions and exceptions </li></ul>
    9. 9. Testing <ul><li>Test cases define input and expected output of a rule </li></ul><ul><li>Detected deviations of input/output/internal data or actions are reported </li></ul>
    10. 10. Management <ul><li>Rules are fully versioned </li></ul><ul><li>Visual compare & merge capabilities </li></ul>
    11. 11. Package and Rule Dependencies <ul><li>Rule and rule package dependency visualization </li></ul>
    12. 12. Documentation
    13. 13. Introduction: EUREX <ul><li>Joint venture of Deutsche Boerse and SIX Swiss Exchange </li></ul><ul><ul><li>One of the world largest derivative exchanges </li></ul></ul><ul><ul><li>One of the largest Repo and SLB markets providers in Europe </li></ul></ul><ul><ul><li>> 500 Participants (Banks) </li></ul></ul><ul><li>Repo Market </li></ul><ul><ul><li>Leading European Repo market place since 1995 </li></ul></ul><ul><ul><li>Exclusive usage by the Swiss Federal Bank (SNB) for conducting monetary interventions </li></ul></ul><ul><li>SLB Market </li></ul><ul><ul><li>Leading European market place for securities lending & borrowing = 60‘000 securities from 87 countries worldwide </li></ul></ul><ul><li> </li></ul><ul><li>Introduction </li></ul>
    14. 14. Problem Description: Master Data Maintenance <ul><li>10‘000 securities is a limit for manual maintenance </li></ul><ul><li>Problems: </li></ul><ul><ul><li>Data quality </li></ul></ul><ul><ul><li>Consistency </li></ul></ul><ul><ul><li>Compliancy with specifications </li></ul></ul><ul><ul><li>Time (time to market) </li></ul></ul><ul><li>Goals for new solution: </li></ul><ul><ul><li>Automate the process => lower costs </li></ul></ul><ul><ul><li>Increase the quality </li></ul></ul><ul><ul><li>Process much higher data volume (100’000 securities) => increase performance </li></ul></ul><ul><li>Problem description </li></ul>
    15. 15. <ul><li>Rule-Based Data Maintenance </li></ul>Rule-based Data Maintenance Valid & consistent Data Automated Process <ul><li>Valid </li></ul><ul><li>Consistent </li></ul><ul><li>Unified format </li></ul>How? Data, or Data fragments <ul><li>Incomplete </li></ul><ul><li>Inconsistent </li></ul><ul><li>Various formats </li></ul>complete filter & merge capture validate release distribute
    16. 16. <ul><li>Rule-Based Data Maintenance </li></ul>Rule-based Data Maintenance Minimal Human Interaction Persistent Data Storage Information Capture Presentation Data Dissemination <ul><li>Valid Data: </li></ul><ul><li>File </li></ul><ul><li>WebService </li></ul><ul><li>DB Table </li></ul><ul><li>E-Mail </li></ul>Automated, Rule-driven Process <ul><li>Incomplete Data </li></ul><ul><li>Fragments: </li></ul><ul><li>File </li></ul><ul><li>WebService </li></ul><ul><li>Web-Extract </li></ul><ul><li>E-Mail </li></ul><ul><li>DB Table </li></ul>
    17. 17. What it really does <ul><li>Data input as e-mail, file, Web-page </li></ul><ul><li>Various formats (XML, csv, text, Edifact) </li></ul><ul><li>Consolidation of data from different sources (Bloomberg, Telekurs, ..) </li></ul><ul><li>Rule-based validation of all data according to business requirements </li></ul><ul><li>Rule-based composition of securities into baskets and markets </li></ul><ul><li>Rule processing uses 35 decision trees > 2,000 rules </li></ul><ul><li>Automatic data dissemination to the trading platform </li></ul><ul><li>Rule-Based Data Maintenance at Eurex </li></ul>Automated, Rule-driven Process
    18. 18. Impact of Visual Rules <ul><li>Change of business logic without change of source code </li></ul><ul><li>Responsibility is with the business unit, not with IT (the natural know-how owner is responsible) </li></ul><ul><li>Experiments with data and rules are possible </li></ul><ul><li>Intuitive and easy to use user interface </li></ul><ul><li>Side effects </li></ul><ul><li>User must know his business </li></ul><ul><li>Rule outcome is exclusively “yes” or “no” </li></ul><ul><li>Bad rules may screw-up the system (versioning required) </li></ul><ul><li>Rule-Based Data Maintenance at Eurex </li></ul>
    19. 19. Business Impact <ul><li>100’000 securities processed within 3 hours </li></ul><ul><li>Data volume increase by factor 10 </li></ul><ul><li>Degree of automation = 98% </li></ul><ul><li>Cost saving </li></ul><ul><li>Eurex data quality is now market reference! </li></ul><ul><li>Rule-Based Data Maintenance at Eurex </li></ul>
    20. 20. What do Analysts say?
    21. 21. Visual Rules Components
    22. 22. Detailed Eclipse-based Modeler Architecture Visual Rules Modeler Test Editor Flow Rule Editor Workspace Decision Table Editor Eclipse Platform JDT (Java Development Tools) EMF (Eclipse Modeling Framework) GEF (Graphical Editing Framework) EMF Commands Rule Meta Model (Ecore) EMF Validation Rule Model Validation (OCL and Java) BIRT (Business Intelligence and Reporting Tools) Equinox (OSGi) Java Code Generator (Velocity Templates) Rule Model Export (HTML) Java Integration API Rule Navigator Java Import Ant Tasks Rule Models (EMF Resources) Rule Integration API Data Model Synch API Extension Points Advisor Security Functions Actions Services Custom UI Debugger Debugging Framework Execution/ Testing JDT Launch Compare/Merge Team API
    23. 23. Visual Rules Enterprise Platform
    24. 24. Any Questions ? Volker Grossmann, Product Management Visual Rules [email_address] Jan Trnka, CEO STABIL IT [email_address]