<!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>Improving Comprehension of Process Diagrams with Graphical Highlights</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Gregor Jost</string-name>
          <email>gregor.jost@um.si</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>The Faculty of Electrical Engineering and Computer Science at the University of Maribor</institution>
          ,
          <addr-line>2000 Maribor</addr-line>
          ,
          <country>Slovenia https</country>
          <institution>://feri.um.si/en/about-us/</institution>
        </aff>
      </contrib-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Business processes are core assets of organizations, and they re ect what
companies do when they deliver services or products to customers. As such, an
organization can outperform its competitors if it has more e ective processes and
executes them more e ciently [
        <xref ref-type="bibr" rid="ref10 ref5">5, 10</xref>
        ]. This is reasonable, since process-oriented
structures help organizations to adapt to the increasingly changing environment
[
        <xref ref-type="bibr" rid="ref20">20</xref>
        ].
      </p>
      <p>
        Business processes can be represented in the form of business process
models, which capture both how the business works, and how the value is created
for various stakeholders [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ]. In this regard, business process models aid in the
communication between the stakeholders, thus, they must be easy to understand
[
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. While business process models can be represented by means of textual
description, it is a common practice to depict them graphically [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] with business
process diagrams [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
      <p>
        There are many visual languages for representing business processes
diagrammatically. However, choosing the most appropriate visual language for
diagrammatic modeling is not a guarantee for a more e ective communication between
the stakeholders. The e ectiveness of such communication is in uenced mainly
by how the intended message (i.e., how the modeler understands a diagram)
matches the received message (i.e., how the reader understands the same
diagram) [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. This can become challenging to achieve, as business process diagrams
can easily become large and di cult to understand [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ]. This is often due to the
complexity of the nature of the problem, which is re ected directly in the
business process diagrams. On the other hand, they can also become unnecessarily
complex, since one behavior can be modeled in di erent ways [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. Indeed, one of
the most common mistakes when modeling diagrams is to display too much
information on a single diagram, which increases the diagram's complexity needlessly
[
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. Incorrect understanding of business process diagrams can cause a variety of
issues [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], e.g., inadequate implementation of the corresponding supporting
systems and other design aws [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. Complex business process diagrams can also
become a barrier rather than an aid to communication with stakeholders [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ],
and can make it harder to determine if they capture the business practices
correctly [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. Considering this, we can conclude that the complexity of a diagram
directly a ects its comprehensibility [
        <xref ref-type="bibr" rid="ref11 ref13">11, 13</xref>
        ] (sometimes used as a synonym for
understandability [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]), since there are limits in human cognitive capabilities to
make sense of complex diagrams [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ].
      </p>
      <p>
        In this light, cognitive e ectiveness of diagrams was de ned as the speed,
ease, and accuracy with which a model representation can be processed by the
human mind [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. However, cognitive e ectiveness is not an inherent property
of diagrams, but it must be designed into them. To this end, nine principles for
creating cognitively e ective diagrams were proposed, namely [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]:
1. Discriminability,
2. Manageable complexity,
3. Emphasis,
4. Cognitive integration,
5. Perceptual directness,
6. Structure,
7. Identi cation,
8. Visual expressiveness, and
9. Graphic simplicity.
      </p>
      <p>
        Some of these principles are already integrated in the diagramming notations,
e.g., Business Process Model and Notation (BPMN) has built-in mechanisms for
managing complexity in the form of Link Events for achieving modularization
and Sub-Processes for hierarchic structuring [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. Regardless of these built-in
mechanisms, managing complex business process diagrams is a task that is still
fraught with challenges [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. This might also be because, according to Moody
[
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], the design of diagramming notations is mostly unscienti c and based on
personal taste or intuition. Indeed, some of the most predominant diagramming
notations that enable modeling of business process diagrams are perceived as
being complex and not easy to learn, even for business analysts [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Similarly,
modelers are typically not instructed on how to create cognitively e ective
diagrams, hence, they rely on their intuition and experience. As such, the resulting
diagrams might distort the information, or even convey unintentional messages
[
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. Hence, it is reasonable that there is a considerable body of literature
regarding the cognitive e ectiveness of business process diagrams. These studies
commonly apply the aforementioned principles for creating cognitively e ective
diagrams by leveraging the extensibility of the elements' non-standardized
visual variables for displaying di erent kinds of information. This is also known
as secondary notation [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], which can improve the comprehension of diagrams
(e.g., associating a speci c color with an organization's role [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]). Other
studies propose extensions of the existing diagramming notations [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ], which do not
violate the speci cation, but they change the corresponding metamodel (e.g.,
simplifying temporal constructs in order to increase readability [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]).
      </p>
      <p>
        To summarize the above, the main purpose of business process diagrams is
to facilitate the communication between the process-related stakeholders, which
directly a ects the decision-making. For this reason, they must be easy to
understand. However, this is often challenging to achieve, since business process
diagrams can become large and complex. In this light, the low level of modeling
competence in a casual modeler has been recognized as one of the main causes
that process diagrams lack in quality [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. The common modeling mistakes can
make diagrams a barrier instead of an aid to communication [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], and poorly
designed diagrams may be even less e ective than text [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. To this end, many
frameworks, principles and guidelines for modeling were proposed. While they
commonly lack a sound research foundation, or are too abstract [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], several
attempts were made to provide empirically-based and operational guidance for
both designers and users of diagrams, e.g.: [
        <xref ref-type="bibr" rid="ref12 ref14 ref2">14, 12, 2</xref>
        ]. However, the majority of
these approaches intervene in the diagramming notations' speci cations or the
business process diagrams' de nition. As such, they require that the
information of applied principle is stored either in the process diagram's model or the
diagramming notation's metamodel. This can cause several issues, e.g.,
interoperability and compatibility between the diagrammatic tools is hindered [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ].
Furthermore, overuse of speci c approaches (e.g., Graphical Highlight pattern
[
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]) may lead to potentially unreadable process diagrams [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ].
      </p>
      <p>Based on these challenges, the goal of this doctoral thesis was to propose
and investigate a non-intrusive approach that makes business process diagrams
appear less complex, without changing the corresponding diagrammatic notation
or the business process diagrams themselves. This was done by manipulating
the opacity of graphical elements in order to emphasize the important parts
of a business process diagram by lowlighting the irrelevant ones. The proposed
solution, named Emphasis, implemented with opacity-based Graphical Highlight
pattern, abbreviated as simply Graphical highlights, introduces six Structural
and seven Behavioral Graphical highlights.</p>
      <p>Graphical highlights were rstly applied to a sample business process
diagram, modeled in Business Process Model and Notation (BPMN). The analysis
addressed the real-world procedure, and based on the survey of the process, we
applied one representative of Structural and one representative of Behavioral
Graphical highlight, respectively, to the conventional process diagram.
Afterwards, the complexity analysis of all three process diagrams was performed.
Based on the results of the analysis, we can conclude that the application of
either Structural or Behavioral Graphical highlights decreased the complexity of
the highlighted part of the process diagram in almost all of the observed
measures. In several cases this meant that understandability of the process diagram
increased.</p>
      <p>Afterwards, a Web application prototype was implemented, which supports
the proposed set of Graphical highlights. The prototype can render the business
process diagrams and provide the support for both categories of the
aforementioned Graphical highlights. The back end of the prototype was implemented
in PHP: Hypertext Preprocessor programming language, while the front end is
served using the AngularJS, a JavaScript open-source web application
framework, and Bootstrap, a framework for developing responsive and mobile-friendly
Graphical User Interfaces (GUIs).</p>
      <p>Furthermore, we empirically validated whether Graphical highlights
positively impact cognitive e ectiveness of business process diagrams, and if the
users will nd the prototype implementation useful. To this end, an
experimental research, which included 85 participants, was conducted. The participants
were randomly assigned in either the treatment group (Graphical highlights
diagram representation approach), or the control group (conventional diagram
representation approach). In accordance with the de nition of cognitive e
ectiveness, speed, ease, and accuracy of answering 26 comprehension questions
were observed, along with the perceived usefulness of the prototype. The results
of the analysis demonstrated that participants who used Graphical highlights
signi cantly outperformed those that used the conventional approach in all
experiment's observations.</p>
      <p>We can conclude that using Graphical highlights increases the cognitive
effectiveness of business process diagrams, while the corresponding prototype
implementation is perceived as being useful by the experiment's participants. The
results supplement the related work, which demonstrated that the color-based
Graphical Highlight pattern is perceived as useful and increases the ease of use.
However, conversely from the related work, Graphical highlights do not interfere
with either the diagramming notations or with the process diagrams. Since
process diagrams are valuable organizational assets that facilitate decision-making
activities and communication, we consider Graphical highlights as a cognitive
e ective mechanism that simpli es those activities further.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Cardoso</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mendling</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Neumann</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reijers</surname>
            ,
            <given-names>H.A.</given-names>
          </string-name>
          :
          <article-title>A Discourse on Complexity of Process Models</article-title>
          .
          <source>In: Proceedings of the 2006 International Conference on Business Process Management Workshops</source>
          . pp.
          <volume>117</volume>
          {
          <fpage>128</fpage>
          . BPM'06,
          <string-name>
            <surname>SpringerVerlag</surname>
          </string-name>
          , Berlin, Heidelberg (
          <year>2006</year>
          ). https://doi.org/10.1007/11837862 13, http: //dx.doi.org/10.1007/11837862{\_}
          <fpage>13</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Corradini</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ferrari</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fornari</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gnesi</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Polini</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Re</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Spagnolo</surname>
            ,
            <given-names>G.O.:</given-names>
          </string-name>
          <article-title>A Guidelines framework for understandable BPMN models</article-title>
          .
          <source>Data &amp; Knowledge Engineering</source>
          <volume>113</volume>
          , 129 {
          <fpage>154</fpage>
          (
          <year>2018</year>
          ). https://doi.org/https://doi.org/10.1016/j.datak.
          <year>2017</year>
          .
          <volume>11</volume>
          .003, http://www. sciencedirect.com/science/article/pii/S0169023X1630341X
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>DaSilva</surname>
            ,
            <given-names>C.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Trkman</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          : Business Model: What It Is and What It Is Not.
          <source>Long Range Planning</source>
          <volume>47</volume>
          (
          <issue>6</issue>
          ),
          <volume>379</volume>
          {
          <fpage>389</fpage>
          (
          <year>2014</year>
          ). https://doi.org/https://doi.org/10.1016/j.lrp.
          <year>2013</year>
          .
          <volume>08</volume>
          .004, http://www. sciencedirect.com/science/article/pii/S0024630113000502
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Dikici</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Turetken</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Demirors</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          :
          <article-title>Factors in uencing the understandability of process models: A systematic literature review</article-title>
          .
          <source>Information and Software Technology</source>
          <volume>93</volume>
          ,
          <issue>112</issue>
          {
          <fpage>129</fpage>
          (
          <year>2018</year>
          ). https://doi.org/https://doi.org/10.1016/j.infsof.
          <year>2017</year>
          .
          <volume>09</volume>
          .001, http://www. sciencedirect.com/science/article/pii/S0950584916302889
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Dumas</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosa</surname>
            ,
            <given-names>M.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mendling</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reijers</surname>
            ,
            <given-names>H.A.</given-names>
          </string-name>
          :
          <source>Fundamentals of Business Process Management</source>
          . Springer Publishing Company, Incorporated (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Fernandez</surname>
            ,
            <given-names>H.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Palacios-Gonzalez</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Garc</surname>
          </string-name>
          a-D
          <string-name>
            <surname>az</surname>
          </string-name>
          , V.,
          <string-name>
            <surname>Pelayo</surname>
            <given-names>G</given-names>
          </string-name>
          -Bustelo,
          <string-name>
            <given-names>B.C.</given-names>
            , Sanjuan Mart nez, O.,
            <surname>Cueva</surname>
          </string-name>
          <string-name>
            <surname>Lovelle</surname>
          </string-name>
          ,
          <string-name>
            <surname>J.M.:</surname>
          </string-name>
          <article-title>SBPMN - An Easier Business Process Modeling Notation for Business Users</article-title>
          .
          <source>Comput. Stand. Interfaces</source>
          <volume>32</volume>
          (
          <issue>1-2</issue>
          ),
          <volume>18</volume>
          { 28 (Jan
          <year>2010</year>
          ). https://doi.org/10.1016/j.csi.
          <year>2009</year>
          .
          <volume>04</volume>
          .006, http://dx.doi.org/10. 1016/j.csi.
          <year>2009</year>
          .
          <volume>04</volume>
          .006
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Gagne</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Trudel</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Time-BPMN</article-title>
          .
          <source>In: Proceedings of the 2009 IEEE Conference on Commerce and Enterprise Computing</source>
          . pp.
          <volume>361</volume>
          {
          <fpage>367</fpage>
          . CEC '09, IEEE Computer Society, Washington, DC, USA (
          <year>2009</year>
          ). https://doi.org/10.1109/CEC.
          <year>2009</year>
          .
          <volume>71</volume>
          , http://dx.doi.org/10.1109/CEC.
          <year>2009</year>
          .71
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Genon</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Heymans</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Amyot</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Analysing the Cognitive E ectiveness of the BPMN 2.0 Visual Notation</article-title>
          .
          <source>In: Proceedings of the Third International Conference on Software Language Engineering</source>
          . pp.
          <volume>377</volume>
          {
          <fpage>396</fpage>
          . SLE'
          <volume>10</volume>
          , Springer-Verlag, Berlin, Heidelberg (
          <year>2011</year>
          ), http://dl.acm.org/citation.cfm?id=
          <volume>1964571</volume>
          .
          <fpage>1964605</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Gruhn</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Laue</surname>
          </string-name>
          , R.:
          <article-title>Complexity metrics for business process models</article-title>
          .
          <source>In: 9th international conference on business information systems (BIS</source>
          <year>2006</year>
          ). vol.
          <volume>85</volume>
          , pp.
          <volume>1</volume>
          {
          <issue>12</issue>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Kunze</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Luebbe</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weidlich</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weske</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Towards Understanding Process Modeling { The Case of the BPM Academic Initiative</article-title>
          . In: Dijkman,
          <string-name>
            <given-names>R.</given-names>
            ,
            <surname>Hofstetter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Koehler</surname>
          </string-name>
          ,
          <string-name>
            <surname>J</surname>
          </string-name>
          . (eds.) Business Process Model and Notation: Third International Workshop, BPMN 2011, Lucerne, Switzerland,
          <source>November 21-22</source>
          ,
          <year>2011</year>
          . Proceedings, pp.
          <volume>44</volume>
          {
          <fpage>58</fpage>
          . Springer Berlin Heidelberg, Berlin, Heidelberg (
          <year>2011</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>642</fpage>
          -25160-3 4, https://doi.org/10.1007/ 978-3-
          <fpage>642</fpage>
          -25160-3{\_}
          <fpage>4</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Lassen</surname>
          </string-name>
          , K.B.,
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          :
          <article-title>Complexity Metrics for Work ow Nets</article-title>
          .
          <source>Inf. Softw. Technol</source>
          .
          <volume>51</volume>
          (
          <issue>3</issue>
          ),
          <volume>610</volume>
          {626 (Mar
          <year>2009</year>
          ). https://doi.org/10.1016/j.infsof.
          <year>2008</year>
          .
          <volume>08</volume>
          .005, http://dx.doi.org/10.1016/j. infsof.
          <year>2008</year>
          .
          <volume>08</volume>
          .005
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Mendling</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reijers</surname>
          </string-name>
          , H., van der Aalst, W.:
          <article-title>Seven process modeling guidelines (7PMG)</article-title>
          .
          <source>Information and Software Technology</source>
          <volume>52</volume>
          (
          <issue>2</issue>
          ),
          <volume>127</volume>
          {
          <fpage>136</fpage>
          (
          <year>2010</year>
          ). https://doi.org/https://doi.org/10.1016/j.infsof.
          <year>2009</year>
          .
          <volume>08</volume>
          .004, http://www. sciencedirect.com/science/article/pii/S0950584909001268
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Mendling</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reijers</surname>
            ,
            <given-names>H.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cardoso</surname>
          </string-name>
          , J.:
          <source>What Makes Process Models Understandable? In: Proceedings of the 5th International Conference on Business Process Management</source>
          . pp.
          <volume>48</volume>
          {
          <fpage>63</fpage>
          . BPM'
          <volume>07</volume>
          , Springer-Verlag, Berlin, Heidelberg (
          <year>2007</year>
          ), http://dl.acm.org/citation.cfm?id=
          <volume>1793114</volume>
          .
          <fpage>1793120</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14. Moody, D.:
          <article-title>What Makes a Good Diagram? Improving the Cognitive E ectiveness of Diagrams in IS Development</article-title>
          . In: Wojtkowski,
          <string-name>
            <given-names>W.</given-names>
            ,
            <surname>Wojtkowski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.G.</given-names>
            ,
            <surname>Zupancic</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Magyar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            ,
            <surname>Knapp</surname>
          </string-name>
          ,
          <string-name>
            <surname>G</surname>
          </string-name>
          . (eds.)
          <source>Advances in Information Systems Development: New Methods and Practice for the Networked Society</source>
          . pp.
          <volume>481</volume>
          {
          <fpage>492</fpage>
          .
          <string-name>
            <surname>Springer</surname>
            <given-names>US</given-names>
          </string-name>
          , Boston, MA (
          <year>2007</year>
          ). https://doi.org/10.1007/978-0-
          <fpage>387</fpage>
          -70802-7 40, https://doi. org/10.1007/978-0-
          <fpage>387</fpage>
          -70802-7{\_}
          <fpage>40</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15. Moody, D.:
          <article-title>The \Physics" of Notations: Toward a Scienti c Basis for Constructing Visual Notations in Software Engineering</article-title>
          .
          <source>IEEE Transactions on Software Engineering</source>
          <volume>35</volume>
          (
          <issue>6</issue>
          ),
          <volume>756</volume>
          {779 (Nov
          <year>2009</year>
          ). https://doi.org/10.1109/TSE.
          <year>2009</year>
          .67
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16. Moody, D., van Hillegersberg,
          <string-name>
            <surname>J.</surname>
          </string-name>
          :
          <article-title>Evaluating the Visual Syntax of UML: An Analysis of the Cognitive E ectiveness of the UML Family of Diagrams</article-title>
          . In: Gasevic,
          <string-name>
            <given-names>D.</given-names>
            , Lammel, R.,
            <surname>Van Wyk</surname>
          </string-name>
          ,
          <string-name>
            <surname>E</surname>
          </string-name>
          . (eds.)
          <source>Software Language Engineering</source>
          . pp.
          <volume>16</volume>
          {
          <fpage>34</fpage>
          . Springer Berlin Heidelberg, Berlin, Heidelberg (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17. Muller, R.,
          <string-name>
            <surname>Rogge-Solti</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>BPMN for healthcare processes</article-title>
          .
          <source>In: Proceedings of the 3rd Central-European Workshop on Services and their Composition (ZEUS</source>
          <year>2011</year>
          ), Karlsruhe, Germany (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Rosa</surname>
            ,
            <given-names>M.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>ter Hofstede</surname>
            ,
            <given-names>A.H.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wohed</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reijers</surname>
            ,
            <given-names>H.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mendling</surname>
            , J., van der Aalst,
            <given-names>W.M.P.</given-names>
          </string-name>
          :
          <article-title>Managing Process Model Complexity via Concrete Syntax Modications</article-title>
          .
          <source>IEEE Transactions on Industrial Informatics</source>
          <volume>7</volume>
          (
          <issue>2</issue>
          ),
          <volume>255</volume>
          {265 (May
          <year>2011</year>
          ). https://doi.org/10.1109/TII.
          <year>2011</year>
          .2124467
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Smirnov</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reijers</surname>
            ,
            <given-names>H.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weske</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>A Semantic Approach for Business Process Model Abstraction</article-title>
          . In: Mouratidis,
          <string-name>
            <given-names>H.</given-names>
            ,
            <surname>Rolland</surname>
          </string-name>
          , C. (eds.) Advanced Information Systems Engineering: 23rd International Conference, CAiSE
          <year>2011</year>
          , London, UK, June 20-24,
          <year>2011</year>
          . Proceedings. pp.
          <volume>497</volume>
          {
          <fpage>511</fpage>
          . Springer Berlin Heidelberg, Berlin, Heidelberg (
          <year>2011</year>
          ). https://doi.org/10.1007/978-3-
          <fpage>642</fpage>
          -21640-4 37, https: //doi.org/10.1007/978-3-
          <fpage>642</fpage>
          -21640-4{\_}
          <fpage>37</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Trkman</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mendling</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krisper</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Using Business Process Models to Better Understand the Dependencies Among User Stories</article-title>
          .
          <source>Inf. Softw. Technol</source>
          . 71(C),
          <volume>58</volume>
          { 76 (Mar
          <year>2016</year>
          ). https://doi.org/10.1016/j.infsof.
          <year>2015</year>
          .
          <volume>10</volume>
          .006, http://dx.doi.org/ 10.1016/j.infsof.
          <year>2015</year>
          .
          <volume>10</volume>
          .006
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Yous</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bauer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Saidi</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dey</surname>
            ,
            <given-names>A.K.</given-names>
          </string-name>
          :
          <article-title>uBPMN: A BPMN extension for modeling ubiquitous business processes</article-title>
          .
          <source>Information and Software Technology</source>
          <volume>74</volume>
          (
          <string-name>
            <surname>Supplement</surname>
            <given-names>C)</given-names>
          </string-name>
          ,
          <volume>55</volume>
          {
          <fpage>68</fpage>
          (
          <year>2016</year>
          ). https://doi.org/https://doi.org/10.1016/j.infsof.
          <year>2016</year>
          .
          <volume>02</volume>
          .002, http://www. sciencedirect.com/science/article/pii/S0950584916300209
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>