process-flexibility.com

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
Read 21906 times
More in this category: « Bettini et al. Eder et al. »

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.