Verification and transformation of

BPELTransformation

QUT Ouyang c.s. HU Stahl c.s. VV Bisgaard Lassen c.s.

Verification Soundness Operational guideline

Conclusions

invoke reply receiveemptyassignwait throwcompensate terminate

sequenceswitchpickwhileflow

links transition condition join condition dead path elimination

variablesevent handlers fault handlerscompensation handler

process

flow

switch

left! right!

exec?

exec?

start?

sequence

sequence

empty

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.

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.

Positive path Negative path Synchronous faults

(not shown)

Positive path Communication

place Asynchronous

faults

Join condition Negative path

(not shown)

Outgoing links

Negative paths

Outgoing links

TRANSFORMATION

QUT HU

VERIFICATION

Soundness State spaces Conflicting receives?

Patterns Library Extensions

TRANSFORMATION

VV

Semantics? Complexity▪ Event handlers▪ Fault handlers▪ Compensation handlers

Pragmatic approachBPEL 2.0?

Tons of issues