<!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>Model Reader Preferences for Semantically Duplicate Elements in BPMN</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Daniel Lübke</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Volker Stiehl</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Digital Solution Architecture GmbH</institution>
          ,
          <addr-line>Hannover</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Leibniz Universität Hannover, FG Software Engineering</institution>
          ,
          <addr-line>Hannover</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>TH Ingolstadt</institution>
          ,
          <addr-line>Ingolstadt</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>BPMN, which is the underlying modeling notation of many BPM endeavours and business information system development projects, is a rich modeling language, which also offers redundant constructs, i.e., different syntax can express the same semantics. We want to investigate which syntactical constructs are preferred by model readers if different ways to model message exchanges are offered by BPMN. In an empirical study we asked 77 participants which BPMN model they prefer for expressing eight situations. We found that send tasks and intermediate message catch events are significantly preferred. Also, event-based gateways are preferred over boundary events for many variants of the Deferred Choice pattern.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;BPMN</kwd>
        <kwd>Empirical Study</kwd>
        <kwd>Gateway</kwd>
        <kwd>Boundary Event</kwd>
        <kwd>Message</kwd>
        <kwd>Subjective Preference</kwd>
        <kwd>Event-based Gateway</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Motivation</title>
      <p>work. In Section 3 the design of our empirical study is presented. The results are presented in
Section 4 and an interpretation of those are given in Section 5. Finally, we conclude and give an
outlook.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Related Work</title>
      <p>
        Quality of business process models is multi-faceted. Lindland et al. [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] specified a framework
that can be used to categorize different quality aspects of models, in which they distinguish
between syntactic, semantic, and pragmatic qualities. This paper is concerned with subjective
preference of certain model constructs. Because “[i]n general, researchers associate aesthetics
with readability, and readability with understanding” [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] subjective preference is a part of
understandability and thus a pragmatic quality. Or as Lindland et al. put it: Understandability is
the main concern of pragmatic model quality, which “affects how to choose from among the
many ways to express a single meaning” [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Comprehension of BPMN models is a vast research
area: For example, there are studies concerning the influence of layout on understandability.
Figl provides a good overview [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Scholz &amp; Lübke [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] investigated subjective layout preferences
and used the same research design as we do: By using a quiz-like study, in which participants
choose one of the presented options, they have analyzed subjective preferences of different
choices for BPMN layouts. Moody [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] has critiqued BPMN in general for failing to adhere to his
“Physics of Notations” [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] – especially that BPMN has considerable semantic redundancy, e.g.,
the Exclusive OR Gateway has two visual representations. Genon et al. [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] found the same. The
eCH-0158 modeling guidelines for BPMN [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] recognize the redundancy between send/receive
tasks and message catching/throwing events. They standardize on send tasks and message catch
events.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Study Design</title>
      <sec id="sec-3-1">
        <title>3.1. Goals, Hypothesis &amp; Variables</title>
        <p>
          By following the Goal-Question-Metric (GQM) approach [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ] we are defining our goal as
        </p>
        <p>Understand the Subjective Preference
with regard to Semantically Equivalent Elements in BPMN 2.0</p>
        <p>from the viewpoint of a Model Reader.</p>
        <p>This goal is refined into (research) questions. While BPMN has many redundancies, we
concentrate on the ones below. We want to answer, which construct for each of the following
pairs of semantically equivalent BPMN constructs are preferred:</p>
        <sec id="sec-3-1-1">
          <title>RQ1 Send Task vs. Intermediate Message Throw Event: BPMN offers two elements for</title>
          <p>sending messages: The send task and the intermediate message throw event both send a
message.</p>
        </sec>
        <sec id="sec-3-1-2">
          <title>RQ2 Receive Task vs. Intermediate Message Catch Event: Similarily to sending a mes</title>
          <p>sage, BPMN also offers a receive task and an intermediate message catch event for receiving</p>
        </sec>
        <sec id="sec-3-1-3">
          <title>RQ3 Send Task vs. End Message Throw Event: For modeling the sending of a message at</title>
          <p>the end of a process execution, a send task and a none end event can be used. Alternatively,
an message throw end event can be used.</p>
          <p>
            RQ4 Deferred Choice between two messages (diff. prob.): A Deferred Choice [
            <xref ref-type="bibr" rid="ref3">3</xref>
            ]
between two incoming messages can be modelled via an event-based gateway or a receive
task with an interrupting message boundary event. Because one participant in [
            <xref ref-type="bibr" rid="ref7">7</xref>
            ] indicated
that he/she would model splits and joins differently depending on the probability of
the branch taken, we differentiate between the probability of events. This question is
concerned with messages that have different probabilities, i.e., the top event after the
event-based gateway and the message caught by the receive task are more likely to occur
than the bottom event, which is more exceptional, after the event-based gateway and the
message caught by the boundary event.
          </p>
        </sec>
        <sec id="sec-3-1-4">
          <title>RQ5 Deferred Choice between two messages (same prob.): This question is similar to</title>
          <p>RQ4. However, the incoming messages have the same probability, i.e., both events
following the event-based gateway and both messages occur equally often.</p>
        </sec>
        <sec id="sec-3-1-5">
          <title>RQ6 Deferred Choice between message and timer (diff. prob.): This question is similar</title>
          <p>to RQ4 but this time the Deferred Choice is not between two messages but instead
resembles a deadline situation with a message event and a timer event. It is more probable
to receive the message than to time-out. This pattern is presented as an event-based
gateway with two following events or with a receive task with an interrupting timer
boundary event.</p>
        </sec>
        <sec id="sec-3-1-6">
          <title>RQ7 Deferred Choice between message and timer (same prob.): This question is simi</title>
          <p>lar to RQ6. However, the incoming message and the time-out have the same probability.</p>
        </sec>
        <sec id="sec-3-1-7">
          <title>RQ8 Deferred Choice between two messages and a timer: The last question is con</title>
          <p>cerned with a Deferred Choice between two messages and a timer, i.e., a scenario in
which one of two messages must be received within a certain time. This can – again – be
modeled as an event-based gateway followed by two message events and one timer event,
or by a receive task with two boundary events.</p>
        </sec>
        <sec id="sec-3-1-8">
          <title>3.1.1. Measurements &amp; Hypothesis</title>
          <p>We measure the subjective preferences of study participants as the only metric for all research
questions. For all research questions the null hypothesis H0 is that there is no preference for
one of the two alternatives. Accordingly, H1 is that one of the two alternatives is preferred.</p>
        </sec>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Objects</title>
        <p>
          The study setup is similar to a previous study by Scholz &amp; Lübke [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]: Participants take part
in an online survey in which two diagrams modeling the same process are shown which only
differ in one point. In this study different but semantically equivalent BPMN diagrams were
used as shown in Appendix A. Both options were shown side by side and participants had to
choose the preferred one by clicking it. Descriptive text was shown to convey the probablity
of some branches. Since branching probabilities cannot be modeled in BPMN directly, it was
necessary to convey this information textually.
        </p>
      </sec>
      <sec id="sec-3-3">
        <title>3.3. Participants</title>
        <p>Participants were a) recruited from lectures of the authors and b) professionals were asked to
participate. We tracked the group to which a participant belongs to by using different invitation
links. Participation was voluntary and no incentives were given. The number of participants
per group and a more detailed description is shown in Table 1. All in all, we had 87 participants
in total. After removing those, who did not complete the quiz or changed their answers in
between, 77 participants remained.</p>
      </sec>
      <sec id="sec-3-4">
        <title>3.4. Validity Procedure</title>
        <p>As a first step we performed a power test: For a two-sided hypothesis test with α = p = 0.05
and confidence β = 0.95 for a medium effect of h = 0.5 yields that we required at least 52
participants. As described above we recruited more participants than required. For eliminating
extraneous variables we took following measures: We randomized the order in which questions
(i.e., diagram pairs) were shown. Thereby, we try to eliminate learning and fatigue effects. We
also randomized the order in which diagrams are shown.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Analysis</title>
      <p>The statistical evaluation of the gathered data is shown in Table 2. The statistical significance
indicated by the p-values is marked by asterisks (*: p ≤ 0.05, **: p ≤ 0.01, ***: p ≤ 0.001).
Similarily, the effect is denoted by pluses (+: h ≥ 0.2, ++: h ≥ 0.5, +++: h ≥ 0.8).
5. Interpretation
5.1. Evaluation of Results &amp; Implications
#A</p>
      <p>#B
The send task is significantly preferred over a message throw event (RQ1). It seems that
participants see the sending of a message more as a task, i.e., an active action, and therefore prefer the
task instead of an event.</p>
      <p>In contrast to RQ1, participants significantly prefer a message catch event for waiting on a
message receive (RQ2). Interestingly, it is inconsistent to use different syntax for sending and
receiving messages. This can mean that perhaps participants differentiate between active and
passive/waiting elements.</p>
      <p>There is no significant difference for sending a message at the process end (RQ3). In contrast
to a significant preference for a send task during the process, there is no clear preference for
a send task with an end event or a message end event. It seems that the additional penalty of
a second symbol and its associated space requirements is not worth to keep up the semantic
difference experienced in RQ1.</p>
      <p>When modeling a Deferred Choice between two messages which arrive with different
probabilities, participants prefer the use of an event-based gateway (RQ4). It may be that the visuals of
two white envelopes – one in the receive task and one in the boundary event – is not attractive.
Participants have an even stronger preference for the gateway if the probability of the messages
are the same (RQ5).</p>
      <p>When modeling a time-out, i.e., a Deferred Choice between a message and a timer, neither
the gateway nor the boundary event is preferred – regardless of whether the timer is as likely to
occur (RQ6) or is only triggered as an exception (RQ7). This contrasts with the results from
RQ4/5, which are structurally the same but use a different second event. While more participants
liked the gateway for same probabilities of events and more participants liked the boundary
event for exceptional cases, these differences were not significant. More research has to further
clarify whether there is a difference with a small effect or not.</p>
      <p>If the Deferred Choice is between two messages and a timer event (RQ8) there is a strong,
significant preference to the event-based gateway. However, we cannot attribute to why this is:
While in our study planning we wanted to examine the effect of a larger number of boundary
events, another possible explanation is that a send task with a message boundary event is
disliked as RQ4 and RQ5 have shown.</p>
      <sec id="sec-4-1">
        <title>5.2. Limitations of Study</title>
        <p>Because we only measured subjective preferences no quantative data on model comprehension
could be measured. This study still gives insights into model perception, especially with different
variants of the Deferred Choice pattern. Like all studies which include students, the question of
generalizability arises. However, we have seen that no differences between our groups exist –
this also means that the group of professionals does not behave significantly different from the
students. While we had a considerable amount of participants, some research questions gave
non-significant results with a small effect size in the range of 0.1 ≤ h ≤ 0.2. To have adequate
power in the statistical tests, more participants (approx. 350) are required.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>6. Implications for Practitioners</title>
      <p>Following from these results practitioners should amend existing modeling guidelines by the
following rules: 1) Use Send Tasks for sending messages during process execution, 2) use Message
Catch Events for receiving messages during process execution, and 3) use Event-based Gateways
when implementing the Deferred Choice pattern when receiving multiple messages. Modelers
should keep in mind that this is the first study to examine these constructs. Hopefully, future
studies will strengthen or refute these results and thus these proposed modeling guidelines.</p>
    </sec>
    <sec id="sec-6">
      <title>7. Conclusions &amp; Outlook</title>
      <p>Within this paper we presented our empirical study with students from two universities and
professionals on the subjective preference of syntactically redundant, message-related constructs
in BPMN. We found a strong subjective preference for send tasks over message throw events
within the process-flow and for message catch events over receive tasks. We also found that
Deferred Choices in event-based gateways are preferred over boundary events in the case of
two message events or three events. We could find no significant preference for Deferred
Choices with a message and a timer (“time-outs”) or for the sending of a message on process
completion. While the results are interesting in themselves, this study lays the foundation
for further empirical inqueries: Follow up studies, especially experiments, can investigate
and compare understandability of redundant BPMN message-related constructs. This way,
especially eye-tracking experiments, can be used to gather quantative data to evaluate whether
the subjective preferences match the differences in objective understandability in the future,
and further developing modeling guidelines for BPMN.</p>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgments</title>
      <p>We’d like to thank all participants who took part in our study. Additionally, we like to thank
Kurt Schneider, Dieter Kähny, and Barbara Ulrich for distributing the quiz within their classes
and organizations.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>V.</given-names>
            <surname>Stiehl</surname>
          </string-name>
          ,
          <source>Implementing the Basic Architecture of Process-Driven Applications</source>
          , Springer,
          <year>2014</year>
          . URL: http://link.springer.com/chapter/10.1007/978-3-
          <fpage>319</fpage>
          -07218-
          <issue>0</issue>
          _
          <fpage>4</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>B.</given-names>
            <surname>Rücker</surname>
          </string-name>
          ,
          <article-title>3 common pitfalls in microservice integration and how to avoid them</article-title>
          , WWW: https://berndruecker.io/3
          <article-title>-pitfalls-in-microservice-integration/</article-title>
          ,
          <source>last access: 2021-02-18</source>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>W. M. van Der</given-names>
            <surname>Aalst</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. H.</given-names>
            <surname>Ter Hofstede</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Kiepuszewski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. P.</given-names>
            <surname>Barros</surname>
          </string-name>
          , Workflow patterns,
          <source>Distributed and parallel databases 14</source>
          (
          <year>2003</year>
          )
          <fpage>5</fpage>
          -
          <lpage>51</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>O. I.</given-names>
            <surname>Lindland</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Sindre</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Solvberg</surname>
          </string-name>
          ,
          <article-title>Understanding quality in conceptual modeling</article-title>
          ,
          <source>IEEE Software 11</source>
          (
          <year>1994</year>
          )
          <fpage>42</fpage>
          -
          <lpage>49</lpage>
          . doi:
          <volume>10</volume>
          .1109/52.268955.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>C.</given-names>
            <surname>Bennett</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Ryall</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Spalteholz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Gooch</surname>
          </string-name>
          ,
          <article-title>The aesthetics of graph visualization</article-title>
          ,
          <source>Proceedings of Computational Aesthetics in Graphics, Visualization</source>
          , and
          <string-name>
            <surname>Imaging</surname>
          </string-name>
          (
          <year>2007</year>
          )
          <fpage>57</fpage>
          -
          <lpage>64</lpage>
          . doi:
          <volume>10</volume>
          .2312/COMPAESTH/COMPAESTH07/057-
          <fpage>064</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>K.</given-names>
            <surname>Figl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Recker</surname>
          </string-name>
          ,
          <article-title>Exploring cognitive style and task-specific preferences for process representations</article-title>
          ,
          <source>Requirements Engineering</source>
          <volume>21</volume>
          (
          <year>2016</year>
          )
          <fpage>63</fpage>
          -
          <lpage>85</lpage>
          . URL: http://dx.doi.org/10. 1007/s00766-014-0210-2. doi:
          <volume>10</volume>
          .1007/s00766-014-0210-2.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>T.</given-names>
            <surname>Scholz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Lübke</surname>
          </string-name>
          ,
          <article-title>Improving automatic bpmn layouting by experimentally evaluating user preferences</article-title>
          , in: Á. Rocha,
          <string-name>
            <given-names>H.</given-names>
            <surname>Adeli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. P.</given-names>
            <surname>Reis</surname>
          </string-name>
          , S. Costanzo (Eds.),
          <source>New Knowledge in Information Systems and Technologies</source>
          , Springer International Publishing, Cham,
          <year>2019</year>
          , pp.
          <fpage>748</fpage>
          -
          <lpage>757</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>D. L</surname>
          </string-name>
          . Moody,
          <article-title>Why a Diagram is Only Sometimes Worth a Thousand Words: An Analysis of the BPMN 2.0 Visual Notation</article-title>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>D. L. Moody,</surname>
          </string-name>
          <article-title>The physics of notations: toward a scientific basis for constructing visual notations in software engineering</article-title>
          , Software Engineering, IEEE Transactions on
          <volume>35</volume>
          (
          <year>2009</year>
          )
          <fpage>756</fpage>
          -
          <lpage>779</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>N.</given-names>
            <surname>Genon</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Heymans</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Amyot</surname>
          </string-name>
          ,
          <article-title>Analysing the cognitive effectiveness of the bpmn 2.0 visual notation</article-title>
          , in: B.
          <string-name>
            <surname>Malloy</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Staab</surname>
          </string-name>
          , M. van den Brand (Eds.),
          <source>Software Language Engineering</source>
          , Springer Berlin Heidelberg, Berlin, Heidelberg,
          <year>2011</year>
          , pp.
          <fpage>377</fpage>
          -
          <lpage>396</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>A.</given-names>
            <surname>Birchler</surname>
          </string-name>
          , E. Bosshart,
          <string-name>
            <given-names>M.</given-names>
            <surname>Märki</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Opitz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Pauli</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Rigert</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Sandoz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Schaffroth</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Spöcker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Tanner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Walser</surname>
          </string-name>
          , T. Widmer, eCH-0158
          <string-name>
            <surname>BPMN-</surname>
          </string-name>
          <article-title>Modellierungskonventionen für die öffentliche Verwaltung</article-title>
          , WWW: https://www.ech.ch/dokument/fb5725cb-813f
          <string-name>
            <surname>-</surname>
          </string-name>
          47dc-
          <fpage>8283</fpage>
          -c04f9311a5b8,
          <year>2014</year>
          . URL: https://www.ech.ch/dokument/fb5725cb-813f
          <string-name>
            <surname>-</surname>
          </string-name>
          47dc-
          <fpage>8283</fpage>
          -c04f9311a5b8.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>V. R.</given-names>
            <surname>Basili</surname>
          </string-name>
          ,
          <article-title>Applying the goal/question/metric paradigm in the experience factory</article-title>
          ,
          <source>Software Quality Assurance and Measurement: A Worldwide Perspective</source>
          (
          <year>1993</year>
          )
          <fpage>21</fpage>
          -
          <lpage>44</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>