process-flexibility.com

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 -
Read 20190 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.