rule-enhanced business process modeling language for service choreographies
DESCRIPTION
Presentation of the MODELS 2009 paper: To address problem of modeling service choreographies, the paper tackles the following challenges of the state of the art in choreography modeling: i) choreography models are not well-connected with the underlying business vocabulary models. ii) there is limited support for decoupling parts of business logic from complete choreography models. This reduces dynamic changes of choreographies; iii) choreography models contain redundant elements of shared business logic, which might lead to an inconsistent implementation and incompatible behavior. Our proposal – rBPMN – is an extension of a business process modeling language with rule and choreography modeling support. rBPMN is defined by weaving the metamodels of the Business Process Modeling Notation (BPMN) and REWERSE Rule Markup Language (R2ML). http://dx.doi.org/10.1007/978-3-642-04425-0_25TRANSCRIPT
Rule-enhanced Business Process Modeling Language
for Service Choreographies
Milan Milanović1, Dragan Gašević2, Gerd Wagner3, and Marek Hatala4
1University of Belgrade, Serbia2Athabasca University, Canada
3Brandenburg University of Technology, Germany4Simon Fraser University, Canada
Problem Domain
Process modeling and service composition Orchestrations – CASCON 2009
Business processes from one participant’s side Choreographies
Business processes from a global perspective
Available languages (e.g., BPMN) Challenges
How to manage redundant elements? How to support business vocabularies rules?
MODELS 2009
Choreography Modeling
Extension of BPMN building on the previous related work
iBPMN [Decker & Puhlmann, 2007] adding support for vocabularies and rules
MODELS 2009
Approach
Rule-enhanced BPMN - rBPMN Interconnection and interaction models Evaluation mechanism – expressiveness
Service Interaction Patterns
MODELS 2009
Result
MODELS 2009
BPMN Language
REWERSE I1 Rule Markup Language
MODELS 2009
Extension for Rule Models
REWERSE I1 Rule Markup Language
MODELS 2009
Extension for Rule Models
Multiplicity of participants - |||
References – to distinguish participants
Correlation information – who sent a message
MODELS 2009
Interaction Models
MODELS 2009
Service Interaction Patterns
Contingent requests pattern
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.
MODELS 2009
Service Interaction Patterns
Contingent requests pattern
Expressiveness comparison
Service Interaction PatternsLanguage Pattern
group Pattern Let’s
Dance BPMN
WS-CDL
iBPMN rBPMN
Send + + + + + Receive + + + + + 1) Send/Receive + + + + + Racing incoming messages + + + + + One-to-many send + - +/- + + One-from-many receive + - + + +
2)
One-to-many send/receive + - +/- + + Multi-responses + + + + + Contingent requests +/- - +/- +/- + 3) Atomic multicast notification - - - - - Request with referral + - + + + Relayed request + - + + + 4) Dynamic routing - - +/- - +/-
Integration of rules and processes - rBPMN Externalizing business logic in rules
run-time changes Interaction and interconnection models Service interaction patterns Future work
additional scenarios for other types of rules rBPMN model checking (e.g., mCRL2/mCRL) transformations of rBPMN models into BPEL4Chor
MODELS 2009
Conclusion
Thank you!
Questions?