process-flexibility.com

Monday, 27 May 2013 14:44

Microsoft Project 2010

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,c] + supported
A Parameters of a pattern may be set at a build-time + supported
b instantiation time - build-time and instantiation time are more or less the same
c run-time + supported
B Time parameters can be specified in different time
granularities
a Basic + Minute, Hour, Day, Week, Month and Year
b System-defined + Working Days
c User-defined + Calendars can be defined for Resources
TP1 Time Lags between two Activities D[a,b], E[a,b,c,d] +/- partially supported
D There are three kinds of restrictions a Minimum value + supported
b Maximum value + supported
c Time interval - only either minimum or maximum
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[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 + supported
c Time interval - not supported
TP3 Time Lags between Arbitrary Events - not supported
D There are three kinds of restrictions a Minimum value - no support of events
b Maximum value -
c Time interval -
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 + Execution date of the first/last activity
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
TP5 Schedule Restricted Element C[a], F[a*,b*] +/- partially supported
C Patterns can be applied to different process elements a Single activity + Creating a special calendar for a resource
c Process model - not supported
F Patterns can restrict three dates of a process artifact a Earliest start date +/- does not prevent the activity from being startet, just suspends it
b Latest start date +/- does not prevent the activity from being startet, just suspends it
c Earliest completion date - not supported
d Latest completion date - not supported
TP6 Time Based Restrictions G[a], H[b], I[a*] +/- partially supported
G Time Based Restrictions can be applied to different types of process artifacts a activities within same process instance + supported
b activities within different process instances - not supported
c Instances of a process or group of processes - not supported
H There are two kinds of restrictions a Minimum number of executions - not supported
b Maximum number of executions + supported
I There are two types of restrictions which can be expressed by Time Based Restrictions a Number of concurrent executions +/- Automatic coordination of activities which share a common resource
b Number of executions per time period - not supported
TP7 Validity Period - not supported
C Patterns can be applied to different process elements a Single activity - no application service / process schema concept
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 - 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 - no variability
b Time lags between activities / events -
TP9 Cyclic Elements D[a*], E[a*,c*], K[a], L[a] +/- partially supported
D There are three kinds of restrictions a Minimum value +/- using a recurring task, this is not really a minimum distance between to activities but between two iterations
b Maximum value -
c Time interval -
Time Lags can be realized based on four different time relations a Start-Start +/- this is not really a relation between two activites but between two iterations (the distance is fixed from start-start but delayed by the end of the last iteration)
b Start-End -
c End-Start +/- see a
d End-End -
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 - 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 21055 times
More in this category: « Google Calendar 12.2011 BPMN 2.0 »

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.