Rule Rngineering

8/6/2019 Rule Rngineering

1/39

Business Rule Engineering

Basic Principle and Practices

Alain NeyroudILOG Technical Sales Americas

[email protected]


2/39

Agenda

Basic Concepts

Analysis & Design Consideration

Implementing

The Rule Model Verification and Validation

Governance

Q&A


3/39

Relationship between Rules and Policies

Business Rules implementBusiness Policies

Regulations implementLaws

To be understood in a similar way as

Policy Rule

Avoid payingfor nonrelatedtreatments

Ask for an audit if one of the treatment includes an emergencyroom treatment or an ambulance transfer done on a day after theaccident.


4/39

Business Rules: A Mean to an End

Business Rules Engineering is about using a modeling

abstraction and a set of supporting tools to facilitate

making changes to some of the logic of an

application/service while it is in production

Requirement

Deploy

Platform upgrade

Requirement

Deploy

Software Development

Functional enhancements

In-production Application

Accelerate Change Management

Change

Business Rules

Policy

Change

Change

Deploy

Policy

Change

Change

Deploy

Policy

Change

Change

DeployDeploy

In-production Application


5/39

Different Types of Changes

FAST

PREDICTABLE

SLOW

UNPREDICTABLE

Engineering

Operation

S f M i R l


6/39

Software Maintenance vs RuleMaintenance

Business

IT Dev / QA

Analyst Support

Business Policy Update

Business Policy Update

development productionrequirement

Operational Changes

Functional Enhancements

Regulatory Changes


7/39

Agenda

Basic Concepts


Implementing


Governance

Q&A


8/39

Traditional Software Lifecycle

Business IT Dev / QAAnalyst Support

Inception Elaboration Construction Transition Production

I1 E1 E2 T1C2 C3C1 Application Maintenance

Build-Time Run-Time


9/39

BRMS Software Lifecycle


I1 E1 T1C1 Policy Change Management

Build-Time Change-Time

E1 C1 C1


10/39

Business Rule Maintenance Lifecycle

Making the change process Easy, Safe and Predictable

Analyze

Author

Validate

Deploy


11/39

Designing the Rule Application/Service

Many Dimensions

Functional

Integration

Usability

Verification/Validation

Deployment

Governance


12/39

Scope of change (1/2)




E1 C1 C1

A system can only support capabilities that have been specified

Hence the nature and scope of the changes the application will

support must be established

It is not about capturing all the rules upfront

It is about capturing a representative set and understanding howthey will likely change in the future


13/39

Scope of Change (2/2)

DecomposeFunctionally

EvaluateVariability inTime and

Space

Define a

Rule Model

Define theVerification &

ValidationProcess

Define theGovernance

Process


14/39

Agenda

Basic Concepts


Implementing


Governance

Q&A


15/39

Implementing the Application




E1 C1 C1

Rule Framework

Rules Capture and Implementation

Rule Framework

Set of software artifacts to support the capture, validation and deployment of the

rules as well as the associated governance processRule Capture and Implementation

The initial set of Policy Management Cycles necessary to implement the minimumset of rule for the application to be operational


16/39

Agenda

Basic Concepts


Implementing


Governance

Q&A


17/39

Implementing the Framework: The Rule Model

Business Object

Model and Vocabulary


18/39


Business Object Model and

Vocabulary Rule Taxonomy and Templates


19/39




Rule Organization


20/39




Rule Organization

Rule Orchestration


21/39

Implementing the framework: The Rule Model



Rule Organization

Rule Orchestration

Rule Deployment

Rule

Repository

Validation


22/39

Agenda

Basic Concepts


Implementing


Governance

Q&A

Implementing the Framework: Verification And


23/39

Implementing the Framework: Verification AndValidation

What need to be verified

Business Objective -> simulation, Champion Challenger, Delta Testing

Change use cases -> unit testing

Service Integrity -> regression testing

How

Definition of the test cases

Using what data

Ad-hoc

Historical

Operational

Who Business User

Analyst

QA



24/39


Static Analysis



25/39


Static Analysis

Unit & Regression

Testing


26/39



27/39


Champion Challenger & Delta Testing

NewOutput Compare

Input

Test Case

Test Harness

CurrentRuleset

New

Ruleset

Current

Output

RuleEngine

Rule

Engine

Change

Definition

Test

Outcomes


28/39

Agenda

Basic Concepts


Implementing


Governance

Q&A


29/39

Rule Governance

Business

IT Dev

IT QA

Analyst

Application

Support

enhance

test

author

monitoringupdate

who can change what?

when will it take

effect?

will I break

something?

what is the impact?

what has

changed?

what do I need to

change?

who changed

what?

how do I undo achange?

Ensure efficient maintenance of the rule application through an optimal

collaboration between Business, IT and other stake holding groups

f G


30/39

Defining Rule Governance

Notes: Define a set of processes to:

Manage expectations for policy change

Control policy change analysis and implementation

Demonstrate the use and performance of the other processes

O


31/39

Outcome

Clear map of the stakeholders roles and responsibilities

How IT and Business collaborate

Separation of duties

Separation of the roles from the individuals

Awareness of the new policy change capabilities and limits Prepare the company for organizational change and agility

BRMS that is adapted to the company environment

No one tool or one process fits all

Well-defined orchestration of the rule life cycle

Consistent authoring, testing, deployment for rules

Ch ll


32/39

Challenges

Staffing of the various roles

Not perceived as priority during initial development

Multi-tasking and business urgencies during project ramp-up

Include explicit staffing task in project plan

Internal politics Fight over control, lack of mutual trust

Educate on respective roles, responsibilities

XP techniques: war room, peer programming

Lack of experience in BRMS implementation

Engage experienced BRMS specialists

Reduce the challenge by incremental implementation

Id tif St k h ld


33/39

Identify Stakeholders

Business

IT Dev

IT QA

Analyst

ApplicationSupport

BRMS

Formalize Business Policy Change


34/39

Formalize Business Policy ChangeTemplates

Inventory of probable ways in which the policies:

may or will change

with which frequency

Analysis Results In:

Template for change submission

A process map to implement the change

Accurate time and effort estimate for the change

Rule templates Precise test plan and set of test cases

D fi R l Lif C l


35/39

Define Rule Life Cycle

Define user roles

Define rule statuses

Keep it simple

Develop appropriate tools (ILOG

Jruless queries)

D fi R l S t A C t l


36/39

Define Rule Set Access Control

Map rule set responsibilities

Assign rule set owner

Assign users responsible for rule review and authoring

Rule Set

Name

Department

Owner

Policy

Manager

Rule

Reviewer

Rule

Author

Customer Loyalty Marketing Bob Reynolds John Smith Ralph Jones

Risk Assessment Risk Bob B. Bob B. Jack C.

Departments

Rule Set Marketing Risk Sale

Customer Loyalty CRUD x x

Customer Eligibility x CRU x

Pricing R x CRU

Develop rule set CRUD matrix

Pl D l t


37/39

Plan Deployment

Plan deployment procedures Test

Staging

Production

Plan production monitoring Audit trails

Performances

Development Team

`

`

Rule Studio

Development Servers

CVS Build Server

Test Platform

RES

Staging Platform

RES

Production Platform

RES

RES

RES

Rule Writers

RTS, RES, RSM Consoles

Administrator

RES Console

RTS

Q&A


38/39

38

Q&A

Questions and Answers

Wh t N t?


39/39

Whats Next?

Resources

www.ilog.com/brmsBRMS Resource Center -- explore, learn, try

blogs.ilog.com

Latest on all ILOG products, technology, and methodology

www.agileitarchitecture.comParticipate in ABRD and share ideas
http://www.ilog.com/brmshttp://blogs.ilog.com/http://www.agileitarchitecture.com/http://www.agileitarchitecture.com/http://blogs.ilog.com/http://blogs.ilog.com/http://www.ilog.com/brmshttp://www.agileitarchitecture.com/

Documents

Rule Rngineering