process-flexibility.com

Friday, 24 May 2013 17:19

Pattern TP10: Periodicity

Especially in the medical domain there are frequently recurring tasks to be executed according to a periodical specification (e.g., a treatment plan). Thereby, periodical implies some regularity, but does not necessarily mean equally distanced.

Also known as

Recurrence, Appointment Series

Problem

A particular set of activities shall be performed periodically (i.e., according to a particular periodicity rule). Thereby, periodically implies some regularity, but does not necessarily mean equally distanced.

Design Choices

C A schedule can be applied to different process granularities
b Activity set
M The Number of cycles is
a determined by a fixed / dynamic number of iterations,
b depends on end date,
c depends on exit condition

PeriodicitySolution

A variant of an Ad-hoc Sub-Process may be used in combination with an associated periodicity rule.Periodicity rules can be realized by combining patterns TP1-6, TP8 and TP9 which are applied when scheduling the activities of the respective Ad-hoc Sub-Process.

Context

The context requirements of the participating time patterns need to be fulfilled.

Examples

  • Starting with next Monday group meetings will take place every two weeks at 11:30 am (Design Choices C[a] M[c]).
  • Each day at 7 am the responsible assistant physician of the Gynecological Clinic is informing the assistant medical director about the patients (Design Choices C[a] M[c]).
  • Course ``Business Processes and Workflows'' takes place every Monday from 8:00 am to 11:00 am starting on Oct 6th and ending on Jan 26th. On Dec 8th, 22nd, 29th and on Jan 5th no lectures will take place (Design Choices C[a] M[b]).
  • An information letter is sent by the leasing company to each customer within the first two weeks of each year (Design Choice C[a] M[c]).

Related Patterns

Product Evaluation

We differentiate between supported, partially supported, not supported and not specified.
If an evaluation object provides support for the particular pattern the supported design choices are listed. If the pattern is only partially supported (e.g., by a work-around) this is indicated by the additional label "*" and if support is not specified this is indicated by the label "?". Missing support is labeled with "-".

Product/LanguageVersionScoreMotivation
Microsoft Outlook 2010 not supported
Sunbird 1.0 not supported
Google Calendar 12.2011 not supported
Microsoft Project 2010 not supported
BPMN 2.0 not supported
IBM Websphere Integration Developer 6.1 not supported
WebSphere Lombardi Edition 7.1 not supported
AristaFlow 1.0.1 not supported
Intalio 6.0.3 not supported
TIBCO Business Studio 3.4.2 not supported
Bettini et al. loops are explicitly excluded from considerations
Combi et al. M[a,b,c] Periodic Constraint on loop Activity; no really complex periodicities
Eder et al. loops are explicitly excluded from considerations
Marjanovic et al. loops are explicitly excluded
Zhuge et al. not discussed
Read 4988 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.