process-flexibility.com

Time Patterns

Time Patterns (28)

Monday, 27 May 2013 14:58

Zhuge et al.

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] +/- partially supported
A Parameters of a pattern may be set at a build-time + supported
b instantiation time - not supported
c run-time + supported
B Time parameters can be specified in different time
granularities
a Basic - not supported
b System-defined - not supported
c User-defined - not supported
TP1 Time Lags between two Activities D[a,b,c], E[c*] +/- partially supported
D There are three kinds of restrictions a Minimum value + supported
b Maximum value + supported
c Time interval + supported as minimum and maximum are supported
E Time lags can be realized based on four different time relations a Start-Start - not supported
b Start-End - not supported
c End-Start +/- partially supported, only succeeding activities (flow constraint d(F_ij) < D_R(F_ij) < D(F_ij))
d End-End - not supported
TP2 Durations C[a], D[a,b,c] +/- partially supported
C Patterns can be applied to different process elements a Single activity + supported (duration constraint d(A) <= D_R(A) <= D(A))
b Activity set - not supported
c Process model - not supported
d Set of process instances - not supported
D There are three kinds of restrictions a Minimum value + supported
b Maximum value + supported
c Time interval + supported as minimum and maximum are supported
TP3 Time Lags between Arbitrary Events - events are not supported
D There are three kinds of restrictions a Minimum value -
b Maximum value -
c Time interval -
TP4 Fixed Date Elements C[a], F[b] +/- partially supported
C Patterns can be applied to different process elements a Single activity + supported
c Process model - not supported
F Patterns can restrict three dates of a process artifact a Earliest start date - not supported
b Latest start date + supported (fixed-point constraints, S(A) < p)
c Earliest completion date - not supported
d Latest completion date - not supported
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 C[a?], F[b?] 0 not discussed but can be supported similar to TP4
C Patterns can be applied to different process elements a Single activity 0 similar to TP4
c Process model - not supported
F Patterns can restrict three dates of a process artifact a Earliest start date - not supported
b Latest start date 0 similar to TP4
c Earliest completion date - not supported
d Latest completion date - not supported
TP8 Time Dependent Variability - not discussed
J There are different time aspects which may be considered by an instance of this pattern a Execution time of an activity / process instance -
b Time lags between activities / events -
TP9 Cyclic Elements - not discussed
D There are three kinds of restrictions a Minimum value -
b Maximum value -
c Time interval
Time Lags can be realized based on four different time relations a Start-Start -
b Start-End -
c End-Start
d End-End -
K Cyclic Elements may restrict the time lag between  a two directly succeeding iterations -
b two subsequent activity instances belonging to arbitrary iterations -
L Time Lag between cycles a is fixed -
b may vary -
TP10 Periodicity - not discussed
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 -
Monday, 27 May 2013 14:57

Marjanovic et al.

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,b?,c?], B[a] +/- partially supported
A Parameters of a pattern may be set at a build-time +
b instantiation time 0 not discussed
c run-time 0 not discussed
B Time parameters can be specified in different time
granularities
a Basic + supported
b System-defined - not supported
c User-defined - not supported
TP1 Time Lags between two Activities D[a,b,c], F[a,b,c,d] + full support
D There are three kinds of restrictions a Minimum value + supported
b Maximum value + supported
c Time interval + supported
E Time lags can be realized based on four different time relations a Start-Start + supported
b Start-End + supported
c End-Start + supported
d End-End + supported
TP2 Durations C[a,c], D[a,b,c] + mainly supported
C Patterns can be applied to different process elements a Single activity + supported
b Activity set - not supported
c Process model + supported
d Set of process instances - not supported
D There are three kinds of restrictions a Minimum value + supported
b Maximum value + supported
c Time interval + supported
TP3 Time Lags between Arbitrary Events - Events are not supported
D There are three kinds of restrictions a Minimum value -
b Maximum value -
c Time interval -
TP4 Fixed Date Elements C[a,c*], F[a,b,c,d] + mainly supported
C Patterns can be applied to different process elements a Single activity + supported
c Process model +/- supported only for completion date
F Patterns can restrict three dates of a process artifact a Earliest start date + supported
b Latest start date + supported
c Earliest completion date + supported
d Latest completion date + supported
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 C[a?,c?], F[a?,b?,c?,d?] 0 not discussed but may be possible similar to TP4
C Patterns can be applied to different process elements a Single activity 0 not discussed but may be possible similar to TP4
c Process model 0 not discussed but may be possible similar to TP4
F Patterns can restrict three dates of a process artifact a Earliest start date 0 not discussed but may be possible similar to TP4
b Latest start date 0 not discussed but may be possible similar to TP4
c Earliest completion date 0 not discussed but may be possible similar to TP4
d Latest completion date 0 not discussed but may be possible similar to TP4
TP8 Time Dependent Variability - not 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 -
b Time lags between activities / events -
TP9 Cyclic Elements - loops are explicitly excluded
D There are three kinds of restrictions a Minimum value -
b Maximum value -
c Time interval -
Time Lags can be realized based on four different time relations a Start-Start -
b Start-End -
c End-Start -
d End-End -
K Cyclic Elements may restrict the time lag between  a two directly succeeding iterations -
b two subsequent activity instances belonging to arbitrary iterations -
L Time Lag between cycles a is fixed -
b may vary -
TP10 Periodicity - loops are explicitly excluded
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 -
Monday, 27 May 2013 14:57

Eder et al.

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,b,c], B[a*] +/-
A Parameters of a pattern may be set at a build-time + supported
b instantiation time + supported
c run-time + supported
B Time parameters can be specified in different time
granularities
a Basic +/- only one basic time granularity
b System-defined - not supported
c User-defined - not supported
TP1 Time Lags between two Activities D[a,b,c], E[d] +/- partially supported
D There are three kinds of restrictions a Minimum value + supported
b Maximum value + supported
c Time interval + combining a and b
E Time lags can be realized based on four different time relations a Start-Start - only end event are considered
b Start-End - only end event are considered
c End-Start - only end event are considered
d End-End + supported
TP2 Durations C[a,c], D[b] +/- partially supported
C Patterns can be applied to different process elements a Single activity + supported
b Activity set - not supported
c Process model + supported
d Set of process instances - not supported
D There are three kinds of restrictions a Minimum value - not supported, only end event are considered
b Maximum value + time distance between two end events
c Time interval - not supported, only end event are considered
TP3 Time Lags between Arbitrary Events - not supported
D There are three kinds of restrictions a Minimum value - no support of events in our sense
b Maximum value -
c Time interval -
TP4 Fixed Date Elements C[a], F[c] +/- partially supported
C Patterns can be applied to different process elements a Single activity + supported
c Process model - not supported
F Patterns can restrict three dates of a process artifact a Earliest start date - only end event are considered
b Latest start date - only end event are considered
c Earliest completion date + converted to a Minimum Time Lag
d Latest completion date - not supported, see c
TP5 Schedule Restricted Element C[a], F[c] +/- partially supported
C Patterns can be applied to different process elements a Single activity + supported
c Process model - not supported
F Patterns can restrict three dates of a process artifact a Earliest start date - only end event are considered
b Latest start date - only end event are considered
c Earliest completion date + converted to a Minimum Time Lag
d Latest completion date - not supported, see c
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 C[a?], F[c?,d?] +/- not discussed but may be possible similar to TP4
C Patterns can be applied to different process elements a Single activity 0 not discussed but may be possible similar to TP4
c Process model - not supported
F Patterns can restrict three dates of a process artifact a Earliest start date - not supported
b Latest start date - not supported
c Earliest completion date 0 not discussed but may be possible similar to TP4
d Latest completion date 0 not discussed but may be possible similar to TP4
TP8 Time Dependent Variability - not supported (not discussed)
J There are different time aspects which may be considered by an instance of this pattern a Execution time of an activity / process instance -
b Time lags between activities / events -
TP9 Cyclic Elements - loops are explicitly excluded from considerations
D There are three kinds of restrictions a Minimum value - loops are explicitly excluded
b Maximum value -
c Time interval -
Time Lags can be realized based on four different time relations a Start-Start -
b Start-End -
c End-Start -
d End-End -
K Cyclic Elements may restrict the time lag between  a two directly succeeding iterations -
b two subsequent activity instances belonging to arbitrary iterations -
L Time Lag between cycles a is fixed -
b may vary -
TP10 Periodicity - loops are explicitly excluded from considerations
M The Number of cycles is a fixed / dynamic number of iterations - loops are explicitly excluded
b depends on time lag and end date -
c depends on exit condition -
Monday, 27 May 2013 14:56

Combi et al.

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], B[a,b] +/- partially supported
A Parameters of a pattern may be set at a build-time + supported
b instantiation time - run-time not considered
c run-time - run-time not considered
B Time parameters can be specified in different time
granularities
a Basic + supported
b System-defined + supported
c User-defined - not supported
TP1 Time Lags between two Activities D[a,b,c], E[a,b,c,d] + supported
D There are three kinds of restrictions a Minimum value + supported
b Maximum value + supported
c Time interval + supported
E Time lags can be realized based on four different time relations a Start-Start + supported
b Start-End + supported
c End-Start + supported
d End-End + supported
TP2 Durations C[a,c], D[a,b,c] + mostly supported
C Patterns can be applied to different process elements a Single activity + supported
b Activity set - not supported
c Process model + supported
d Set of process instances - not supported
D There are three kinds of restrictions a Minimum value + supported
b Maximum value + supported
c Time interval + supported
TP3 Time Lags between Arbitrary Events D[a*,b*,c*] +/- Time Lags are only supported between events an the events of an activity not between arbitrary events.
D There are three kinds of restrictions a Minimum value +/- partially supported
b Maximum value +/- partially supported
c Time interval +/- partially supported
TP4 Fixed Date Elements C[a], F[a,b*,c,d] +/- supported
C Patterns can be applied to different process elements a Single activity + supported
c Process model - not supported
F Patterns can restrict three dates of a process artifact a Earliest start date + Absolute Constraints restrict the intervall during which an activity can be performed
b Latest start date +/- Absolute Constraints restrict the intervall during which an activity can be performed
c Earliest completion date +
d Latest completion date + Absolute Constraints restrict the intervall during which an activity can be performed
TP5 Schedule Restricted Element C[a], F[a,b] +/- partially supported
C Patterns can be applied to different process elements a Single activity + Periodic Constraints
c Process model - not supported
F Patterns can restrict three dates of a process artifact a Earliest start date + A periodic constraint represents a periodic time interval during which an activity can be started
b Latest start date + A periodic constraint represents a periodic time interval during which an activity can be started
c Earliest completion date - not supported
d Latest completion date - not supported
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 C[a], F[a,d] +/- partially supported using absolute constraint
C Patterns can be applied to different process elements a Single activity + supported
c Process model - not supported
F Patterns can restrict three dates of a process artifact a Earliest start date + supported
b Latest start date - not supported
c Earliest completion date - not supported
d Latest completion date + supported
TP8 Time Dependent Variability - not discussed
J There are different time aspects which may be considered by an instance of this pattern a Execution time of an activity / process instance -
b Time lags between activities / events -
TP9 Cyclic Elements D[a,b,c], E[a?,b?,c?,d?], K[a], L[b] +/- partially supported (but not really clear)
D There are three kinds of restrictions a Minimum value + supported
b Maximum value + supported
c Time interval + supported
Time Lags can be realized based on four different time relations a Start-Start 0 not explicitly discuss
b Start-End 0 not explicitly discuss
c End-Start 0 not explicitly discuss
d End-End 0 not explicitly discuss
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 - not supported
TP10 Periodicity M[a,b,c] +/- Periodic Constraint on loop Activity; no really complex periodicities
M The Number of cycles is a fixed / dynamic number of iterations + supported
b depends on time lag and end date + supported
c depends on exit condition + supported
Monday, 27 May 2013 14:56

Bettini et al.

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,b?,c?], B[a,b,c] + supported but not everything is discussed
A Parameters of a pattern may be set at a build-time + supported
b instantiation time 0 Not discussed but probably possible
c run-time 0 Not discussed but probably possible
B Time parameters can be specified in different time
granularities
a Basic + supported
b System-defined + supported
c User-defined + supported
TP1 Time Lags between two Activities D[a,b,c], E[a,b,c,d] + fully supported
D There are three kinds of restrictions a Minimum value + supported
b Maximum value + supported
c Time interval + supported
E Time lags can be realized based on four different time relations a Start-Start + supported
b Start-End + supported
c End-Start + supported
d End-End + supported
TP2 Durations C[a,c], D[a,b,c] +/- supported for activities and processes but not for complex constructs
C Patterns can be applied to different process elements a Single activity + supported
b Activity set - not supported
c Process model + supported
d Set of process instances - not supported
D There are three kinds of restrictions a Minimum value + supported
b Maximum value + supported
c Time interval + supported
TP3 Time Lags between Arbitrary Events D[a,b,c] + fully supported
D There are three kinds of restrictions a Minimum value + supported
b Maximum value + supported
c Time interval + supported
TP4 Fixed Date Elements C[a], F[a,b,c,d] +/- supported for activities but not for processes
C Patterns can be applied to different process elements a Single activity + Time lag between the activity and an event at time point 0
c Process model - not supported
F Patterns can restrict three dates of a process artifact a Earliest start date + supported
b Latest start date + supported
c Earliest completion date + supported
d Latest completion date + supported
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 C[a?], F[a?,b?,c?,d?] 0 not discussed but may be possible similar to TP4
C Patterns can be applied to different process elements a Single activity 0 not discussed but may be possible similar to TP4
c Process model - not supported
F Patterns can restrict three dates of a process artifact a Earliest start date 0 not discussed but may be possible similar to TP4
b Latest start date 0 not discussed but may be possible similar to TP4
c Earliest completion date 0 not discussed but may be possible similar to TP4
d Latest completion date 0 not discussed but may be possible similar to TP4
TP8 Time Dependent Variability - not supported (not discussed)
J There are different time aspects which may be considered by an instance of this pattern a Execution time of an activity / process instance -
b Time lags between activities / events -
TP9 Cyclic Elements - loops are explicitly excluded from considerations
D There are three kinds of restrictions a Minimum value -
b Maximum value -
c Time interval -
Time Lags can be realized based on four different time relations a Start-Start -
b Start-End -
c End-Start -
d End-End -
K Cyclic Elements may restrict the time lag between  a two directly succeeding iterations -
b two subsequent activity instances belonging to arbitrary iterations -
L Time Lag between cycles a is fixed -
b may vary -
TP10 Periodicity - loops are explicitly excluded from considerations
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 -
Monday, 27 May 2013 14:56

TIBCO Business Studio 3.4.2

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] +/- partially supported
A Parameters of a pattern may be set at a build-time + supported
b instantiation time - not supported
c run-time + supported
B Time parameters can be specified in different time
granularities
a Basic + supported
b System-defined - not supported
c User-defined - not supported
TP1 Time Lags between two Activities D[a,b*,c*], E[c*] +/- supported
D There are three kinds of restrictions a Minimum value + supported
b Maximum value +/- can be realized using deferred choice
c Time interval +/- can be realized by combining a and b
E Time lags can be realized based on four different time relations a Start-Start - not possible to determine the start time of an activity
b Start-End - not possible to determine the start time of an activity
c End-Start +/- supported for succeding activities only
d End-End - can be realized using signaling events, but this solution is to complex
TP2 Durations C[a,c*], D[b] +/- partially supported
C Patterns can be applied to different process elements a Single activity + supported
b Activity set - not supported
c Process model +/- wrap the whole process, then treat it like an activity
d Set of process instances - not supported
D There are three kinds of restrictions a Minimum value - not supported
b Maximum value + Non-Interupting Intermediate-Timer-Event attached to an Activity
c Time interval - not supported
TP3 Time Lags between Arbitrary Events D[a,b*,c*] +/- mainly supported (through work-arounds)
D There are three kinds of restrictions a Minimum value + Intermediate Timer Event between two Events
b Maximum value +/- can be realized using signaling events
c Time interval +/- can be realized combining a and b
TP4 Fixed Date Elements C[a,c*], F[a,b*,d] + mainly supported
C Patterns can be applied to different process elements a Single activity + supported
c Process model +/- supported, only earliest start date and latest completion date
F Patterns can restrict three dates of a process artifact a Earliest start date + supported (be carefull if the fixed date is before the timer is activated)
b Latest start date +/- can be realized using deferred choice (be carefull if the fixed date is before the timer is activated)
c Earliest completion date - not supported
d Latest completion date + Non-Interupting Intermediate-Timer-Event attached to an Activity or Sub-process
TP5 Schedule Restricted Element - not supported
C Patterns can be applied to different process elements a Single activity - Can be realized using a very complex construction with several signaling and timer events inside a sub-process. But this is to complex to be considered as supported.
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 - not supported
c Process model - not supported
F Patterns can restrict three dates of a process artifact a Earliest start date - not supported
b Latest start date - might be possible using a deferred choice with a intermediate timer event. But depends on the implementation of timer events (do they fire if the respective time has already passed?)
c Earliest completion date - not suported
d Latest completion date - might be possible by attaching a timer event to the activity (see b, for details)
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 + Event based XOR
b Time lags between activities / events +/- partially possible using Event based XOR
TP9 Cyclic Elements D[a*], E[c*], K[a], L[a] +/- partially supported (with limits)
D There are three kinds of restrictions a Minimum value +/- Timer on the Sequence Flow connecting the iterations. This limits the minimum time lag between the iterations but not between the activities inside the iterations.
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, not really a realation between activities but between iterations
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 -
 
Monday, 27 May 2013 14:55

Intalio 6.0.3

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] +/- 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 + supported
b System-defined - not supported
c User-defined - not supported
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 wait and fault handlers
C Patterns can be applied to different process elements a Single activity +/- supported by wrapping activity in a sub-process and adding a wait and fault handler parallel to the activity
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 +
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 - 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 -
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*] +/- mainly 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 -
Monday, 27 May 2013 14:54

AristaFlow 1.0.1

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] +/- mostly supported
A Parameters of a pattern may be set at a build-time + supported
b instantiation time - not supported
c run-time + supported
B Time parameters can be specified in different time
granularities
a Basic + supported
b System-defined + supported
c User-defined - not supported
TP1 Time Lags between two Activities D[b], E[c*,d*] +/- partially supported (with limits)
D There are three kinds of restrictions a Minimum value - not supported
b Maximum value + supported
c Time interval - not supported
E Time lags can be realized based on four different time relations a Start-Start - not supported
b Start-End - not supported
c End-Start +/- only directly preceeding activity (i.e., activation of the second activity)
d End-End +/- only directly preceeding activity (i.e., activation of the second activity)
TP2 Durations C[a], D[b] +/- partially supported
C Patterns can be applied to different process elements a Single activity + supported
b Activity set - not supported
c Process model - not supported
d Set of process instances - not supported
D There are three kinds of restrictions a Minimum value - not supported
b Maximum value + supported
c Time interval - not supported
TP3 Time Lags between Arbitrary Events - No event concept
D There are three kinds of restrictions a Minimum value -
b Maximum value -
c Time interval -
TP4 Fixed Date Elements C[a], F[b*,d] +/- partially supported
C Patterns can be applied to different process elements a Single activity + supported
c Process model - not supported
F Patterns can restrict three dates of a process artifact a Earliest start date - may be possible using resubmission. But currently not implemented
b Latest start date +/- possible using escalation and delegation
c Earliest completion date - not supported
d Latest completion date + supported
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] +/- 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 + supported through now()-Function in XOR
b Time lags between activities / events - not supported
TP9 Cyclic Elements D[b], E[c*,d*], K[a], L[a,b] +/- partially supported
D There are three kinds of restrictions a Minimum value - not supported
b Maximum value + possible using escalation/due date from data element written during last iteration
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 +/- partially supported (an automatic step is required directly after the first activity)
d End-End +/- partially supported (an automatic step is required directly after the first activity)
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 -
Monday, 27 May 2013 14:53

WebSphere Lombardi Edition 7.1

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,c*] +/- partially supported
A Parameters of a pattern may be set at a build-time + supported
b instantiation time - not evaluated before run-time
c run-time + supported
B Time parameters can be specified in different time
granularities
a Basic + supported
b System-defined - not supported
c User-defined +/- using java script
TP1 Time Lags between two Activities D[a,b*,c*], E[a*,b*,c,d*] +/- work-arounds are needed, not all combinations are supported
D There are three kinds of restrictions a Minimum value + supported by using a timer
b Maximum value +/- not all combination with Design Choice E are supported
c Time interval +/- possible using a and b
E Time lags can be realized based on four different time relations a Start-Start +/- possible to implement using pre-assignments and a timer event
b Start-End +/- possible to implement using pre-assignments and due date
c End-Start + supported
d End-End +/- possible to implement using post-assignments and due date
TP2 Durations C[a,c], D[b] +/- partially supported
C Patterns can be applied to different process elements a Single activity + supported (due date for activity)
b Activity set - not supported
c Process model + supported (due date for process)
d Set of process instances - not supported
D There are three kinds of restrictions a Minimum value - not supported
b Maximum value + supported by setting due date
c Time interval - not supported
TP3 Time Lags between Arbitrary Events D[a*] +/- partially supported
D There are three kinds of restrictions a Minimum value +/- Intermediate Timer Event between two Message Events
b Maximum value - not supported
c Time interval - not supported
TP4 Fixed Date Elements C[a,c*], F[a*,d] +/- partially supported
C Patterns can be applied to different process elements a Single activity + supported
c Process model +/- partially supported
F Patterns can restrict three dates of a process artifact a Earliest start date +/- supported only for activites
b Latest start date - not supported
c Earliest completion date - not supported
d Latest completion date + supported
TP5 Schedule Restricted Element C[a*,c*], F[a,b] +/- time table is only used for due date calculation and simulation
C Patterns can be applied to different process elements a Single activity +/- set a time schedule for the activity
c Process model +/- set a time schedule for the process
F Patterns can restrict three dates of a process artifact a Earliest start date + supported
b Latest start date + supported
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] +/- 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 + supported using expressions in an xor
b Time lags between activities / events - not supported
TP9 Cyclic Elements D[a*], E[c*], K[a], L[a,b] +/- partially supported (with limits)
D There are three kinds of restrictions a Minimum value +/- Timer on the Sequence Flow connecting the iterations. This limits the minimum time lag between the iterations but not between the activities inside the iterations.
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, not realy a relation between activities but between iterations
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 -

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] +/- partially supported
A Parameters of a pattern may be set at a At build-time + supported
b At instantiation time - not supported
c At run-time + supported
B Time parameters can be specified in different time
granularities
a Basic + Days, Hours, Minutes, Seconds, Milliseconds
b System-defined - not supported
c User-defined - not supported
TP1 Time Lags between two Activities D[a,b,c], E[c,d*] +/- partially supported; directly succeeding activities only
D There are three kinds of restrictions a Minimum value + wait
b Maximum value + supported
c Time interval + using a and 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 +/- Maximum Time between a task becoming ready and end of the task (human tasks only)
TP2 Durations C[a,c], D[b] +/- partially supported
C Patterns can be applied to different process elements a Single activity + supported
b Activity set - not supported
c Process model + supported
d Set of process instances - not supported
D There are three kinds of restrictions a Minimum value - not supported
b Maximum value + Maximum Distance between claiming human task and its end
Duration of a tasks can be specified 
c Time interval - not supported
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,b*,d*] +/- partially 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 + supported by using a wait previous to the activity
b Latest start date +/- only if activity is already in state ready
c Earliest completion date -
d Latest completion date +/- only if activity is already in statet ready
TP5 Schedule Restricted Element - not supported
C Patterns can be applied to different process elements a Single activity - Could probably be simulated using a Time Table assigned to a resource assigned to the task. But this is only supported for simulation purposes
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 C[c], F[a] +/- partially supported
C Patterns can be applied to different process elements a Single activity - not supported
c Process model + supported
F Patterns can restrict three dates of a process artifact a Earliest start date + supported
b Latest start date - not supported
c Earliest completion date - not supported
d Latest completion date - not supported
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 + supported using a choice with date comparision
b Time lags between activities / events +/- Pick with Wait (deferred choice)
TP9 Cyclic Elements D[a*], E[a*,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 +/- possible by extracting the start date of the first activity from the event log
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 -
Page 1 of 2

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.