Upload
oliver-kopp
View
1.664
Download
2
Embed Size (px)
DESCRIPTION
Citation preview
Oliver Kopp, Matthias Wieland, Frank LeymannInstitute of Architecture of Application Systems
External and Internal Events in EPCs: e²EPCs
2nd International Workshop onEvent-Driven Business Process Management
edBPM09 – http://icep-edbpm09.fzi.de/
Presented by Matthias Wieland
Motivation
We created a development method for workflow based applications based on event-driven service-oriented architectures (SOEDA)
Wieland, M., Martin, D., Kopp, O., Leymann, F.: SOEDA: A Methodology for Specification and Implementation of Applications on a Service-Oriented Event-Driven Architecture. In: BIS 2009. (2009)
SOEDA uses MDA (Model-Driven Architecture) approachSave development time by automated transformationsTransformation of EPCs to detailed abstract BPEL workflows
SOEDA Methodology stepsStep 1: Process DefinitionStep 2: Complex Event ExtractionStep 3: Process to Workflow TransformationStep 4: CEP Rules SpecificationStep 5: Executable Completion
Presented by Matthias Wieland
SOEDA - High-Level Architecture
Automatic transformation based on: Vanhatalo, J., Völzer, H., Koehler, J.: The Refined Process Structure Tree. In: BPM 2008, Springer (2008)
CEP System
Function f1
Event e1
Event e2
Business process relevant complex events
s1 s2m1
e1 e2
f1e
Specificationlayer
Executionlayer
BPEL engine
<process> <receive e1 ... > <invoke f1 ...> <receive e2 ...></process>
Event e1:select avg(price) from OrderEvent.win:time
(30 sec)
Low Level Events
event specification
event specificationautomatic
transformation
event notification
Presented by Matthias Wieland
Problem
All EPC events are treated the same way in the automatic transformation
For every event a complex event description has to be definedAll events have to be observed by a CEP system
But: Many events are process internal eventsCould be handled “inside” the workflow without CEP systemManual optimization required
We need a EPC transformation that distinguishes external and internal events
4
Presented by Matthias Wieland 5
Example
Adapted from:Scheer, A.W. & Thomas, O. & Adam, O.:Process Modeling Using Event-Driven Process Chains.In: Process-Aware Information Systems: Bridging People andSoftware Through Process Technology. Wiley & Sons (2005)
External event,triggered by external system
Internal event,triggered by process data
6
Current Transformation Approaches
Presented by Matthias Wieland
Drop Intermediate Events
7
Mendling, J. et al, 2008ARIS Toolset (Stein, S. & Ivanov, K. 2007)
Presented by Matthias Wieland
Drop Start and End Events
8
Kopp, O. et al., 2006Specht, T. et al., 2005Ziemann, J. et al., 2005
Presented by Matthias Wieland
Interpret all Events as External Events
9
SOEDA: Wieland, M. et al., 2009
Presented by Matthias Wieland
Summary
10
11
Our new Approach:e²EPCs
Presented by Matthias Wieland
Input: e²EPCs
Explicit distinction between internal and external events by new annotations (red lines) in eEPCAim: Keep change of eEPC notation as small as possible – only following two new connections allowed
External event with organizational unit Internal event with process data
AlternativesStore type in repositoryPlace in swim lanes
12
Presented by Matthias Wieland
Transformation Result
13
Presented by Matthias Wieland
Possible Annotations
14
Presented by Matthias Wieland
Transformation Overview
15
Presented by Matthias Wieland
BPEL4Chor Result
16
Presented by Matthias Wieland
Conclusion and Outlook
Motivated why events in EPC should be distinguished between internal and external onesShowed extension of eEPC notation for modeling internal and external events: e²EPCsShowed an adequate automatic transformation toWS-BPEL and BPEL4Chor
Future Work: Evaluation of the ApproachAnnotation or annotation in the repository?Chaining of EPCs?
End Event: invoke instead of receive
17