process-flexibility.com

Monday, 27 May 2013 14:50

WS-BPEL4People

Evaluation

Ratings can take the form '+' which indicates that a particular tool or language provides direct support for the pattern involved, '+/-' which indicates that some limitations exists regaring direct support, and '-' which indicates that no direct support is provided. If support is not specified this is indicated by the label '0'.

Pattern Design Choice Score Comment
System-specific Design Choices A[a,c], B[a?,b?,c?] +/- partially supported
A Parameters of a pattern may be set at a build-time +
b instantiation time -
c run-time +
B Time parameters can be specified in different time
granularities
a Basic 0 not specified
b System-defined 0 not specified
c User-defined 0 not specified
TP1 Time Lags between two Activities D[a,b*,c*], E[c] +/-
D There are three kinds of restrictions a Minimum value + supported using wait
b Maximum value +/- can be realized using deferred choice
c Time interval +/- a & b
E Time lags can be realized based on four different time relations a Start-Start -
b Start-End -
c End-Start + supported using wait
d End-End -
TP2 Durations C[a,c*], D[b] +/- partially supported using scheduled action
C Patterns can be applied to different process elements a Single activity + supported
b Activity set -
c Process model +/- wrap the whole process then treat it like an activity
d Set of process instances -
D There are three kinds of restrictions a Minimum value -
b Maximum value + supported using scheduled action
c Time interval -
TP3 Time Lags between Arbitrary Events D[a] +/- not supported
D There are three kinds of restrictions a Minimum value + supported using wait
b Maximum value -
c Time interval -
TP4 Fixed Date Elements C[a], F[a,d] +/- partially supported using scheduled action
C Patterns can be applied to different process elements a Single activity + supported
c Process model -
F Patterns can restrict three dates of a process artifact a Earliest start date + supported using scheduled action
b Latest start date -
c Earliest completion date -
d Latest completion date + supported using scheduled action
TP5 Schedule Restricted Element - not supported
C Patterns can be applied to different process elements a Single activity -
c Process model -
F Patterns can restrict three dates of a process artifact a Earliest start date -
b Latest start date -
c Earliest completion date -
d Latest completion date -
TP6 Time Based Restrictions - not supported
G Time Based Restrictions can be applied to different types of process artifacts a activities within same process instance -
b activities within different process instances -
c Instances of a process or group of processes -
H There are two kinds of restrictions a Minimum number of executions -
b Maximum number of executions -
I There are two types of restrictions which can be expressed by Time Based Restrictions a Number of concurrent executions -
b Number of executions per time period -
TP7 Validity Period - not supported
C Patterns can be applied to different process elements a Single activity -
c Process model -
F Patterns can restrict three dates of a process artifact a Earliest start date -
b Latest start date -
c Earliest completion date -
d Latest completion date -
TP8 Time Dependent Variability J[a,b*] +/- partially supported
J There are different time aspects which may be considered by an instance of this pattern a Execution time of an activity / process instance + Pick with XPath expression
b Time lags between activities / events +/- Pick with Wait (deferred choice)
TP9 Cyclic Elements D[a*], E[c], K[a], L[a,b] +/- partially supported through a work-around
D There are three kinds of restrictions a Minimum value +/- can be simulated by using a wait activity in each iteration which is configured by the previous iteration
b Maximum value - not supported
c Time interval - not supported
Time Lags can be realized based on four different time relations a Start-Start - not supported
b Start-End - not supported
c End-Start + supported
d End-End - not supported
K Cyclic Elements may restrict the time lag between  a two directly succeeding iterations + supported
b two subsequent activity instances belonging to arbitrary iterations - not supported
L Time Lag between cycles a is fixed + supported
b may vary + supported
TP10 Periodicity - not supported
M The Number of cycles is a fixed / dynamic number of iterations -
b depends on time lag and end date -
c depends on exit condition -
Read 20058 times

Involved Partners

andreaslanz 50

 

Andreas Lanz
University of Ulm, Institute of Databases and Information Systems

 

 

manfredreichert 50

Manfred Reichert
University of Ulm, Institute of Databases and Information Systems

 

 

barbaraweber 50

Barbara Weber
University of Innsbruck, Department of Computer Science

 

Get the Book!

book cover small

Important Publications

Lanz, A. and Weber, B. and Reichert, M. (2012) Time patterns for process-aware information systems.Requirements Engineering.

 

Lanz, A. and Weber, B. and Reichert, M. (2010) Workflow Time Patterns for Process-aware Information Systems. In: BPMDS'10.