Milan Milanović 1 and Dragan Gašević 2 1 University of Belgrade, Serbia 2 Athabasca University, Canada Towards a Language for Rule-enhanced Business Process Modeling
Towards a Language for Rule-enhanced Business Process Modeling
May 10, 2015
Presentation of the EDOC 2009 paper:
Business process modeling is a commonly used approach in the development of service-oriented architectures. The previous research on this topic demonstrated that process-oriented models might be too rigid for dynamic adaptations of the business logic. Rule-based approaches are considered an alternative, which offers more flexibility thanks to the declarative nature of rules and their underlying reasoning algorithms. However, modeling a business process through rules is a tedious process for developers in terms of the overall business process comprehension. In this paper, we propose a hybrid solution – a modeling language that integrates both rule- and process-oriented modeling perspectives. The language (Rule-based BPMN –rBPMN) is based on the integration of the Business Process Modeling Notation with the REWERSE Rule Markup Language. In this paper, after introducing rBPMN, we report on the experience in modeling of Service-Oriented Architectures (SOA) from the perspective of message exchange patterns.
http://dx.doi.org/10.1109/EDOC.2009.12
Business process modeling is a commonly used approach in the development of service-oriented architectures. The previous research on this topic demonstrated that process-oriented models might be too rigid for dynamic adaptations of the business logic. Rule-based approaches are considered an alternative, which offers more flexibility thanks to the declarative nature of rules and their underlying reasoning algorithms. However, modeling a business process through rules is a tedious process for developers in terms of the overall business process comprehension. In this paper, we propose a hybrid solution – a modeling language that integrates both rule- and process-oriented modeling perspectives. The language (Rule-based BPMN –rBPMN) is based on the integration of the Business Process Modeling Notation with the REWERSE Rule Markup Language. In this paper, after introducing rBPMN, we report on the experience in modeling of Service-Oriented Architectures (SOA) from the perspective of message exchange patterns.
http://dx.doi.org/10.1109/EDOC.2009.12
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Milan Milanović1 and Dragan Gašević2 1University of Belgrade, Serbia2Athabasca University, Canada
Towards a Language for Rule-enhanced
Business Process Modeling
2
Connecting process models and vocabularies Effective updates of process models Smaller chunks of business logic in processes Visualizing business logic exchange
EDOC 2009
Motivation
3
Approach Language that combines
business rules and business processes Following model-driven engineering Evaluation on message exchange patterns
EDOC 2009
4EDOC 2009
Background Rule-enhanced BPMN
o BPMN language and metamodelo R2ML language and metamodelo rBPMN language and metamodel
Case studyo Message Exchange Patterns
Conclusion and future work
Outline
5
Background Business processes
o Coordinated set of activitieso Business goalso Model: activities, participants, organizational
structures, goals, policies, and vocabularieso Model perspectives
• Control flow, data flow, interaction, …o BPMN language
6
Background Business rules
“A statement that defines or constraints some aspect of the business. It is intended to assert business structure or to control or influence the behavior of the business.”
BRG, 2009 Types [Wanger, 2005]
oDerivation, integrity, production, and reaction Standardization efforts: RIF, SBVR, and PRR
7
Background Business processes and business rules
o Fully rule-based• Reaction and production rules
• Comprehension• Execution flow at run-time• No support for different rules & low-level representation
o Hybrid approaches• Graml et al., 2007: control flow decisions,
data constraints, process composition
8
Goal Systematic definition of
a rule-based business modeling language
9
Rule-enhanced BPMN MDE as a solution
o Language engineering with metamodelingo Business process and rule (meta)models
• Integration on the level of the metamodels• Validity of expressions in models
o Integration of BPMN and R2ML languages
EDOC 2009
10
Modeling elementso Flow objecto Connecting objectso Pools
EDOC 2009
BPMN Language
11
Business Process Model and Notation (BPMN) Specification 2.0, initial submission,
http://www.omg.org/cgi-bin/doc?bmi/08-02-06, 2008
EDOC 2009
BPMN Metamodel
12
REWERSE I1 Rule Markup Languageo Four rule typeso Organization
• R2ML MOF-based metamodel for rules• R2ML XML Schema• UML-based Rule Modeling Language (URML)• Transformations
Towards a Language for Rule-enhanced Business Process ModelingEDOC 2009 12
Rule Modeling Language
13EDOC 2009
R2ML Metamodel
14
URML DetailsExtension of UML for rule modelingVocabularies by using UML class models
o Rules are defined on top of such models
EDOC 2009
15EDOC 2009
On a patient information request, if the user is registered and provided valid credentials, retrieve the requested information and notify the user.
Otherwise, send a fault message.
16EDOC 2009
rBPMN Metamodel
17
rBPMN metamodel
EDOC 2009
18
Activity extensions: Tasks and Subprocesses
EDOC 2009
rBPMN metamodel
19
rBPMN data model: Correlation information
EDOC 2009
rBPMN Metamodel
20
Service-oriented health information system Message Exchange Patterns
o Types and order of messages o Inbound patterns
• Initiated by service requestorso Outbound patterns
• Initiated by services themselves
MEPs modeled by reaction rules
EDOC 2009
Case Study
21
In-Out MEP (with fault replaces message)
EDOC 2009
Message Exchange Patterns
22
23
Out-In Pattern (with fault)
EDOC 2009
Message Exchange Patterns
24
Related Work
Types of rules Approach Process lang. Rule lang. Integration
IR DR PR RR Modeling standards
McBrien & Seltveit PID ERL Graphical syntax + + - + None Knolmayer et al. Extended ECAA ECA notation Graphical syntax - - - + None
Charfi & Mezini BPEL AO4BPEL Hard-coded via aspect oriented programming
+ + - + None
Meng et al. WPDL Hard-coded (CBRSL)
Graphical syntax and metamodel-based
- - + - -
Rosenberg & Dustdar BPEL Jess, RuleML Web service based and hard-coded
+ + - + None
Orriëns et al AGFIL-BM RuleML Graphical & textual syntax + + - + None Bry et al. XChange XChange Hard-coded (procedural) - - - + None
Goedertier & Vanthienen EM-BRACE PENELOPE and hard-coded
Graphical syntax and metamodel-based
+ + + + BPMN, SBRV
Graml et al. BPEL Java Graphical syntax and hard-coded
+ + + - BPMN
Eijndhoven et al. BPMN iLOG JRules Transformations - - - + BPMN
25
Conclusion Integration of rules and processes Supported patterns by Graml et al. Visualization for rule interchange Verification of shared rules
EDOC 2009
26
Future Work Workflow and service-interaction patterns Mapping onto and extending BPEL Structured natural language for rules Policies with business processes
EDOC 2009
Related Documents
