IBM Websphere Integration Developer 6.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] +/- 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 -