<!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>Human Behavior as a Process Model: Which Language to Use?⋆</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Gemma Di Federico</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andrea Burattin</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Marco Montali</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Free University of Bozen-Bolzano</institution>
          ,
          <addr-line>Bolzano</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Representing Human Behavior as a Process</institution>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Technical University of Denmark</institution>
          ,
          <addr-line>Kgs. Lyngby</addr-line>
          ,
          <country country="DK">Denmark</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Repetitive human behavior could be represented in the form of a process. Existing process modeling notations, however, are not able to handle all the features of these processes. We identify a set of key properties that a process modeling language needs to fulfill to capture human behavior. Let's define human behavior (HB) as a combination of intentions, thoughts, perceptions and states. The execution of a human behavior, and its purpose, is influenced by all of these factors. Human beings usually perform activities following some structures or patterns. Whenever we deal with the organization of activities in structures that are performed repetitively, we can leverage the notion of process [5]. This regularity, hence, can be exploited to study human behavior using Business Process Management techniques. The problem arises when trying to model a human-related process with current process modeling languages: unlike a business process, human behavior is more dynamic and less structured. The behavior is not fixed, but its execution varies and adapts over time, based on feedback, preferences and other contextual factors [1]. The importance of modeling human behavior is recognized in many diferent ifelds, including the healthcare sector [9]. Let's consider, as an example, elderly people afected with Dementia: they tend to have a very repetitive behavior. Changes in such a behavior could represent a symptom of the worsening of their disease [8]. Therefore a model representing their daily practices, in combination with data referring to the activities being performed, could be used to identify deviations in behavior. The ability to automatically capture, process and analyze human behaviors represents a valuable opportunity to monitor human-related processes. How the human beings behave can be observed from the viewpoint of the daily routine, intending their behavior as the execution of activities. Routines consist of frequent behaviors, composed by actions, carried out in situations that are the cause of</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Modeling of human behavior
(as a sequence of routine)</p>
      <p>1
Modeling of an individual routine
(as a sequence of activities)</p>
      <p>Modeling of activities
(as a sequence of observable units)
 2</p>
      <p>A
 3
 1
 4
 1</p>
      <p>2
B</p>
      <p>D</p>
      <p>C</p>
      <p>
        SCDITUAOJECDTOUIAJOWEFWEFWEFTWTYSDTYJI
those actions. People develop, acquire and adapt their routines through repeated
practice [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. However, human behavior is flexible and governed by uncertainty,
even if we are able to identify the general underlying process [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>The first step towards the analysis of human behavior is to represent an
unstructured process in form of a model. Once we have identified the process
modeling language that is able to faithfully represent the process, it will be
possible to automatically derive and analyse these type of processes. The problem
we want to highlight in this paper consists of devising the right process modeling
language. In Sec. 2 we investigate what characterizes human behavior and we
identify the requirements that a process modeling language must fulfill. In Sec. 3
we analyze the requirements with respect to the main features of the existing
languages.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Peculiarities of Human Behavior</title>
      <p>A process describing human behavior difers from a business process in many
respects. In this section we depict the main characteristics of activities performed
by human beings, deriving a specific characterization of their behavior.</p>
      <p>
        While human behavior is a mixture of intentions, perception, states [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ];
routines are intermediate structures of aggregated tangible actions that human
behavior results into (i.e., the actual sequence of activities carried out during a
day). In our investigation, we will focus our attention on routines as a proxy to
human behavior. HB may be interpreted as a sequence of routines. A routine
is composed of a series of activities which, at a lower level of abstraction, are
sequences of observable units. As highlighted in Fig. 1, the structure of HB
is hierarchical. In fact, a routine could be composed of other routines, and an
activity could be composed of other activities.
      </p>
      <p>
        Human beings establish routines and performs them repetitively [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. But
routines are not fixed, instead they vary over the time and they heavily depend on
the contingent situations, as an outgrowth of the uncertainty of human
behavior [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. This evolution is caused by the assumption that human beings usually
do not fit into the same routine, so the set of behaviors part of a routine varies.
Variations can be an alternative way to accomplish a task or the introduction
of a new behavior. For example, the breakfast routine changes often, according
to the seasons and our preferences. As a consequence, there may be multiple
variations that describe the same routine. To detect variability in behaviors, we
need to identify what is the reference behavior, so what the invariants are (that
is the goal) [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. In the example above, we need to identify what is the objective
and which are the variations.
      </p>
      <p>
        When modeling human processes, psychological and external factors should
also be taken into account, as they result in a close dependence between behavior
and context. The behavior is completely guided by the participant, who decides
how and when to perform certain actions [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], but it is also case-dependent because
the activities are combined based on specific circumstances (or context) [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. As
a consequence, based on these variables, human beings choose how and which
routine put in place.
      </p>
      <p>A routine is composed by set of activities. Although it is possible to predict
the set of activities that make up a behavior, we cannot define with certainty
their order of execution. Since human beings do not always act in the same way,
even a behavior is not performed following a rigid sequence of activities, resulting
in the variability of behaviors. E.g., the working routine is made up of several
activities, and part of them do not have a rigid and specicfi execution order.</p>
      <p>Additionally, human beings usually repeat certain activities several times
throughout the day and, whenever a behavior is executed, it may be part of
a diferent circumstance. For example the behavior of “preparing a meal” is
executed several times during the day, but the meaning varies according to the
circumstances. In fact, it can be (a) the preparation of a pasta dish (i) for lunch
or (b) the preparation of a meat dish (ii) for dinner. At a high level of abstraction
they all refer to the behavior of preparing a meal but, when observed within a
process, they have diferent meanings.</p>
      <p>Human beings can also perform multiple actions at the same time:
concurrency typically takes the form of mixing activities in a period of time. E.g., you
can talk on the phone while walking or watch a movie while eating supper.</p>
      <p>Uncertainty, evolution, dependencies, variability, repetition and concurrency
are all aspects that the process model should be able to represent. A process
model that is not capable of capturing all these components is deemed not to
have enough representative power to capture human behavior. As a consequence,
we would not be able to identify patterns and relations in a routine.</p>
      <p>Starting from the description presented above, we have devised a list of
characteristics that a process modeling language needs to possess.</p>
      <p>A. HB can be formalized as a set of sequences of observable units (that are
activities), with corresponding likelihoods, which are afected by the context.
B. HB is intrinsically hierarchical. As depicted in Fig. 1, HB could be seen as a
set of routines, that are in turn hierarchically structured. I.e., sequences of
HB are grouped into routines; a routine is composed by set of activities (or
other routines). For example, the daily routine includes the morning and the
working routine. Each of them is, in turn, made up of a set of behaviors.
C. HB can be instantiated, giving value to all the measures of a context:
executions of a behavior are bound to other contextual parameters. E.g., the
“sleeping” activity could be a nap or the deep night sleep, depending on
time and place. According to these parameters, the behavior is part of one
routine rather than another.</p>
      <p>D. Diferent instances of the same behavior could be observed in a sequence.</p>
      <p>E.g., the “preparing a meal” activity is performed several times during a
day, thus it is repeatedly observed during the daily routine sequence. Each
instance could belong to distinct routines, implying diferent other behaviors.
E. Instances of diferent HB could be observed over the same time period.
Human beings could perform activities simultaneously or intertwine the
execution of diferent behaviors with each other. E.g., watch television while
ironing.</p>
      <p>F. Diferent instances of the same HB could result in diferent sequences of
observable units (within the same set). The sequence of activities that compose
a behavior do not necessarily have a rigid execution order. E.g., the behavior
of “doing the laundry” is made up of various activities which do not have a
precise order: put in clothes/ the detergent/ the softener/ the color catcher.
G. As mentioned above, HB comprises sequences of observable units and their
likelihood. These could change over time based on the context.</p>
      <p>H. The context where HB happens can be formalized as a set of measures
(direct or computed value, internal or external to the process instance) that
characterize an instance. E.g., if it is snowy, it is more likely that a person
goes often to the window. According to this weather condition, the behaviour
is afected.</p>
      <p>I. HB does not have a fixed start and a fixed end. It is not always possible to
define exactly the initial and final actions of a given behavior.This is mainly
the case when there is a process that is characterized by a high variability,
such as the activity of preparing a meal. In this case the process can be
initiated from diferent points, in fact there is no specific action that defines
the beginning, or the end of it.</p>
      <p>
        There are also two additional, and more specific, requirements. Firstly, the model
must have an unambiguous semantic in order to allow establishing direct links
between the observed execution of the model and the observed execution of
activities (e.g., to calculate the conformity [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] w.r.t. activities). Secondly, the model
must be understandable and should clearly express its structure and relations,
in order to allow to know how the process is carried out.
      </p>
      <p>In the following section, we will identify the main properties of the existing
process modeling languages, and we will associate each of them to our list of
requirements for modeling HB. By doing so, we are able to identify which class
of modeling languages best reflects our needs.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Process Modeling Language Requirements</title>
      <p>
        Starting from the characterization presented in the previous section, we have
identified the requirements that a process modeling language needs to fulfill in
order to prove itself as a suitable candidate to model human behavior. A process
model representing human behavior must reflect the dynamic nature of these
behaviors, the flexibility and variations, such as the evolution. There are plenty
of process modeling languages, and we need to identify the one that is able to
express the aspects listed above to the largest extent. In the remainder of the
section we list the requirements expected by process modeling languages:
– The language must be able to handle true concurrency : human beings can
perform multiple activities at the same time.
– The language must support hierarchies as HB is also hierarchical.
– The language must represent at least the basic control flow patterns [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] to
properly capture the activities in HB.
– The language must allow for the definition of data flow conditions , as well as
include the provisioning of external data: HB is influenced by the context,
which can be a direct or computed value, internal or external to the process.
      </p>
      <p>Therefore the model must handle this data.
– The language must allow a certain level of flexibility in the execution flow,
as HB is not strictly enforced. Moreover, a stochastic language is preferred,
in order to support the evolution and the variation of the process.
– The language should be both a continuous or a discrete system. HB is subject
to change and, as such, the set of sequences of observable units could change
too, both in terms of structure (the sequence itself) and likelihood, at specific
points in time or continuously.
– The language must be able to represent processes that are not end-to-end.</p>
      <p>A set of sequences, part of a behavior, does not have a clear start and end
activities.
– The language must have a formal operational semantic to describe how the
process is interpreted, since the objective is to understand in detail the
meaning of the process.
– In addition to the previous point, the language must represent white box
models to explain the behaviors of a routine and to identify the variables
that influence the behavior.</p>
      <p>This list of process modeling languages properties could be used to select the
language that best reflects the requirements of a human behavior process 3.
4</p>
    </sec>
    <sec id="sec-4">
      <title>Future Work to Tackle the Problem</title>
      <p>When considering the requirements that a modeling language must support, in
order to model HB, a very important aspect to consider is the context. In fact
the model adapts itself according to specific conditions detected at that moment.
The process modeling language, therefore, should include conditions on data as
well as the provisioning of external data. Moreover, HB can be interpreted as
a sequence of routines that can be nested. In fact, a routine is composed by a
sequence of activities, that in turn could be other routines. That is, the
behavior is hierarchical. On the contrary, starting from low-level activities (namely
3 An initial comparison of the languages is reported in https://doi.org/10.11583/</p>
      <p>DTU.14745693.
observable units), as the level of abstraction increases, the concept of behavior
emerges in a broader sense. Hence, the model must represent behaviors in a
hierarchical way. The set of activities that compose a behavior could change over
the time, therefore the model must handle variations and respond to evolution:
the process model changes over the time. Another tricky aspect is the
stochasticity of HB. Two considerations must be made: the model cannot limit human
behavior, and the model cannot allow for all the behaviors. It is not possible
to predict the exact behaviors, as they are guided by a certain degree of
flexibility and uncertainty. Consequently, we cannot limit the model by defining a
rigid sequence of activities, but we cannot even admit the execution of all the
behaviors, as the concept of process would be lost. However, we can assert that
all behaviors can be performed, but some are more likely than others. This also
supports the evolution of behaviors described above, letting the possibility to
admit behaviors during the execution of the process. The limit, however, is that
the possibility of representing all possible behaviors would increase the dificulty
of identifying the real process, excluding anomalies and outliers. The stochastic
aspect is also questioned by the concurrency and the fuzziness of human
behavior. In fact, several activities could be performed simultaneously but we are
unable to completely include or exclude one of them, or distribute the
probability of execution among them, but it can be considered as a fuzzy behavior. One
ifnal note concerns the fact that that the process is not end to end. Therefore,
it does not have a well-defined start and end, but can be instantiated from any
point. The language must be able to handle this cyclic nature of the process.</p>
      <p>Given the identified list of requisites, it is now necessary to proceed towards
a thorough evaluation of the process modeling languages. One of the existing
language, or the combination of several of them, may be the most appropriate
way to represent processes related to human behavior.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Banovic</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Buzali</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chevalier</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mankof</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dey</surname>
            ,
            <given-names>A.K.</given-names>
          </string-name>
          :
          <article-title>Modeling and understanding human routine behavior</article-title>
          .
          <source>In: Proc. of CHI</source>
          . pp.
          <fpage>248</fpage>
          -
          <lpage>260</lpage>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Carmona</surname>
            , J., van Dongen,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Solti</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weidlich</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          : Conformance checking:
          <source>Relating Processes and Model</source>
          . Springer (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. da Cunha Mattos,
          <string-name>
            <given-names>T.</given-names>
            ,
            <surname>Santoro</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            ,
            <surname>Revoredo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Nunes</surname>
          </string-name>
          , V.T.:
          <article-title>A formal representation for context-aware business processes</article-title>
          .
          <source>Comput. Ind</source>
          .
          <volume>65</volume>
          (
          <issue>8</issue>
          ) (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>Di</given-names>
            <surname>Ciccio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            ,
            <surname>Marrella</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Russo</surname>
          </string-name>
          ,
          <string-name>
            <surname>A.</surname>
          </string-name>
          :
          <article-title>Knowledge-intensive processes: characteristics, requirements and analysis of contemporary approaches</article-title>
          .
          <source>J. Data Semant</source>
          .
          <volume>4</volume>
          (
          <issue>1</issue>
          ) (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Dumas</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>La</given-names>
            <surname>Rosa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Mendling</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Reijers</surname>
          </string-name>
          ,
          <string-name>
            <surname>H.A.</surname>
          </string-name>
          :
          <article-title>Fundamentals of business process management</article-title>
          . Springer (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Feldman</surname>
            ,
            <given-names>M.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pentland</surname>
            ,
            <given-names>B.T.</given-names>
          </string-name>
          :
          <article-title>Reconceptualizing organizational routines as a source of flexibility and change</article-title>
          .
          <source>Adm. Sci. Q</source>
          .
          <volume>48</volume>
          (
          <issue>1</issue>
          ),
          <fpage>94</fpage>
          -
          <lpage>118</lpage>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Guizzardi</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reis</surname>
            ,
            <given-names>A.N.N.:</given-names>
          </string-name>
          <article-title>A method to align goals and business processes</article-title>
          .
          <source>In: International Conference on Conceptual Modeling</source>
          . pp.
          <fpage>79</fpage>
          -
          <lpage>93</lpage>
          . Springer (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Kales</surname>
            ,
            <given-names>H.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gitlin</surname>
            ,
            <given-names>L.N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lyketsos</surname>
            ,
            <given-names>C.G.</given-names>
          </string-name>
          :
          <article-title>Assessment and management of behavioral and psychological symptoms of dementia</article-title>
          .
          <source>BMJ</source>
          <volume>350</volume>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Lull</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bayo</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shirali</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghassemian</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fernandez-L.</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Interactive Process Mining in IoT and Human Behaviour Modelling</article-title>
          , pp.
          <fpage>217</fpage>
          -
          <lpage>231</lpage>
          . Springer (
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Sanchez-Calzon</surname>
            ,
            <given-names>A.B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fernandez-L.</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pileggi</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Meneu</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Impact of semantic technologies to human behavior modeling: A psychosocial rationalization</article-title>
          .
          <source>In: Proc. of ICAART</source>
          . pp.
          <fpage>547</fpage>
          -
          <lpage>552</lpage>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Stefanini</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aloini</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Benevento</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dulmin</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mininno</surname>
          </string-name>
          , V.:
          <article-title>A process mining methodology for modeling unstructured processes</article-title>
          .
          <source>Knowl. Process. Manag</source>
          .
          <volume>27</volume>
          (
          <issue>4</issue>
          ),
          <fpage>294</fpage>
          -
          <lpage>310</lpage>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Van der Aalst</surname>
            ,
            <given-names>W.M.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>Ter</given-names>
            <surname>Hofstede</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.H.</given-names>
            ,
            <surname>Kiepuszewski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            ,
            <surname>Barros</surname>
          </string-name>
          ,
          <string-name>
            <surname>A.P.</surname>
          </string-name>
          :
          <article-title>Workflow patterns</article-title>
          .
          <source>Distrib. Parallel Databases</source>
          <volume>14</volume>
          (
          <issue>1</issue>
          ),
          <fpage>5</fpage>
          -
          <lpage>51</lpage>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>