07.03.2014 Views

BPMN and Beyond Business process modelling notation, workflow ...

BPMN and Beyond Business process modelling notation, workflow ...

BPMN and Beyond Business process modelling notation, workflow ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Token Sets To speak about the synchronization of tokens in cycles needs the ability to express<br />

that certain tokens belong together, whereas others do not. To express such a concept we introduce<br />

token sets, i.e. sets of tokens which are viewed as a coherent group when a join fires. We will use<br />

the token sets to assign new token sets to tokens at paths that have later to be synchronized <strong>and</strong><br />

to distinguish tokens in cycles by appropriately assigned token sets. In this section we prepare the<br />

needed purely syntactical refinement, which is used in the next section to h<strong>and</strong>le the problem of<br />

cycles.<br />

We will make sure that each token t is a member of exactly one token set tokenSet(t). We<br />

assume that upon a start event a token set tokenSet(t) is generated for the start token t. When<br />

new tokens t ′ appear during the computation, their tokenSet(t ′ ) has to be defined, as happens in<br />

particular in the join rules. In the purely syntactical refinement defined in this section, the new<br />

tokens are declared to belong to the same token set as the firing tokens.<br />

We also have to refine the concept of Enabledness to guarantee that each time only tokens of<br />

one token set ts are considered.<br />

Enabled(in, ts) = (| token(in) ∩ ts |≥ inQty(in))<br />

Similarly we impose on firingToken that each time only tokens belonging to one token set are<br />

selected.<br />

if firingToken(node) = {t 1 , . . . , t n } then forall 1 ≤ i ≤ n tokenSet(t i ) = tokenSet(t 1 )<br />

This leads to the following refinement of the AND-join rule:<br />

AndJoinGateTransition(node) = WorkflowTransition(node)<br />

where<br />

let {in 1 , . . . , in n } = inArc(node)<br />

let {t 1 , . . . , t n } = firingToken(inArc(node))<br />

let ts = tokenSet(t 1 )<br />

CtlCond(node) = forall in ∈ inArc(node) Enabled(in, ts)<br />

CtlOp(node) =<br />

ConsumeAll({(t i , in i ) | 1 ≤ i ≤ n})<br />

Produce(<strong>and</strong>JoinToken({t 1 , . . . , t n }), out)<br />

tokenSet(<strong>and</strong>JoinToken({t 1 , . . . , t n })) := ts<br />

ConsumeSyncAll({(t i , in)|in ∈ AllJoinArc(out), 1 ≤ i ≤ n} ∪ {(t i , in i ) | 1 ≤ i ≤ n})<br />

ProduceSyncAll({(<strong>and</strong>JoinToken(t 1 , . . . , t n ), in)|in ∈ AllJoinArc(out)})<br />

Synchronization at an OR-join only happens among tokens of the same token set. We therefore<br />

refine the synchronization part of the control condition as follows, where ts is the given token set:<br />

CtlCondSync(node, I , ts) =<br />

forall i ∈ I syncToken(i) ∩ ts ≠ ∅ <strong>and</strong> forall i ∈ inArc(node) \ I syncToken(i) ∩ ts = ∅<br />

With these preparations we can now refine the Or-join to work only on tokens of the token set<br />

underlying the to-be-fired tokens on the selected arcs:<br />

OrJoinGateTransition(node) = WorkflowTransition(node)<br />

where<br />

let I = {in 1 , . . . , in n } = select Consume (node)<br />

let {t 1 , . . . , t n } = firingToken(I )<br />

let ts = tokenSet(t 1 ) in<br />

CtlCond(node) = (I ≠ ∅ <strong>and</strong> forall i ∈ I Enabled(i, ts) <strong>and</strong> CtlCondSync(node, I , ts))<br />

CtlOp(node) =<br />

Produce(orJoinToken(firingToken(I )), out)<br />

tokenSet(orJoinToken(firingToken(I ))) := ts<br />

ConsumeAll({(t i , in i ) | 1 ≤ i ≤ n})<br />

ConsumeSyncAll({(t i , in)|in ∈ AllJoinArc(out), 1 ≤ i ≤ n} ∪ {(t i , in i ) | 1 ≤ i ≤ n})<br />

ProduceSyncAll({(orJoinToken(t 1 , . . . , t n ), in)|in ∈ AllJoinArc(out)})<br />

15

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!