<!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>Can Working Style Be Identi ed?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Marcello Sarini</string-name>
          <email>marcello.sarini@unimib.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>University of Milano-Bicocca, Department of Psychology</institution>
          ,
          <addr-line>I-20126 Milan</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Working style is a concept not fully taken into account especially when the unfolding of a business process is supported by Processaware Information Systems. In this paper we present a practical approach to define and identify working style. The identification is done by searching for some patterns representing critical common features which define a working style. A prototype is presented as a proof of concepts for this new research path.</p>
      </abstract>
      <kwd-group>
        <kwd>Working style</kwd>
        <kwd>Organizational mining</kwd>
        <kwd>Graph databases</kwd>
        <kwd>Process-aware Information Systems</kwd>
        <kwd>Visualization</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>
        The concept of style has been widely discussed in different fields such as Arts,
Fashion, and Design. Research on style focused on two different complementary
perspectives, on the one hand on the artifacts which are characterized by a
certain style; on the other hand on the process of designing the artifacts [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. In this
last perspective, more related to the Design field, style is an organizing principle
emerging from a series of choices made within some set of constraints [
        <xref ref-type="bibr" rid="ref21 ref6">6, 21</xref>
        ]. In
our proposal we want to fill this gap by creating an artifact, the Working Style
Artifact (WSA), which reifies the way people work by making visible the
interdependencies among performers who completed their work related to a business
process. Even if little has been told about the concept of style associated to the
way people work, Working style considers the process of work as a set of choices
made by the involved performers within the set of constraints posed by the
workplace; and this is crucial especially when work is performed with the
support of Process-aware Information Systems as these systems tend to pose strong
constraints on the way work is arranged during the unfolding of the supported
business process.
      </p>
      <p>
        In this view, the concept of Working style, and especially its visible
counterpart, the Working Style Artifact, can be seen as a tool for facilitate comparisons
to identify similarities and differences about the nature of work; this could be
useful in different situations where it would be meaningful to make visible and
commonly acknowledged in a seamless way to the involved stakeholders
repetitions of work behaviors. This seems relevant for instance in different areas of
Job analysis where Job analysis is the process by which jobs are subdivided
into elements, such as tasks, through the application of a formalized, systematic
procedure for data collection, analysis and synthesis [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]: e.g., to promote
organizational compliance, i.e., to facilitate the comparison of real work performed
by an actor with the tasks expected to be completed according to her specific
position; to facilitate team formation, by choosing people who are similar in
working [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ]; to limit the possible raise of resistance to change, by facilitating
the comparison of work performed during the as-is process with the tasks
expected for the redesigned to-be process. All of these aspects will be crucial for
a well functioning organization, as organizational compliance is about the
capability of an organization of setting clear duties for a determined position; this
is the opposite of role ambiguity, where studies in organizational Psychology
emphasized that role ambiguity could negatively affect, among the others, job
satisfaction [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ]. It would be useful to keep into account that working style could
be associated to the concept of habits in work settings and changing habits could
be troublesome [
        <xref ref-type="bibr" rid="ref27">27</xref>
        ], leading also to resistance to change phenomenon which
often hampers redesign efforts [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. All in all, taking into account working style
would also lead to the satisfaction of both joint understanding and involvement
principles advocated as two of the identified ten principles for good business
process management [
        <xref ref-type="bibr" rid="ref25">25</xref>
        ].
      </p>
      <p>
        Research on style is interested to answer different critical questions about
style, and how a style could be identified is one of them [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ]. The visual
identification of a style would follow two different theoretical approaches as described
in [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]: template matching and feature analysis : the first approach relies on the
possibility to compare each new input with a standard; the last ones focuses
on the identification of a common set of critical features which characterizes
the style itself [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Here we propose a similar approach to the definition and
identification of a working style focusing on a set of features describing
possible aspects of working style as reported within the Working Style Artifact. For
the first step towards its identification, we consider working style in terms of
handover-orientedness and rework-orientedness. The first feature characterizes
the working style of a person in terms of level of handovers and this would relate
to the degree of interdependence in the work of a performer. The second feature
is intended to characterize the working style of a person in terms of amount of
rework and this is strictly connected to the concept of efficiency in working or,
following the idea of waste reduction in Lean thinking [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ], to the reduction of
over-processing. To give these features a concrete meaning we associate to them
a set of patterns identifying the repetition of a specific work condition
charactering the style of work in terms of the considered features which should be then
made visible and recognizable within the corresponding Working Style Artifact.
      </p>
      <p>
        In Computer Science the concept of pattern was mainly exploited in the
Software Engineering field, focusing on design patterns [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], intended as tools
helpful to facilitate the reuse of object oriented software already coded for a
similar problem. The idea of the authors is rooted in the work of Alexander [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ],
an Architect, who defined patterns as “elements which are a collective memory of
things which work in our surroundings”. Lately, the concept of design pattern was
extended also to the Business Process Management area, with the definition of
workflow patterns [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ], built with the same rationale in mind of design patterns
for Software Engineering. We considered here patterns, and more specifically
work patterns, concerning a repetition of obversable behaviors [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. From the
perspective of identifying patterns as a repetion of a structure, and in particular
referring to the definition of working style, we took strong inspiration from the
field of Organizational mining. Organizational mining was defined by [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ] as
part of the broader Process Mining area where the focus is on the possibility to
extract any meaningful repetition of behaviors regarding the organization of work
from logs of real work. Similarly, patterns of work has been identified in terms
of Affordance Networks [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ] within Organizational Routines, where again the
concept of organizational routine is related to “repetitive, recognizable patterns
of action” [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ].
      </p>
      <p>In the following of the paper we describe our approach to identify
working style by means of Working Style Artifacts; Conclusions and Future Works
conclude the paper.</p>
    </sec>
    <sec id="sec-2">
      <title>2 The Proposed Approach</title>
      <p>
        As the presence of Process-aware Information Systems has become readily
available, it is assumed that it is possible to extract information from transaction
logs such as i) events concerning an activity (a well defined step in a process);
ii) the case to which an event is related (the istance of the process); iii) the
performer of the event; iv) and the total order of events [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ]. In this way, the nature
of work would be analyzed thanks to this information. From this premise, we
propose a prototype which allows users to search for patterns where the
identified patterns would be related to features describing some characteristics of a
working style. Patterns will be searched within the Working Style Artifact by
means of a pattern search interface (See e.g., Fig. 4). For the search of patterns
we took inspiration from [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ] by considering the metrics proposed, in
particular the metrics based on the identification of possible causality of work such as
handovers. The occurences of the eventually found patterns are then visualized
directly in the Working Style Artifact. In addition, to facilitate the identification
of the occurrences of the selected patterns, we considered to support
juxtaposition [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] which is a technique for visually comparing information which aims at
helping “the users shift their attention between objects or see patterns between
elements” (compare e.g., the initial Working Style Artifact in Fig. 3 with the
Artifact displayed in Fig. 5 after the highlighting of the found patterns).
      </p>
      <p>
        The prototype is built using Python programming language [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] togheter with
Neo4j, a graph database [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. The choice of this database was driven by the fact
that it provides a query language, Cypher, which is oriented to the identification
of patterns within graphs. Moreover, the Cypher language, was already used for
its flexibility in the field of Business Process Management [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. For what
concerns the idea of visualizing patterns of work behavior, we took inspiration from
another tool, the EventExplorer by [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], used to identify and visualize patterns
of events regarding consumers’ activities during online commerce sessions.
2.1 The Identi cation of Patterns
To illustrate our prototype we took inspiration from the log presented in [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ].
The prototype first reads the log data expressed in CSV format (see Fig. 1),
where in each row is reported a case, an activity performed, a performer and
a timestamp. At this point, the CSV data are transformed into the related db
graph. This would then facilitate the search of patterns within Working Style
Artifact through the functionalities provided by the Cypher language.
      </p>
      <p>The graph db will include nodes: Cases, Activities, and Performers and
relations: a Case includes an Activity, an Activity is performed by a performer,
and most important of all, for the search of patterns related to working style, a
Performer works with a Performer, where this relation is set into the database
whenever a Performer p1 performed an activity immediately before an activity
performed by p2. As it is possible to notice in Fig. 1, John performs activity A
before Mike performs B, and this is represented in the graph database with the
creation of a relation works with connecting John to Mike (see Fig. 2).</p>
      <p>From the graph generated, we are able then to build the corresponding
Working Style Artifact (see Fig. 3) which is structured in this way: each row represents
a case, while each cell in the rows is colored as to represent the related performer
in completing an activity for that case. For instance, John in the first case
performs both the first and the third activity (see Fig. 1) and consequently both the
first and the third cell of the first row of the Working Style Artifact are colored
in red which is assumed to be the color representing the performer John within
the Working Style Artifact (see Fig. 3).</p>
      <p>The search for the patterns of interest is specified through a Cypher query.
In this query are to be specified: i) the two performers at the edge of the pattern
(both the request for a specific performer or for any performer is allowed); ii)
the length of the path connecting the two performers (with the Cypher language
different options are possible, such as to search for paths of any length, to search
for paths with a specific length, with at least or at most a specific length, or
to search for paths with a length falling into an interval); iii) if any performer
is selected at one edge of the pattern, whether to search for patterns including
only the same or different performers; iv) whether the activities performed by
the two performers have to be the same or not. To facilitate the definition of the
query to search for a pattern we designed a pattern search interface generating
automatically the desired query.</p>
      <p>In Fig. 4 for instance it is displayed how to set the user interface to search for
handover patterns in which John is the first performer completing an activity
(p1 is selected as “John” and p2 as “any”), and there is a direct handover of work
with other performers (path length is set to “Exactly 1” and also the “search
different performers” check box is set). The results of the query both identifies
some metrics counting the occurrence of the pattern, and identifies the recurring
patterns which are then visualized accordingly in the Working Style Artifact by
coloring in light blue all the cells corresponding to the performers involved in
the patterns (See Fig. 5).</p>
      <p>Another interesting example is related to the identification of some forms of
rework for a performer. The idea is to look for patterns whenever a performer,
e.g. John, is involved into some rework, (see Fig. 6 ).</p>
      <p>In this case the specification of rework is done by selecting “John” for both
performers and selecting “Same activity” with paths of any length. The
occurrences of the pattern are then visualized in the Working Style Artifact (See
Fig. 7).</p>
      <p>The first pattern considered in the examples is about the feature of
handoverorientedness to characterize working style. In the presented case, John’s working
style is handover-oriented as it is characterized by the presence of the handover
pattern in all of the considered cases (as it is possible to notice by comparing
the Working Style Artifact in Fig. 3 with the Working Style Artifact after the
search of the handover patterns as displayed in Fig. 5). In the second example
(see Fig. 7), the pattern we looked for is related to rework-orientedness feature.
In the presented case, the rework pattern is identified with just one occurrence
only in the first case, so due to its scarse presence, John’s working style is not
to be considered rework oriented.</p>
    </sec>
    <sec id="sec-3">
      <title>3 Conclusions and Future Works</title>
      <p>
        In this paper it is described our approach to identify working style through the
definition of a Working Style Artifact. This Artifact reifies visually the way
people work according to the data contained in a log file related to the activities
they performed in a business process. It is explained how to build and query the
Working Style Artifact by means of a prototype implemented using the Python
programming language [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] and the Neo4j graph database [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Working style is
determined by searching within the Working Style Artifact for the occurrence of
some patterns which characterize some critical common features of the working
style. However, other features could be considered to enrich the set of
common features characterizing a working style e.g., feature of autonomy: whether
a performer is the only one to perform the activities of a case or not; feature of
redundancy: whether a performer in any single case is replaceable or not by other
performers in the completion of the same activities; feature of question-answers
among pair of performers reflecting the occurrence of some Activity Patterns [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ].
Future works will be oriented to apply the approach to real cases by considering
a richer set of common features to characterize a style. Then, the future
prototype will aim at facilitating both the visual pattern recognition associated to
the features of the style and the visual comparison of Working Style Artifacts by
considering additional visualization techniques, such as Arc Diagrams [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ] and
Rythm-Eye views [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. These methods could be more useful than the simpler
visualization of the Working Style Artifact proposed in the prototype. In fact,
the first method is aimed at making more explicit the relations among different
segments of the considered Working Style Artifact so to facilitate the
identification of patterns, while the second method could make the sequences in the
Working Style Artifacts more easy to be compared as the presentation of them
is not linear and dispersed but built around a circle to facilitate comparison at
a glance. This would be especially useful for visually comparing larger Working
Style Artifacts.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>1. Merriam-webster. https://www.merriam-webster.com/dictionary/pattern.</mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <article-title>2. The Neo4j graph database</article-title>
          . https://neo4j.com/.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <article-title>Python programming language</article-title>
          . https://www.python.org/.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>C.</given-names>
            <surname>Alexander</surname>
          </string-name>
          . Notes on the Synthesis of Form. Harvard University Press,
          <year>1964</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>P.</given-names>
            <surname>Bodesinsky</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Alsallakh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Gschwandtner</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Miksch</surname>
          </string-name>
          .
          <article-title>Exploration and Assessment of Event Data</article-title>
          .
          <source>In EuroVA Workshop</source>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>C.-S.</given-names>
            <surname>Chan</surname>
          </string-name>
          .
          <source>Exploring Individual Style in Design. Environment and Planning B: Planning and Design</source>
          ,
          <volume>19</volume>
          (
          <issue>5</issue>
          ):
          <fpage>503</fpage>
          -
          <lpage>523</lpage>
          ,
          <year>1992</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>C.-S.</given-names>
            <surname>Chan</surname>
          </string-name>
          . Can Style Be Measured? Design Studies,
          <volume>21</volume>
          :
          <fpage>277</fpage>
          -
          <lpage>291</lpage>
          ,
          <year>2000</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>C. M. Eckert</surname>
            and
            <given-names>E. Y.</given-names>
          </string-name>
          <string-name>
            <surname>Do</surname>
          </string-name>
          . Special Issue: Understanding, Representing, and
          <article-title>Reasoning about Style</article-title>
          .
          <source>AI EDAM</source>
          ,
          <volume>20</volume>
          (
          <issue>3</issue>
          ):
          <fpage>163</fpage>
          -
          <lpage>165</lpage>
          ,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>E.</given-names>
            <surname>Gamma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Helm</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Johnson</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Vlissides</surname>
          </string-name>
          . Design Patterns:
          <article-title>Elements of Reusable Object-oriented Software</article-title>
          .
          <source>Addison-Wesley</source>
          ,
          <year>1995</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>M. Gleicher</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Albers</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Walker</surname>
            , I. Jusufi,
            <given-names>C. D.</given-names>
          </string-name>
          <string-name>
            <surname>Hansen</surname>
            , and
            <given-names>J. C.</given-names>
          </string-name>
          <string-name>
            <surname>Roberts</surname>
          </string-name>
          .
          <article-title>Visual Comparison for Information Visualization</article-title>
          .
          <source>Information Visualization</source>
          ,
          <volume>10</volume>
          (
          <issue>4</issue>
          ):
          <fpage>289</fpage>
          -
          <lpage>309</lpage>
          , Oct.
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <given-names>J.</given-names>
            <surname>Gulden</surname>
          </string-name>
          .
          <article-title>Visually Comparing Process Dynamics with Rhythm-Eye Views</article-title>
          , pages
          <fpage>474</fpage>
          -
          <lpage>485</lpage>
          . Springer International Publishing, Cham,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <given-names>R.</given-names>
            <surname>Hirschheim</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Newman</surname>
          </string-name>
          .
          <source>Information Systems and User Resistance: Theory and Practice. Comput. J.</source>
          ,
          <volume>31</volume>
          (
          <issue>5</issue>
          ):
          <fpage>398</fpage>
          -
          <lpage>408</lpage>
          , Oct.
          <year>1988</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <given-names>K.</given-names>
            <surname>Kammerer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Kolb</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Reichert. PQL - A Descriptive Language for Querying</surname>
          </string-name>
          ,
          <source>Abstracting and Changing Process Models</source>
          , pages
          <fpage>135</fpage>
          -
          <lpage>150</lpage>
          . Springer International Publishing,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14. E.
          <source>McCormick. Job and Task Analysis</source>
          , pages
          <fpage>651</fpage>
          -
          <lpage>96</lpage>
          . Chicago: Rand Mc nalley,
          <year>1976</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15. U. Neisser. Cognitive Psychology. Appleton-Crofts, New York,
          <year>1967</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <given-names>T.</given-names>
            <surname>Ohno</surname>
          </string-name>
          .
          <source>Toyota Production System: Beyond Large-Scale Production. Productivity</source>
          ,
          <year>1988</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <given-names>B. T.</given-names>
            <surname>Pentland</surname>
          </string-name>
          and
          <string-name>
            <given-names>T.</given-names>
            <surname>Haerem</surname>
          </string-name>
          .
          <article-title>Organizational Routines as Patterns of Action: Implications for Organizational Behavior</article-title>
          .
          <source>Annu. Rev. Organ. Psychol. Organ. Behav</source>
          .,
          <volume>2</volume>
          (
          <issue>1</issue>
          ):
          <fpage>465</fpage>
          -
          <lpage>487</lpage>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <given-names>B. T.</given-names>
            <surname>Pentland</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Recker</surname>
          </string-name>
          , and
          <string-name>
            <given-names>G. M.</given-names>
            <surname>Wyner</surname>
          </string-name>
          .
          <article-title>A Thermometer for Interdependence: Exploring Patterns of Interdependence Using Networks of Affordances</article-title>
          .
          <source>In Proceedings of ICIS</source>
          <year>2015</year>
          , Dec.
          <year>2015</year>
          ,
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>J. R. Rizzo</surname>
            ,
            <given-names>R. J.</given-names>
          </string-name>
          <string-name>
            <surname>House</surname>
            , and
            <given-names>S. I.</given-names>
          </string-name>
          <string-name>
            <surname>Lirtzman</surname>
          </string-name>
          .
          <source>Role Conflict and Ambiguity in Complex Organizations. Administrative Science Quarterly</source>
          ,
          <volume>15</volume>
          (
          <issue>2</issue>
          ):
          <fpage>150</fpage>
          -
          <lpage>163</lpage>
          ,
          <year>1970</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <given-names>M.</given-names>
            <surname>Song</surname>
          </string-name>
          and
          <string-name>
            <given-names>W. M. P. van der</given-names>
            <surname>Aalst</surname>
          </string-name>
          .
          <article-title>Towards Comprehensive Support for Organizational Mining</article-title>
          . Decis. Support Syst.,
          <volume>46</volume>
          (
          <issue>1</issue>
          ):
          <fpage>300</fpage>
          -
          <lpage>317</lpage>
          , Dec.
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <given-names>M.</given-names>
            <surname>Stacey</surname>
          </string-name>
          .
          <article-title>Psychological Challenges for the Analysis of Style. Arti cial Intelligence for Engineering Design, Analysis</article-title>
          and Manufacturing,
          <volume>20</volume>
          (
          <issue>3</issue>
          ):
          <fpage>16784</fpage>
          ,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22. L.
          <string-name>
            <surname>Thom</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Reichert</surname>
            , and
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Iochpe</surname>
          </string-name>
          .
          <article-title>Activity Patterns in Process-aware Information Systems: Basic Concepts and Empirical Evidence</article-title>
          .
          <source>Int. J. Bus. Process. Integrat. Manag. (IJBPIM)</source>
          ,
          <volume>4</volume>
          (
          <issue>2</issue>
          ):
          <fpage>93</fpage>
          -
          <lpage>110</lpage>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>W. M. P. van der Aalst</surname>
            ,
            <given-names>H. A.</given-names>
          </string-name>
          <string-name>
            <surname>Reijers</surname>
            , and
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Song</surname>
          </string-name>
          .
          <article-title>Discovering Social Networks from Event Logs</article-title>
          .
          <source>Computer Supported Cooperative Work (CSCW)</source>
          ,
          <volume>14</volume>
          (
          <issue>6</issue>
          ):
          <fpage>549</fpage>
          -
          <lpage>593</lpage>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>W. M. P. Van Der Aalst</surname>
          </string-name>
          ,
          <string-name>
            <surname>A. H. M. Ter Hofstede</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <string-name>
            <surname>Kiepuszewski</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A. P.</given-names>
            <surname>Barros</surname>
          </string-name>
          . Workflow Patterns.
          <source>Distrib. Parallel Databases</source>
          ,
          <volume>14</volume>
          (
          <issue>1</issue>
          ):
          <fpage>5</fpage>
          -
          <lpage>51</lpage>
          ,
          <year>July 2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25. J. vom Brocke, T. Schmiedel,
          <string-name>
            <given-names>J.</given-names>
            <surname>Recker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Trkman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Mertens</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Viaene</surname>
          </string-name>
          .
          <source>Ten Principles of Good Business Process Management. Business Process Management Journal</source>
          ,
          <volume>20</volume>
          (
          <issue>4</issue>
          ):
          <fpage>530</fpage>
          -
          <lpage>548</lpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <string-name>
            <given-names>M.</given-names>
            <surname>Wattenberg</surname>
          </string-name>
          . Arc Diagrams:
          <article-title>Visualizing Structure in Strings</article-title>
          .
          <source>In IEEE Symposium on Information Visualization</source>
          ,
          <year>2002</year>
          .
          <source>INFOVIS</source>
          <year>2002</year>
          ., pages
          <fpage>110</fpage>
          -
          <lpage>116</lpage>
          ,
          <year>2002</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <string-name>
            <given-names>W.</given-names>
            <surname>Wood</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Quinn</surname>
          </string-name>
          , and
          <string-name>
            <given-names>D.</given-names>
            <surname>Kashy</surname>
          </string-name>
          . Habits in Everyday Life: Thought, Emotion, and Action.
          <source>Journal of Personality and Social Psychology</source>
          ,
          <volume>83</volume>
          (
          <issue>6</issue>
          ):
          <fpage>1281</fpage>
          -
          <lpage>1297</lpage>
          ,
          <year>2002</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>