© 2010 ibm corporation ilog jrules overview roles-based tour and intro to business rule management...

© 2010 IBM Corporation

ILOG JRules OverviewRoles-based Tour and Intro to Business Rule Management Systems (BRMS) (from ILOG 2010 STEW & PoT)

© 2010 IBM CorporationIBM WebSphere ILOG JRules 7.1.1.0 2

Rule Solutions for Office

AuthorAuthor

Rule Execution Server

Java™ SE / Java EE / SOA

Rule Team Server

PublishPublish8

Rule Studio

DesignDesign1

OrchestrateOrchestrate2

AuthorAuthor3

TestTest4

DebugDebug5

DeployDeploy6

IntegrateIntegrate7

AuditAudit12

Enterprise ApplicationArchitect / Developer / Administrator

Business Rule Management and AuthoringBusiness Analyst / Policy Manager / Administrator

Business Rule Application DevelopmentArchitect / Developer / Business Analyst

ILOG BRMS Roles-based Tour

Tip: click on any task number or name to move to this task.2

ValidateValidate10

ManageManage9

DeployDeploy11

© 2010 IBM CorporationIBM WebSphere ILOG JRules 7.1.1.0

Agenda

Introduction to Business rule management systems (BRMS)

Roles-based Tour of ILOG JRules BRMS

Methodology and Next steps


Up-sell or Cross-sellCompensationSmart CRMUnderwritingTax calculationBenefit calculation…

FraudRiskPricingClaims processingEligibilityCompliance…

Business Decisions are everywhere

Change – Need for Agility

Va

riatio

n – N

ee

d for Flexibility

• Jurisdictional

• Micro-Market Segmentation

• Multichannel

• Market Driven

• Regulatory

• Mergers and Acquisitions

4


Business Needs are Dynamic

Are we compliant with the new regulation requirements?

Let’s create a special promotion for our best customers.

Can we automate approvals for this type of order?

5


When business logic is hard-coded

• Long change cycle• Opaque for business users• Often hidden, scattered and duplicated

Application code

LOB

IT

6


Business Change Drives IT agility

Decisions used in operations = “business rules”

Issues

• Rules are hidden in code or isolated within the organization

• Changes are hard to track and maintain over time

• Rules used by systems have to be programmed and require IT resources

• Duplication and multiple versions of the same rules

• Lack of auditability, traceability

• Decision changes cannot be easily tested or simulated

• Rules are hidden in code or isolated within the organization

• Changes are hard to track and maintain over time

• Rules used by systems have to be programmed and require IT resources

• Duplication and multiple versions of the same rules

• Lack of auditability, traceability

• Decision changes cannot be easily tested or simulated

Where Business Rules Exist

ApplicationsDocuments

ProcessesPeople

7


Where Business Rules Exist

ApplicationsDocuments

ProcessesPeople

Business Rule Management System

Rules are Defined, Analyzed and Maintained

Rules are Deployed, Executed and Monitored

Rules are Managed and Stored

User Tools

The Smarter Approach: Facilitating Change with BRMS


Rule Repository

8


Rule and Software Development Life cycles

DesignDesign

ConstructConstruct

TestTest

AnalyzeAnalyzeAuthorAuthor

ValidateValidate

Manage and MonitorManage and MonitorDeployDeploy

Platform upgradePlatform upgrade

Change RequestChange Request

DeployDeploy


ValidateValidate

DeployDeploy



ValidateValidate

DeployDeploy

Rule Management Life cycleRule Management Life cycle

DesignDesign

ConstructConstruct

TestTest

DeployDeploy

Software Development Life cycleSoftware Development Life cycle



ValidateValidate

DeployDeploy

Functional enhancementsFunctional enhancements

> 4-6 months

< 1 month

9


Agenda






AuthorAuthor


Java™ SE / Java EE / SOA

Rule Team Server

PublishPublish8

Rule Studio

DesignDesign1


AuthorAuthor3

TestTest4

DebugDebug5

DeployDeploy6

IntegrateIntegrate7

AuditAudit12




Roles: Sequence of 13 tasks

Tip: click on any task number or name to move to this task.12

ValidateValidate10

ManageManage9

DeployDeploy11


Agenda



– Business user focused activities

– IT user focused activities




AuthorAuthorValidateValidate10

ManageManage9

Decision Validation Services


Java SE / Java EE / SOA

Rule Team Server

PublishPublish8

DeployDeploy11

Rule Studio

DesignDesign1


AuthorAuthor3

DeployDeploy6

IntegrateIntegrate7

AuditAudit12




Task 9: Manage

14

TestTest4

DebugDebug5


Access rule artifacts concurrently without conflict or delay

Take control of very large rule projects with Smart Views, easy search and reporting

Get automatic notification of potential rule conflicts, redundancies

See where rules are used across projects using queries

Hot-deploy rule changes in minutes

Secure, integrated with enterprise security facility including single sign-on

15

Task 9: Manage – web application for rule management

15


Task 9: Manage – Rule Repository capabilities

Who can change what?Who can change what?

When will this rule take effect?When will this rule take effect?

What is the impact of changing this rule?`What is the impact of changing this rule?`

What rules do I need to deploy?What rules do I need to deploy?

How do I undo a change?How do I undo a change?

What has changed?What has changed?

What rules do I need to validate?What rules do I need to validate?

Rule repository

• Rule Governance• Meta-data• Lifecycle management• Versioning• Role-based permissions• Consistency checking

Validated

Inactive

DeployableRetired

New

Rejected

Defined

PM

PM

PM PM

Analyst

Admin Admin

AdminAdmin

Admin

16


Versions

– Rules, Decision Tables, Decision Trees, Ruleflows, etc… are versioned

– Versions created upon modification of element

– You cannot delete previous versions

History

– consult the history of version modifications made over time

Baselines

– freeze the state of a project

– for instance keeps an image of rules currently deployed

17

Task 9: Manage – Rule Versioning

17


Task 9: Manage – Comparing versions of a Decision Table

18


Queries enable to search the content of the repository, including any type of artifact (rule, folder, ruleflow and others)

Evaluate impact of changes to the object model or changes to the rules

• Before adding a new rule that modifies a certain data value to a rule project, query for all rules that use that parameter to assess impact of new rule

Find rule artifacts based on their properties

• Find only rules you wrote

• Find all rules added within certain time period

• Find a specific rule, based on documentation

Perform actions based on the results of a search

Find all business rules such that the status of each business rule is new

Do set the status of each business rule to validated

19

Task 9: Manage – Rule Queries

19




ManageManage9




Rule Team Server

PublishPublish8

DeployDeploy11

Rule Studio

DesignDesign1


AuthorAuthor3

DeployDeploy6

IntegrateIntegrate7

AuditAudit12




Task 10: Validate

20

TestTest4

DebugDebug5


Support the various testing aspects of a decision service– Correctness

– Non Regression

– Performance

– Coverage

Support the business impact of a set of changes– KPI-driven simulation

Support the ability for qualitative and quantitative comparisons of the execution of different versions of a given decision service– Real-time: champion-challenger

– Off-line: data mining and analytics

21

Task 10: Validate - Motivations

21


Functionality Overview

– Ready for immediate use ruleset testing in Rule Team Server

– Business impact simulation in Rule Team Server

– Scenario configuration and customization in Rule Studio

– Audit - Decision Warehouse in Rule Execution Server

22

Task 10: Validate – Decision Validation Services (DVS)

22


Scenarios

– A scenario defines a real or fictitious use case that contains the necessary input to execute a decision service properly

– Support for Microsoft® Excel® for defining scenarios

– Specific “scenario providers” can be implemented to use alternate format such as databases

Test Suites

– Test suites enable to compare the outcome of a set of scenarios against expected results

– Expected results and expected execution details can be defined Example: the list of rules expected to execute

Simulation Suites

– enables the evaluation of one or more KPIs against a set of scenarios

– KPIs must be defined in Rule Studio

23

Task 10: Validate – Fundamental Concepts

23


Individual ScenarioResult

ConsolidatedResults

RTS Test Suite Results

Detailed ScenarioReports

24

Task 10: Test Suite in Rule Team Server (RTS)

24




ManageManage9




Rule Team Server

PublishPublish8

DeployDeploy11

Rule Studio

DesignDesign1


AuthorAuthor3

DeployDeploy6

IntegrateIntegrate7

AuditAudit12




Task 11: Deploy

25

TestTest4

DebugDebug5


Rules can get deployed either from Rule Team Server to the Rule Execution Server.

Hot-deploy rule changes in minutes

deploymentdeploymentdeploymentdeploymentRule Studio Rule Team

Server

Rule ExecutionServer

Task 11: Deploying from Rule Team Server

26


Agenda








AuthorAuthor




Rule Team Server

PublishPublish8

Rule Studio

DesignDesign1


AuthorAuthor3

TestTest4

DebugDebug5

DeployDeploy6

IntegrateIntegrate7

AuditAudit12




Task 1: Design

28

ValidateValidate10

ManageManage9

DeployDeploy11


Rule Studio is the development environment for business rule applications. Developers can take advantage of this integration with Eclipse to develop their Java projects along with rule projects.

Rule Perspective

Rule Project

Rule Project Map

Task 1: Rule Studio

29


Easy to learn

– Familiar environment

– Project map for new users

– Follows Eclipse style and design guidelines

– Complete Comprehensive Documentation

– Tutorials and Samples

Easy to use

– Auto-completion in rule text editor

– Wizard-Driven

Productivity

– Wizard-driven Java, XML, WSDL data integration

– Automatic Vocabulary Generation

– Re-factoring

– Queries

– Integrated Rules and Java debugging

30

Task 1: Rule Studio Low cost of ownership for developers

30


The business logic of your application is stored in a rule project. A rule project enables you to manage, build, and debug the artifacts that comprise the business logic of your application.

A rule project is a container for rules and for the artifacts needed to create them and manage them:

– Business Object Model (BOM)

– Rule templates

– Queries

A project can refer to another rule project.It will have access to all artifacts.

Repository

Project

BOM

*

Rules QueriesTemplates

Task 1: Rule Project

31


Before writing any rules a vocabulary must be prepared

The vocabulary is defined by a Business Object Model (BOM)

– BOM classes are “Terms”

– Class members are “Phrases” to be used as conditions or actions

A BOM is based on an eXecutable Object Model (XOM)

– XOM can be Java classes, XML Schemas

– Not necessarily one to one mapping. A BOM can have virtual artifacts with explicit BOM to XOM mapping defined

Task 1: Business Object Model (BOM)

32


Task 1: BOM (2/5)

33


Rule Studio provides a dedicated editor to prepare the BOM

Term verbalization

BOM navigation

Discrete domain definition

Rule category applicability

BOM class editor

Custom BOM to XOM mapping

Task 1: BOM (3/5)

34


Phrase verbalization

Discrete domain definition

Class member editor

Custom BOM to XOM mapping

Rule category applicability

Task 1: BOM (4/5)

35


BOM Entry

BOM folder

Java classes

BOM class created from the Java classes « miniloan-xom »

Task 1: BOM (5/5)

36


A rule service is defined by a ruleset containing:

– a set of input/output parameters

– a ruleflow orchestrating the execution of the rules

– a set of rules artifacts grouped into several packages

boolean Eligibility (Customer cust)Risk Scoring (CreditRequest request)

Business applicationRule-based Decision Service

IN

OUT

Task 1: Ruleset parameters

37



AuthorAuthor




Rule Team Server

PublishPublish8

Rule Studio

DesignDesign1


AuthorAuthor3

TestTest4

DebugDebug5

DeployDeploy6

IntegrateIntegrate7

AuditAudit12




Task 2: Orchestrate

38

ValidateValidate10

ManageManage9

DeployDeploy11


A rule package is a container for rule artifacts:

Free text rules written in a pseudo naturallanguage, Business Action Language

Decision tables

Decision trees

Functions written in interpreted Java enabling to perform technical tasks

Ruleflows

Project

Rule

*

Top-level container

Package

*

**

Rule project structure and rule packaging should be carefully designed to enable easy maintenance and efficient execution.

39

Task 2: Rule packages

39


A ruleflow is an executable procedural diagram composed of tasks and transitions between tasks

A rule task maps to a rule package : When the task is traversed, the rules in the package are evaluated.

A function task contains interpreted Java code performing technical computation (external data access, etc)

A flow task maps to another ruleflow module that can be reused across many higher level ruleflows

Any task can be enriched with initial and/or final actions in interpreted Java

40

Task 2: What is a ruleflow?

40



AuthorAuthor




Rule Team Server

PublishPublish8

Rule Studio

DesignDesign1


AuthorAuthor3

DeployDeploy6

IntegrateIntegrate7

AuditAudit12




Task 3: Author

41

TestTest4

DebugDebug5

ValidateValidate10

ManageManage9

DeployDeploy11


Repository

Project

Rule

*

Top-level container

Package

*

*

**

•A repository includes a set of projects that may reference each other

•A project is a container for business rules along with the elements needed to define them (rule artifacts, BOM, rule templates, queries)

•A container for rule artifacts and packages (rules, rule flows, functions, variables, rule packages)

•A container for rule artifacts and packages (rules, rule flows, functions, variables, rule packages)

•A rule (action rule, decision table, decision tree, technical rule)

42

Task 3: Author – A hierarchy of artifacts

42


Using ILOG JRules, business logic is expressed using rule artifacts based on the vocabulary of all the “visible” BOMs

Rule Artifacts

business rules decision tables decision trees ruleflows

BOM

Vocabulary

Task 3: Write rules

43


Anatomy of a rule

Rulesetparameter

definitions

conditions

actions

Localvariable

rule name rule documentation rule category

Task 3: Business Action Language (BAL) rule

44


Concise way of representing sets of business rules that have a uniform structure in the form of a spreadsheet

columnheader

rows

rowheader condition column action column

45

Task 3: Decision Table

45



AuthorAuthor




Rule Team Server

PublishPublish8

Rule Studio

DesignDesign1


AuthorAuthor3

TestTest4

DebugDebug5

DeployDeploy6

IntegrateIntegrate7

AuditAudit12




Task 4: Test

46

ValidateValidate10

ManageManage9

DeployDeploy11


Decision Validation Services allow for testing and simulation of rulesets in RTS and Studio– Non regression testing for QA– Functional tests and simulations for developers and business analysts

Based on concepts of usage scenarios:– A usage scenario represent a use case– A usage scenario is composed of:

• a ruleset, • An input data set (Excel by default)

Testing– A set of expected values for the output parameters is associated with the

usage scenario

Simulation– A simulation will be based on a (often large) set of usage scenario without

expected results but with a KPI (Key Performance Indicator)

Reports– Test and Simulation runs generate reports

47

Task 4: Test – Testing & Simulation

47


Input Data

Expected Results

RulesetTests

48

Task 4: Test – Scenario Definition

48


GeneratedScenario Document

Configurationediting

Detailed ScenarioReports

49

Task 4: Test – Test suite in Rule Studio

49



AuthorAuthor




Rule Team Server

PublishPublish8

Rule Studio

DesignDesign1


AuthorAuthor3

TestTest4

DebugDebug5

DeployDeploy6

IntegrateIntegrate7

AuditAudit12




Task 5: Debug

50

ValidateValidate10

ManageManage9

DeployDeploy11


With the Debugger, the process of business rule execution can be controlled by:

– Step into, step over, and step return in any given block of business rule.

– Resume, suspend, and terminate.

– Setting breakpoints on rules, classes, and objects.

Task 5: Debug rules

51



AuthorAuthor




Rule Team Server

PublishPublish8

Rule Studio

DesignDesign1


AuthorAuthor3

DeployDeploy6

IntegrateIntegrate7

AuditAudit12




Task 6: Deploy

52

TestTest4

DebugDebug5

ValidateValidate10

ManageManage9

DeployDeploy11


Rulesets are packaged as RuleApp for deployment and execution

A RuleApp is a deployable management unit that contains one or more RuleSets

Each RuleSet is the invocation unit when executing the rules

Several RuleSets can be packaged in the same RuleApp for management purpose

Each RuleSet has its own:

– Signature: Input/Output parameters

– Content:

• Rules

• Ruleflows

• Variables

• Functions

A ruleset is the minimal executable resource, identified as:– /<ruleapp>/<ruleapp-version>/<ruleset>/<ruleset-version>

RuleApp: name, version, creation date, etc.

RuleSet: name, version, parameters, rules, ruleflow, etc.

RuleSet: name, version, parameters, rules, ruleflow, etc.

53

Task 6: Deployment and Execution

53


RuleApps can get deployed either from Rule Studio or/and Rule Team Server to the Rule Execution Server.

RES (Rule Execution Server)

– managed business rule execution platform that embeds JRules engine

– Persists rulesets in database in the file system

– Communicates with Rule Studio (RS) and Rule Team Server (RTS)

deploymentdeploymentdeploymentdeploymentRule Studio Rule Team

Server

Rule ExecutionServer

Task 6: Deploying from Rule Studio

54



AuthorAuthor




Rule Team Server

PublishPublish8

Rule Studio

DesignDesign1


AuthorAuthor3

DeployDeploy6

IntegrateIntegrate7

AuditAudit12




Task 7: Integrate

55

TestTest4

DebugDebug5

ValidateValidate10

ManageManage9

DeployDeploy11


Managed environment for executing rules

Set of independent, but cooperating, software modules that interact with the rule engine

– Provide management, performance, security, and logging capabilities

Flexible modular architecture can service different server clients and integration with enterprise infrastructure

– Enables you to dynamically change business logic in Java SE, Java EE and SOA environments

– Can handle rule execution for multiple applications

56

Task 7: What is the Rule Execution Server (RES)?

56


Ruleset change notificationMonitoring data gathering

Console

Management Model

Persistence Layer

JMX

Execution Unit (XU)

Execution Components

Persistence Layer

Rule Studio

Rule Team Server

Database /File System

Management stack Execution stack

57

Task 7: Rule Execution Server components

57


Execution components: stub components (rule sessions, rule Message Driven Beans MDB and so on) used in the business logic layer to invoke rule service execution

Execution Units: J2EE Connector Architecture-compliant components that manage rule execution.

– Rule engine pooling (connection management)

– Secure access to rule engines (through rule sessions)

– Ruleset hot update

– Ruleset tracing and monitoring

Persistence layer: retrieves rulesets from the database for execution.

58

Task 7: Execution stack

58


Management Console

– The Rule Execution Server is accessed through the Rule Execution Server Console, a web-based administration interface

– The console acts as an application-specific interface to manage business rules, including remote browsing, updating and deployment of RuleApps

– Central point of the Rule Execution Server architecture

JMX Management Model components

– Based on JMX (Java Management eXtension), a part of Java SE

– Responsible for:

• Hot update / deployment: when a new version of a ruleset is deployed, the console notifies through the JMX control all XUs in the cluster that a new version of the ruleset is available in database

• Exposing execution statistics as MBeans which can be then monitored using JMX tools such as IBM Tivoli® software

59

Task 7: Management and monitoring stack

59


File persistence

– Targets the Java SE platform

– Is useful for testing on a single local instance of the application server

Database persistence

– Recommended option when deploying to a Java EE cluster

60

Task 7: Persistence layer

60


Rule Execution Server provides a series of Management Ant Tasks and Persistence Ant Tasks for automation purpose

Use Management Ant tasks to automate RuleApp deployment and un-deployment in Rule Execution Server.

With Persistence Ant tasks, you directly access the persistence layer, storing or removing rulesets and RuleApps directly in the database, without passing through the Management stack (JMX)

– If you use Persistence Ant tasks to deploy rulesets or RuleApps, there will be no notification, no hot deployment, and the Rule Execution Server console will not be aware of this deployment

61

Task 7: Ant tasks

61


Task 7: Integration options

62

Application Integration– J2SE with direct API control– J2SE managed service– J2EE managed service– SCA components– Web Service

Data Integration– Java– XML

Operating Systems– Microsoft Windows® – UNIX® or Linux®– Mainframe (IBM z/OS®)

J2EE architecture– J2EE RES– Standard J2EE service interface for remote clients– In-memory/local invocation for co-hosted clients– POJO application controller– App Server handles security, transactions, session

replication

J2EEJ2EE

Rulesets+ Metadata

Session BeanMDBServlet…

Session BeanMDBServlet…

RuntimeAuditTrail

RuntimeAuditTrail

Execution Unit(XU).rar

ManagementStack.ear

Service Interface

POJO controllerPOJO controller

Service Implementation


LocalRulesetRepository

ExternalClient

JMSRMI

IIOPSOAPHTTP

Local client


WebSphere ILOG JRules in the SOA Reference Architecture

63

Business Innovation & Optimization Services

Dev

elo

pm

ent

Ser

vice

s

Interaction Services Process Services Information Services

Partner Services Business App Services Access Services

ESBFacilitates communication between services

IT S

ervi

ceM

anag

emen

t

Infrastructure Services

Rule integration Rule authoring, governance, testing and simulation

Complex decisionautomation

QoS

Personalization Process routing Data processing


Rule Team Server Rule Solutions for OfficeRule Studio(Eclipse)


The business logic within business processes changes

more frequently than the business processes themselves

BPM & BRMS interoperability overview

Fraud

Detection

ReviewProcess

Order

Order

Validation

YesNo

Order validation rules

Fraud detection rules

Computation rules

Order parameter

Report parameter

(for example, exception)

Exception?

NoYes

Exception

handling

Orderaccepted?

Rule Repository

Rule Repository

TransparentDecision

Service

TransparentDecision

Service

Rule DesignerRule Designer

Deploy rules

BPM WebSphere ILOG JRules

64


Integration with the IBM WebSphere Process ServerDecision Service Wizard (Service Component Architecture - SCA)

65



AuthorAuthor




Rule Team Server

PublishPublish8

Rule Studio

DesignDesign1


AuthorAuthor3

DeployDeploy6

IntegrateIntegrate7

AuditAudit12




Task 8: Publish

66

TestTest4

DebugDebug5

ValidateValidate10

ManageManage9

DeployDeploy11


Rule Synchronization

– In Rule Studio users edit rule projects stored in an Eclipse workspace; In Rule Team Server users edit rule projects stored in the reference rule repository stored in a relational database

– Synchronization goes in both directions

– Differences are managed in the Synchronization perspective of Eclipse

Rule Studio Rule TeamServer

Project Synchronization

Task 8: Publishing to Rule Team Server (1/3)

67


A project is the unit of synchronization between Rule Studio (RS) and Rule Team Server (RTS)

The default ruleset extraction maps a rule project to a ruleset

RTS views one project at a time

Security settings within RTS are project-specific

68

Task 8: Publish – Rule projects

68



AuthorAuthor




Rule Team Server

PublishPublish8

Rule Studio

DesignDesign1


AuthorAuthor3

DeployDeploy6

IntegrateIntegrate7

AuditAudit12




Task 12: Audit

69

TestTest4

DebugDebug5

ValidateValidate10

ManageManage9

DeployDeploy11


Traces decisions in production applications

– Logs execution trace

– Input / Output data

– Execution results

– Executed Tasks

– Rules Fired

– Queries

– Open API to connect third-party business intelligence (BI) tools

Task 12: Audit – Decision Warehouse

70


Task 12: Audit – Decision Warehouse

71


Agenda







What are the challenges using rules?

Business involvement and new business processes– How do I know when rules change?– Where can I find the rules?

Data modeling– What is the business vocabulary?– Where do my business objects come from?

Rule acquisition, modeling, and execution– What is the complexity of rules? How do I write new rules?– How do I validate the rules?

Integration, performance, and scalability– Will I have good performance at full production scale?– How do I integrate business rules into my IT architecture?

73


Agile Business Rule Development

RuleDiscovery

RuleAnalysis

RuleAuthoring

RuleValidation

RuleDeployment

Maintenance

Complement

Improve

Enhance

New Rule Set

Capture the raw business rules for one decision service

Harvest rule using short workshop sessions

Form a set of coherent business rules

applying industry standard benchmarks,

including redundancy and overlap

checks

Isolate and factor out common rules

• Develop domain object model

• Design a scalable rule repository

structure

• Develop ruleflow, rules, decision

tables… Test in Sandbox deployment environment

Involve subject matter expert (SME) for

feedback

Use rule execution server staging

platform74


Discovery Workshop

75

Preparation Meeting

Project Goals

ILOG Offering

- Business objectives- Walk thru use cases- ILOG capabilities

Business Session

Business Goals

ILOG Offering

Implementation Approach

Suggested next steps

Wrap-up Session

- IT issues / goals- IT infrastructure- ILOG technology

Architecture Session

- Methodology aspects- High level project plan- Important Milestones

Implementation Session


Application Assessment

Scope Experts will interview key SMEs to refine the requirements and use cases, and develop a proposed architecture, design, and plan. A report with these findings will be presented to executives.

Context This is intended for clients who have already identified a target project and use cases and would like help outlining a plan for building the BRMS application to support this project.

Benefits ● Identify the most feasible plan for best meeting the requirements● Set expectations from the beginning● Identify risks and mitigation techniques early on

Duration 10 days (23 man-days workload)

Resources 1 BRMS Project Manager (PM)1 BRMS Architect1 Business Policy Consultant

RIGHT START

Set yourself up for success by planning and designing your BRMS applications with IBM experts

76


Value of BRMS

Improved agility

– Business Decisions and Rules can be more easily accessed and changed

– Business Decisions and Rules can be reused across applications

Improved time to market

– Line of Business Managers can manage and change rules

– Quick response to market and regulatory changes

Management of rule based decisions

– Improved regulatory compliance

– Consistency in applying business decisions across applications

Incremental application modernization

– Incrementally modernize business applications by managing business logic

independently of technical services

77


Central resource for developers, architects and IT managers to share industry knowledge, experience and best practices surrounding BRMS.

IBM developerWorks - BMRS Resources

http://www.ibm.com/developerworks/websphere/zones/brms

78


We appreciate your feedback. Please fill out the survey form in order to improve this educational event.

SIMPLIFIED CHINESEHINDI JAPANESE

ARABICRUSSIANTRADITIONAL CHINESE TAMIL THAI

FRENCH

GERMAN

ITALIAN

SPANISH

BRAZILIAN PORTUGUESE


Backup Slides


“Miniloan” Scenario Background Information


Learn by example about “Business Rule Management with ILOG JRules”

Walk through all the tasks of BR management life cycle

Exercises divided in three separate laboratories:

– Business Rule Management and Authoring : Focused on the Business Rule Management activities by business users

– Business Rule Application Development : Focused on the BRMS development activities by developers

– Enterprise Application : Focused on the BRMS deployment activities by developers

Objectives

83


Company profile

– Mid-size mortgage bank

– Sells loans to individuals

Company objectives

– Build a re-usable risk qualification function for loan applications based on their corporate business policies and compliant with regulations

– Build a flexible implementation in order to minimize the effort needed to update these policies

– Involve different roles (analyst, developer, administrator) in policy maintenance.

Scenario: Business Case

84


Scenario: Functional Architecture

85

Rule-basedDecision Service

Web Application

IT users Business users

Rule Repository

• Validation rules• Eligibility rules

Input/Output

LOANLOAN

BORROWERBORROWER

© 2010 ibm corporation ilog jrules overview roles-based tour and intro to business rule management...

Documents

business rules issues

business logic

business needs

business users

business change drives

rule solutions

rule studio design

time rules