<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Research Challenges on Person-centric Flows</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Tobias Unger</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Hanna Eberle</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Frank Leymann</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Institute of Architecture of Application Systems University of Stuttgart, Universitatsstra e 38</institution>
          ,
          <addr-line>70569 Stuttgart</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Research in the domain of Work ow Management focuses increasingly on service orchestrations. Often the fact is neglected that a huge part of the activities of business processes are performed by people. Especially, in the domain of pervasive computing processes are describing sequences of real world activities which are invariably performed by people. Therefore we consider the role of people participating in work ows from a new perspective. The basic idea of this work is to transfer the work ow metaphor to people processing their tasks. Therefore, we introduce the concept of a person-centric ow, which denotes such an implicit ow scheduled and executed by a single person. Secondly, we provide a list on research challenges on person-centric ows.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Most research in business process management focuses on the aspects of service
orchestration. The fact, that in certain types of businesses a business process
consists of many manual activities, has not been recognized as a major research
item, yet. Manual activities are carried out by people. We call those activities in
the following tasks to di erentiate them from the other types of activities, such
as an invoke activity that requests the execution of a Web Service. For example,
pervasive computing processes are typically describing sequences of activities
which are performed by people. People are involved in many business processes
at the same time, which requires appropriate support from the underlying IT
infrastructure to help organize the work they need to carry out. Among many
other functions such a infrastructure requires capabilities for work prioritization,
context-sensitive assistance, or the capability of structuring a task by dividing
the task into smaller tasks and ordering them as required by the user. Several
speci cations such as [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] and WS-Humantask [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] have been developed to address
the integration of people into the world of services. We claim that those speci
cations only partially provide the required support and that additional capabilities
must be provided by work ow management system to better integrate people in
the execution of business processes.
      </p>
      <p>This work is partially funded by the ALLOW project. ALLOW
(http://www.allow-project.eu/) is part of the EU 7th Framework Programme
(contract no. FP7-213339).</p>
      <p>
        Since the cognitive capabilities of people do not allow to carry out many
tasks in parallel, people order the di erent tasks in a way that is convenient
for them to process the di erent tasks. Current state of the art in work ow
management typically provide the notion of work lists (cf. [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]), which the user
can sort in any desired way using the properties that are associated with each
task. Incidentally [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] shows that the e ciency of users highly depends on the
capability for individual ordering of the work list. A disadvantage of larger work
lists is the increased probability of missing the schedule for a task.
      </p>
      <p>
        Studies have shown that people not only use the basic ordering of the work
lists to select the next set of tasks, but also use some correlations or similar
context information between the di erent tasks to select them [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. This is similar
to traditional work ow paradigm where the execution of the di erent activities
is driven through the context that is associated with a process instance. We
propose in this paper to order the individual tasks via process templates that
are dynamically generated from the available tasks via the user preferences and
automatically instantiated.
      </p>
      <p>
        We introduce the concept of a person-centric ow, which denotes such an
implicit ow scheduled and executed by a single person. Basically, a
personcentric ow consists of the tasks on a person's worklist extended by additional
ordering information. However, the knowledge about the existence of such a
implicit person-centric ow cannot be utilized. Thus, making the person-centric
ow explicitly visible and observable opens great opportunities to support people
in doing their work. For example recommendations on the task ordering can
be made which helps people e.g. to save resources or time. The goal of this
work is to list research challenges on person-centric ows, their modeling, and
execution. The aim of person-centric ows is not to prescribe people an ordering
for performing their tasks. In fact, we want to support people e.g. by calling
their attention to possible errors or to the fact, that the chosen ordering is
prohibited. Another advantage of person-centric ows is the possibility to adapt
the environment to needs of a future task. This is particularly useful in the case
of actions that need time consuming preparation (cf. [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]) For example the lling
of the bathtub can be started in time, as soon as it is known when a nurse will
start washing a patient. For simpli cation reasons this work assumes that all
tasks are generated by a Work ow Management System (WfMS).
      </p>
      <p>The outline of this paper is as follows: Section 2 presents a scenario which is
used to explain some issues of person-centric ows. A brief de nition of
personcentric ows is presented in Section 3. Section 4 lists the research challenges
concerning person-centric ows and related approaches. Finally, Section 5
concludes the paper.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Scenario</title>
      <p>
        Our scenario is situated in the domain of Healthcare (cf. [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]). Figure 1 shows
simpli ed versions of the work ows executed each morning for each patient.
All steps of the two work ows have to be done by a nurse and all steps of the
medication ow has to be done by the same nurse. Imagine there are two patients
Frank and Tobias situated in two di erent rooms and one nurse Hanna. Imagine
the situation where Hanna has executed the prepare medicine and fetch medicine
task for both patients. As a consequence, Hanna has four tasks to perform which
all appear on her worklist. Her person-centric ow could be rst to medicate and
wash Frank and afterwards to medicate and wash Tobias. In another situation
she may decide to medicate both patients before washing them. This can be
considered as an adaptation of her ow.
      </p>
      <p>Patient 
Medication </p>
      <p>Flow</p>
      <p>Prepare</p>
      <p>Fetch</p>
      <p>Administer</p>
      <p>Patient 
Washing </p>
      <p>Flow</p>
      <p>Wash</p>
      <p>The scenario shows that a person-centric ow does not just follow a static ow
model. It is highly dynamic due to context and changes of the worklist. Hanna
implicitly forms her ow according to her actual situation. Her ow is not visible
to the outside completely. Only the history of the ow is visible. Secondly, while
executing a prepare task of an instance of the medication ow, by experience
she schedules a fetch and a medication task even if these task are actually not
on her worklist yet. By experience she knows that the a fetch medicine task is
followed by a medication task. Hence, she considers the medication task right at
the moment of scheduling her tasks, although only the fetch medication task is
active.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Person-centric Flows</title>
      <p>The aim of this section is to provide a rst informal de nition of the term and
concept of person-centric ows. Later on the de nition serves as foundation in
order to identify research challenges. As mentioned before all tasks arise from
ow instances executed by a WfMS which also provides a person's worklist. In
the second part of this section we present the types of person-centric ows we
identi ed during our research.
3.1</p>
      <p>De nition
De nition 1 (Person-centric ow). A person-centric ow de nes a partial
ordering over a set of tasks which have to be performed by one single person.
Tasks of a person-centric ow can be classi ed in three tenses: past tasks, present
tasks, and future tasks. Past tasks are completed either correct or incorrect and
their ordering is known. Present tasks are tasks currently present at a person's
worklist. Their ordering is planned by the person but can change dynamically.
Future tasks are tasks which are assumed to be executed in the future. Both the
set of future task as well as their ordering may change dynamically.</p>
      <sec id="sec-3-1">
        <title>Present</title>
      </sec>
      <sec id="sec-3-2">
        <title>Future</title>
        <p>During our research we recognized the following classes of person-centric ows:</p>
        <p>Predicted ow: This is a predicted ow which corresponds to a person's ow
with a high probability. Such ows are used for example to adapt the environment
of a person. If washing a patient is supposed to be a nurse's next task the light
in the shower could be switched on automatically. Regarding our scenario the
knowledge of the nurse's ow helps to decide which patient will be washed rst
and consequently in which shower the light has to be switched on.</p>
        <p>Guidance ow: A guidance ow is based on a predicted ow. However, a
guidance ow may be extended by external ordering constraints. The aim of
a guidance ow is to guide people actively through their ow. For example a
constraint demands that a nurse must disinfect her hands between washing two
patients. If she decides to perform both washing tasks without disinfecting her
hands between, the constraint will be violated and the system will inform her.
1 The gure uses an illustration by Patrick J. Lynch, medical illustrator and C. Carl
Ja e, MD, cardiologist.</p>
        <p>Enforcement ow: An enforcement ow orders the tasks of a patient only
based on external constraints. In this case the person-centric ow of a person is
given by the environment. For example the fact that the medication must take
place before washing can be enforced by an enforcement ow and the system can
drive the person accordingly. A major disadvantage of this kind of person-centric
ow is that it deprives people of the freedom to decide in which order they want
to perform their tasks.</p>
        <p>However, there is no clear distinction between the three classes of
personcentric ows. A ow can comprise enforced as well as predicted as well as guided
parts. Mostly, only a meaningful scenario-based combination of the three classes
facilitates to reduce the cognitive load of a person necessary for scheduling task
while retaining a high degree of freedom in scheduling tasks. Sometimes the
characteristic of a person-centric ow may change over time. While a
unexperienced nurse should be guided, with increasing experience the guidance should be
reduced. As of that time the person-centric ow is only used for adapting the
environment.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Research Challenges</title>
      <p>In this section we present the identi ed research challenges on person-centric
ows derived from the scenario analysis. The list is not exhaustive. Analyzing
other scenarios may identify further issues.</p>
      <p>
        Relation between implicit and explicit ow: As mentioned earlier a
person-centric ow is implicit created by a person. In order to utilize the
personcentric ow a explicit representation must be created. Like a hidden markov
chain the observable behavior of the explicit ow may di er from the hidden
implicit ow. Anyhow, the relation between these two ows must be described.
The relation may be de ned by describing the possible deviations of the predicted
person-centric ow compared to the person-centric ow a person has in mind.
Such an approach for modeling process variants is presented in [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Additionally,
the predicted ow can be annotated with a maximum likelihood of its occurrence.
      </p>
      <p>Rethinking the notion of ow model and instance: A person-centric
ow has no prede ned ow model. Since tasks emerge and disappear continuously,
the person-centric ow has to be adapted very often. Thus, a language has to
be de ned that can deal with such a high degree of exibility. Furthermore, the
notion of an instance must be rethought. An instance of a common ow model
has a de ned beginning and a de ned end. In contrast to traditional work ows a
person-centric ow has no de ned beginning and end. People are continuously
performing tasks. Although there might be gaps in the ow where no tasks are
performed.</p>
      <p>
        Imperative vs. declarative process modeling languages: Basically, two
types of work ow languages exist: imperative languages (cf. e.g. [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]) and
declarative languages (cf. e.g. [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]). While imperative languages are assumed to be
easier to understand, declarative languages promise a higher degree of exibility.
Furthermore, di erent orderings of the same set of tasks are hard to model
using imperative languages. In this work we use [
        <xref ref-type="bibr" rid="ref10 ref9">9, 10</xref>
        ] as starting points for our
discussion on declarative and imperative work ow modeling languages, since the
authors aim to contribute to a rigorous, theoretical discussion of this topic. Since
high exibility is a requirements for person-centric ows we decided to use a
declarative language for the rst attemp to describe person-centric ows (cf. [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]).
The language is based upon the interval relations of Allen's interval algebra [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
In contrast to existing declarative languages (cf. [
        <xref ref-type="bibr" rid="ref13 ref14 ref8">8, 13, 14</xref>
        ]) we extended the
constraints of our language by time parameters to add support for temporal
restrictions. To validate the consistency of the relation constraints we follow an
approach similar to the one suggested in [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. Also case handling [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] provides
more exibility in executing work ows. In case handling the control- ow related
information does not drive the process but the state of the process, i.e. the
existence of data objects. Since our approach focuses on the tasks themselves and
not on the state of a data object, case-handling is inappropriate for modeling
person-centric ows.
      </p>
      <p>
        Algorithms for prediction: Since we are not able to capture the
personcentric ow a person has in mind, we need to nd algorithms to determine the
task orderings. Especially history based algorithms are promising since people
often have behavior patterns which can be detected by history-based algorithms.
But also algorithms operating e.g. on task deadlines without considering the
history (e.g. scheduling algorithms) seem to be useful in certain scenarios. There
are many approaches which can be used as a starting point. In [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] the authors
present an approach, which can be used for predicting a person's next steps
based on the ow history. The recommendation in this approach is made for a
single process instance and doesn't consider the interleaving of di erent process
instances. In [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ] scheduling algorithms are used to order worklists. Such an
approach is suitable, if the person-centric ow should be enforced. [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ] provides an
approach which can be used for mining behavior patterns of people. Algorithms
for predicting a person's next location are presented in [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ]. The latter two
approaches can be used, if there are recurring behavior patterns. However, they
have to be adapted in order to operate on work ow histories.
      </p>
      <p>
        Granularity of tasks: Tasks in business process are often modeled on a
higher level than they will be actually executed by the people. Hence, people
divide tasks in a set of subtasks. For example the washing of a patient is divided
in several sub-tasks by a nurse. Algorithms for predicting person-centric ows
also have to consider the fact that people re-structure their tasks. In [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ] a case
study is presented showing how people re-structure tasks.
      </p>
      <p>Parallelism of human actions: It has to be discussed whether it is
reasonable to allow parallelism in person-centric ows. Hence, granularity implies
that if task are divided in sub-tasks which might be executed interleaving with
subtasks of other tasks urge for parallelism capabilities.</p>
      <p>
        Visualization: If person-centric ows are made explicit they should also be
visualized in order to present them to a person, e.g. in the case that the personal
ow is a guidance ow. However, meaningful representations must be found. For
example, the person-centric ow of a nurse may be integrated within a map of
the hospital. Such a scenario may be realized based on an approach for workitem
visualization as presented in [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ]. In [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ] a work ow visualization framework is
presented, which enables a exible business-oriented process visualization (e.g.
using a gant chart). This approach can also serve as foundation for a visualization
discussion on person-centric ows.
      </p>
      <p>
        Privacy: Person-centric ows contain a lot information about the speci c
behavior of a person, which should be protected. Hence, discussing privacy is
an important issue. [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ] gives an overview on the e ects of combining work ow
systems and context-aware systems and to discuss its implications for workplace
privacy and human-oriented design.
5
      </p>
    </sec>
    <sec id="sec-5">
      <title>Conclusion</title>
      <p>
        In this paper we introduce the concept of person-centric ows. Since
personcentric ows are orthogonal to the existing work ow concept the two concepts
complement each other. The main goal of person-centric ows is to support a
person performing her tasks for example by reducing the cognitive load necessary
for scheduling their tasks. However, person-centric ows can also be used to enforce
external constraints. Initially, we will use the declarative work ow modeling
language proposed in [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] to representing person-centric ows. In future work,
we investigate and implement a prediction algorithm to predict person-centric
ows prototypically. The aim of the prototype is to guide unskilled nurses. The
prototype is also used to improve the accuracy of activity sensing and context
recognition. In that case the person-centric ow reduces the search space of the
activity recognition system since two activities having the same characteristics of
sensor data may be distinguished according to their position in the person-centric
ow.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. OASIS:
          <article-title>WS-BPEL Extension for People Speci cation Version 1</article-title>
          .1,
          <string-name>
            <surname>Committee</surname>
            <given-names>Draft</given-names>
          </string-name>
          06. (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <source>OASIS: Web Services Human Task Speci cation Version 1</source>
          .1,
          <string-name>
            <surname>Committee</surname>
            <given-names>Draft</given-names>
          </string-name>
          06. (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Leymann</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Roller</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Production Work ow { Concepts and</article-title>
          <string-name>
            <surname>Techniques. Prentice Hall PTR</surname>
          </string-name>
          (
          <year>2000</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Card</surname>
            ,
            <given-names>S.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Newell</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Moran</surname>
            ,
            <given-names>T.P.:</given-names>
          </string-name>
          <article-title>The Psychology of Human-Computer Interaction</article-title>
          . L. Erlbaum Associates Inc., Hillsdale, NJ, USA (
          <year>1983</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Nurmi</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Martin</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Flanagan</surname>
            ,
            <given-names>J.A.</given-names>
          </string-name>
          :
          <article-title>Enabling Proactiveness through Context Prediction</article-title>
          . In: In: CAPS 2005,
          <article-title>Workshop on Context Awareness for Proactive Systems</article-title>
          . (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <source>ALLOW: D3</source>
          .
          <article-title>1: Results of Scenario Analysis</article-title>
          .
          <article-title>(</article-title>
          <year>2009</year>
          )
          <article-title>Available online</article-title>
          (http://www. allow-project.eu/).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Hallerbach</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bauer</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>Issues in Modeling Process Variants with Provop</article-title>
          . In Ardagna, D.,
          <string-name>
            <surname>Mecella</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yang</surname>
          </string-name>
          , J., eds.:
          <source>Business Process Management Workshops. Volume 17 of Lecture Notes in Business Information Processing.</source>
          , Springer (
          <year>2008</year>
          )
          <volume>56</volume>
          {
          <fpage>67</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pesic</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schonenberg</surname>
          </string-name>
          , H.:
          <article-title>Declarative work ows: Balancing between Flexibility and Support</article-title>
          . Computer Science - R&amp;D
          <volume>23</volume>
          (
          <issue>2</issue>
          ) (
          <year>2009</year>
          )
          <volume>99</volume>
          {
          <fpage>113</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Fahland</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mendling</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reijers</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weber</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weidlich</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zugal</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Declarative vs</article-title>
          .
          <source>Imperative Process Modeling Languages: The Issue of Maintainability. In: 1st International Workshop on Empirical Research in Business Process Management (ER-BPM'09)</source>
          , Ulm, Germany (
          <year>September 2009</year>
          )
          <volume>65</volume>
          {
          <fpage>76</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Fahland</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          , Lubke,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Mendling</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Reijers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            ,
            <surname>Weber</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            ,
            <surname>Weidlich</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Zugal</surname>
          </string-name>
          ,
          <string-name>
            <surname>S.</surname>
          </string-name>
          :
          <article-title>Declarative versus Imperative Process Modeling Languages: The Issue of Understandability</article-title>
          .
          <source>In: Proceedings of the 14th International Conference on Exploring Modeling Methods in Systems Analysis and Design (EMMSAD'09)</source>
          , Amsterdam, The Netherlands, Springer-Verlag (
          <year>June 2009</year>
          )
          <volume>353</volume>
          {
          <fpage>366</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Wagner</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>A Concept of Human-oriented Work ows</article-title>
          .
          <source>Diploma thesis</source>
          , University of Stuttgart, Germany (
          <year>January 2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Allen</surname>
            ,
            <given-names>J.F.</given-names>
          </string-name>
          :
          <article-title>Maintaining Knowledge about Temporal Intervals</article-title>
          .
          <source>Commun. ACM</source>
          <volume>26</volume>
          (
          <issue>11</issue>
          ) (
          <year>1983</year>
          )
          <volume>832</volume>
          {
          <fpage>843</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Pesic</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>Constraint-Based Work ow Management Systems: Shifting Control to Users</article-title>
          .
          <source>PhD thesis</source>
          , Eindhoven University of Technology (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Pesic</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schonenberg</surname>
            ,
            <given-names>M.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sidorova</surname>
          </string-name>
          , N.,
          <string-name>
            <surname>van der Aalst</surname>
          </string-name>
          , W.M.P.:
          <article-title>ConstraintBased Work ow Models: Change Made Easy</article-title>
          .
          <source>In: OTM Conferences (1)</source>
          . (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Lu</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sadiq</surname>
            ,
            <given-names>S.W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Padmanabhan</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Governatori</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          :
          <article-title>Using a temporal constraint network for business process execution</article-title>
          .
          <source>In: ADC</source>
          . (
          <year>2006</year>
          )
          <volume>157</volume>
          {
          <fpage>166</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weske</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , Grunbauer, D.:
          <article-title>Case handling: a new paradigm for business process support</article-title>
          .
          <source>Data Knowl. Eng</source>
          .
          <volume>53</volume>
          (
          <issue>2</issue>
          ) (
          <year>2005</year>
          )
          <volume>129</volume>
          {
          <fpage>162</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Schonenberg</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weber</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>van Dongen</surname>
            ,
            <given-names>B.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          :
          <source>Supporting Flexible Processes through Recommendations Based on History. [25] 51{66</source>
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18. Han,
          <string-name>
            <surname>R</surname>
          </string-name>
          ., Liu,
          <string-name>
            <given-names>Y.</given-names>
            ,
            <surname>Wen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            ,
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <surname>J.:</surname>
          </string-name>
          <article-title>A Two-Stage Probabilistic Approach to Manage Personal Worklist in Work ow Management Systems</article-title>
          . In Meersman, R.,
          <string-name>
            <surname>Dillon</surname>
            ,
            <given-names>T.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Herrero</surname>
          </string-name>
          , P., eds.
          <source>: OTM Conferences (1)</source>
          . Volume
          <volume>5870</volume>
          of Lecture Notes in Computer Science., Springer (
          <year>2009</year>
          )
          <volume>24</volume>
          {
          <fpage>41</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Vrotsou</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ellegard</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cooper</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Everyday Life Discoveries: Mining and Visualizing Activity Patterns in Social Science Diary Data</article-title>
          . In: IV, IEEE Computer Society (
          <year>2007</year>
          )
          <volume>130</volume>
          {
          <fpage>138</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Petzold</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bagci</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Trumler</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ungerer</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Comparison of Di erent Methods for Next Location Prediction</article-title>
          . In Nagel, W.E.,
          <string-name>
            <surname>Walter</surname>
            ,
            <given-names>W.V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lehner</surname>
          </string-name>
          , W., eds.:
          <string-name>
            <surname>Euro-Par</surname>
          </string-name>
          . Volume
          <volume>4128</volume>
          of Lecture Notes in Computer Science., Springer (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Schroeder</surname>
          </string-name>
          , W.:
          <article-title>New Tools for Task Work ow Analysis</article-title>
          .
          <source>In: CHI EA '09: Proceedings of the 27th international conference extended abstracts on Human factors in computing systems</source>
          , New York, NY, USA, ACM (
          <year>2009</year>
          )
          <volume>3877</volume>
          {
          <fpage>3882</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22. de Leoni, M.,
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>ter Hofstede</surname>
            ,
            <given-names>A.H.M.</given-names>
          </string-name>
          :
          <article-title>Visual Support for Work Assignment in Process-Aware Information Systems</article-title>
          . [
          <volume>25</volume>
          ]
          <fpage>67</fpage>
          {
          <fpage>83</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Bobrik</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bauer</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>View-Based Process Visualization</article-title>
          . In Alonso, G.,
          <string-name>
            <surname>Dadam</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosemann</surname>
          </string-name>
          , M., eds.
          <source>: BPM</source>
          . Volume
          <volume>4714</volume>
          of Lecture Notes in Computer Science., Springer (
          <year>2007</year>
          )
          <volume>88</volume>
          {
          <fpage>95</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Wieland</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>L</surname>
          </string-name>
          angerer,
          <string-name>
            <given-names>C.</given-names>
            ,
            <surname>Leymann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            ,
            <surname>Siemoneit</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            ,
            <surname>Hubig</surname>
          </string-name>
          ,
          <string-name>
            <surname>C.</surname>
          </string-name>
          :
          <article-title>Methods for Conserving Privacy in Work ow Controlled Smart Environments - A Technical and Philosophical Enquiry into Human-Oriented System Design of Ubiquitous Work Environments</article-title>
          .
          <source>In: UBICOMM</source>
          <year>2009</year>
          , Sliema, Malta, IEEE (
          <year>October 2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Dumas</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shan</surname>
          </string-name>
          , M.C., eds.: Business Process Management, 6th International Conference, BPM 2008, Milan, Italy, September 2-
          <issue>4</issue>
          ,
          <year>2008</year>
          . Proceedings. In Dumas,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Reichert</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Shan</surname>
          </string-name>
          , M.C., eds.
          <source>: BPM</source>
          . Volume
          <volume>5240</volume>
          of Lecture Notes in Computer Science., Springer (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>