Contributed on May 14, 2014

2.8K

1.8K

Capturing and documenting business processes and rules for agility

Description

Combining Business Rules documentation and Process Modelling for business agility

Transcript

Combining Business Rules documentation and
Process Modelling for business agility
Capturing and documenting
Process and Rules
© Copyright 2012 Process Agility Limited
Model Process and Rules – Combined for Agility
Agenda
© Copyright 2012 Process Agility Limited
What are Business Rules?
BRMS
Model Process and Rules – Combined for agility
Benefits
Why Capture Business Rules?
Methodology
Business Rules Engines
1
2
3
4
5
6
7
How to streamline processes end to end
What are Business Rules?
© Copyright 2012 Process Agility Limited
Business logic to be
implemented in one or
more business
applications
The IT perspective
Formal statements of
business policy that
define or constrain
some aspect of the
business
The business perspective
21
Customer credit is = High and customer salary is > £45,000,
and customer spends > £10k a year, and credit balance <= £5k
then customer is Preferred
Why Capture Business Rules?
• Problem: Change is constant
– Regulations
– Market fluctuations
– New technologies
• Solution: Business Rules
– Core concepts & policies
– Basic business vocabulary
– Essence of business “know-how”
Why Capture Business Rules?
The Continuous Drive for Change
Crisis
Regulation
Market
Competition
Internal process
Drivers for Change
Business Operations
New Product Lines
New Segments
New Territories
Attractive Offerings
New Services
New Bundles
Reorganisation
Restructuring
M&A
Dodd–Frank
SOX
Breakouts
Unexpected
Events
Why Capture Business Rules?
The Continuous Drive for Change
• New Product
• New Policy
• New Regulation
• New Pricing Rules / Model
• New Scoring Rules / Tables
…
Streamlined process
works fine until…
Request for
Change
Why Capture Business Rules?
The Continuous Drive for Change
Many Decision element exists
throughout the process, such as:
• Pricing / Quoting
• Eligibility Determination
• Scoring
• Case Assignment
• Data validation / Compliance
• Reconciliation / Transformation
• ..
• .
• Historically, organisation do not combine their
process modeling with business rule
documentation
• Combine these two aspects to provide a
complete Model and;
• Make business processes intelligent
• Improve communication between Business & IT
• Lead to integration with business rule engines
• Implement fit IT solutions that provide better business
benefits
Model Process and Rules
Combined for agility
Create a combined model for business processes
and business rules; bridge the communication gap
between business and IT
Combined approach makes business architecture
management easy when in done one tool.
© Copyright 2012 Process Agility Limited
Combine rules and processes for agility
Methodology
Step 3: Describe
the Business
Rule
Step 2: Identify
the Business
Rules
Step 1: Capture
the processes
Step 1: Model the processes
Business process modelling using the BPMN notation
Identify the steps in the process that rely on business rules
Step 2: Identify the Business Rules
Step 3: Describe the Business Rule
Benefits of combining Rules and
Processes
• Process Flows and Rules are accessible to business users
– Improves compliance and auditability
• Rules are externalized from the process
– Improves responsiveness to business change
– Impacts all the running processes if needed
• “No human touch”: Business Rules automate routine
decisions
– Reduces transaction costs
– Shortens process cycle time
Process Automation Matuiry Model
Data driven diagram – Bar diagram
© Copyright 2012 Process Agility Limited
Little or No
Automation
Manual Processes,
Many Human
interactions
and exchanges
Automated Workflows
Fewer Human interventions
mostly for Decision-making
activities
Automated Decisions
Human interventions
only for handling
exceptions
LevelofAutomation
Time
Straight-
through
processing
(STP)
Business Rules Engines
Have involved to become part of the BPM/SOA stack
• PegaRULES Process Commander
– combines rules and process engine with tools for developing enterprise-wide
business process applications.
• Haley Systems and RuleBurst were acquired by Oracle
– Now part of
• ILOG was acquired by IBM
– Now renamed
• Corticom was acquired by Progress Software
• RulesPower was acquired by FICO
THANK YOU!
Michael Moyal
Independent Technology Consultant
BPM, Business Analyst, Solution Architect & Change Management
michael@process-agility.com
Your Logo