In-Out pattern consists of exactly two messages: a message received by a service (i.e., input message) from some other node, followed by a message (i.e., output message) sent to the other node The second message may be replaced by a fault as specified in the "Fault Replace Message" model
Towards a Language for Rule-enhanced Business Process Modeling - Presentation Transcript
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
Connecting process models and vocabularies
Effective updates of process models
Smaller chunks of business logic in processes
Visualizing business logic exchange
Motivation EDOC 2009
Approach
Language that combines business rules and business processes
Following model-driven engineering
Evaluation on message exchange patterns
EDOC 2009
Background
Rule-enhanced BPMN
BPMN language and metamodel
R2ML language and metamodel
rBPMN language and metamodel
Case study
Message Exchange Patterns
Conclusion and future work
Outline EDOC 2009
Background
Business processes
Coordinated set of activities
Business goals
Model: activities, participants, organizational structures, goals, policies, and vocabularies
Model perspectives
Control flow, data flow, interaction, …
BPMN language
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]
Derivation, integrity, production, and reaction
Standardization efforts: RIF, SBVR, and PRR
Background
Business processes and business rules
Fully rule-based
Reaction and production rules
Comprehension
Execution flow at run-time
No support for different rules & low-level representation
Hybrid approaches
Graml et al., 2007: control flow decisions, data constraints, process composition
Goal
Systematic definition of a rule-based business modeling language
Rule-enhanced BPMN
MDE as a solution
Language engineering with metamodeling
Business process and rule (meta)models
Integration on the level of the metamodels
Validity of expressions in models
Integration of BPMN and R2ML languages
EDOC 2009
Modeling elements
Flow object
Connecting objects
Pools
BPMN Language EDOC 2009
Business Process Model and Notation (BPMN) Specification 2.0, initial submission,
Rule Modeling Language Towards a Language for Rule-enhanced Business Process Modeling EDOC 2009
R2ML Metamodel EDOC 2009
URML Details
Extension of UML for rule modeling
Vocabularies by using UML class models
Rules are defined on top of such models
EDOC 2009
EDOC 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.
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.
0 comments
Post a comment