process-flexibility.com

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