1. Verification and transformation of
BPEL processes

2. Agenda BPEL Transformation Verification Conclusions QUT Ouyang c.s.
HU Stahl c.s.
VV Bisgaard Lassen c.s.
Verification
Soundness
Operational guideline
Conclusions

3. BPEL – Basic activities
invoke
reply
receive
empty
assign
wait
throw
compensate
terminate

4. BPEL – Structured activities
sequence
switch
pick
while
flow
links
transition condition
join condition
dead path elimination

5. BPEL – Scopes variables event handlers fault handlers
compensation handler

6. BPEL – Example process

7. BPEL – Specification I
If, during the performance of structured activity S, the semantics of S dictate that activity X nested within S will not be performed as part of the behavior of S, then the status of all outgoing links from X is set to negative.

8. BPEL – Specification II
If during the execution of a business process instance, two or more receive activities for the same partner link, portType, operation and correlation set(s) are in fact simultaneously enabled, then the standard fault bpws:conflictingReceive MUST be thrown by a compliant implementation.

9. QUT – Basic activity Positive path Negative path
Synchronous faults (not shown)

10. HU – Basic activity (Receive)
Positive path
Communication place
Asynchronous faults

11. QUT – Links
Join condition
Negative path (not shown)

12. HU – Links
Outgoing links

13. QUT – Switch
Negative paths

14. HU – Switch
Outgoing links

15. Demo – ProM QUT HU Soundness State spaces Conflicting receives?
Transformation
Verification
QUT HU
Soundness
State spaces
Conflicting receives?

16. VV
Patterns
Library
Extensions

17. VV – Example I

18. VV – Example II

19. VV – Example III

20. VV – Example IV

21. VV – Example V

22. VV – Example VI

23. VV – Case study I

24. VV – Case study II

25. Demo – ProM
Transformation VV

26. BPEL – Conclusions Semantics? BPEL 2.0? Complexity Pragmatic approach
Event handlers
Fault handlers
Compensation handlers
Pragmatic approach
BPEL 2.0?
Tons of issues