<!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>Investigating the Collaborative Process of Process Modeling</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Simon Forster</string-name>
          <email>simon.forster@uibk.ac.at</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>University of Innsbruck Technikerstrasse 21a</institution>
          ,
          <addr-line>6020 Innsbruck</addr-line>
          ,
          <country country="AT">Austria</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Research on quality issues of business process models has recently begun to explore the process of creating process models. With growing complexity, the creation of business process models requires the presence of several, potentially spatially distributed stakeholders. As a consequence, the question arises how this a ects the process of process modeling. This paper describes a thesis working on this question. More precisely, an infrastructure for recording and analyzing the collaborative process of process modeling is introduced and further used for investigating this process using empirical research methods.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Introduction
\Business process modeling is the task of creating an explicit, graphical model
of a business process from internalized knowledge on that process " [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. The
resulting business process models play an important role for the management of
business processes [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], depicting how \various tasks are coordinated to achieve
speci c organizational goals " [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Such process models are used to build a
consensus among stakeholders involved within the business process [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], help to obtain
a common understanding of a company's business processes [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], serve as drivers
for the implementation and enactment of business processes, and enable the
discovery of improvement opportunities [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Therefore, the quality of business
process models is essential [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] as it constitutes a measure of the ful llment of its
purpose (e.g., to serve as a basis for a system development project) [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. However,
industrial process model collections su er from a range of quality problems.
Understandability of process models su ers from poor quality which subsequently
hampers the models' maintainability [
        <xref ref-type="bibr" rid="ref8 ref9">8, 9</xref>
        ]. Examples for typical quality
problems are non-intention-revealing or inconsistent naming [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], redundant process
fragments [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] or overly large and unnecessarily complex models [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
      </p>
      <p>
        To address these quality problems signi cant research has been conducted in
recent years on factors that impact process model understandability and
maintainability [
        <xref ref-type="bibr" rid="ref6 ref8 ref9">8, 9, 6</xref>
        ]. Focus of these works is on the outcome of the modeling process
[
        <xref ref-type="bibr" rid="ref13 ref14">13, 14</xref>
        ], i.e., the resulting process model. In turn, relatively little emphasis has
been put on the fact that model quality presumably depends upon the
modeling process that was followed to create it, i.e., the process of process modeling
(PPM) [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. For example, [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] aims at a better understanding of the PPM, i.e.,
the formalization of a process model from an informal requirements speci
cation. Thereby, [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] assumes a modeling setting where a single model engineer
is creating a process model and where the communication between model
engineers and domain experts is mediated via an informal requirements speci cation
[
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. However, when looking at the complexity of real life projects it is often not
possible to have only a single model engineer creating the corresponding
business process model, since knowledge of the business process might be distributed
over a number of domain experts [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]. Similarly, the corresponding knowledge
to create the process model has to be distributed among model engineers. As
a consequence, various domain experts and model engineers are involved in the
development cycle, who collaboratively create a process model [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. By this close
collaboration the border between requirements elicitation and formalization
becomes blurred. In fact, the distinction between those two phases disappears and
is replaced by an iterative process performing them repeatedly.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Problem Identi cation</title>
      <p>
        Even though collaborative process modeling settings are increasingly found in
practice [
        <xref ref-type="bibr" rid="ref19">19, 20</xref>
        ] and results in software engineering have shown that
collaboration can increase quality and e ciency signi cantly [21], the way how process
models are collaboratively created is hardly understood [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ]. Therefore, we want
to extend existing work on the PPM [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], which focuses on single model engineer
settings, toward a collaborative setting where multiple stakeholders (e.g., domain
experts and model engineers) collaboratively create process models. Our work
is closely related to research on collaborative process modeling and the PPM as
detailed in the following. First, we will give an overview of research on
collaborative process modeling, speci cally focusing on factors in uencing its outcome (cf.
Sect. 2.1) and introduce various environments fostering collaborative modeling
(cf. Sect. 2.2). Afterwards, we introduce research on the PPM (cf. Sect. 2.3) and
subsequently on the collaborative PPM (cf. Sect. 4.2).
      </p>
      <sec id="sec-2-1">
        <title>2.1 Research on Factors In uencing the Outcome of Collaborative</title>
      </sec>
      <sec id="sec-2-2">
        <title>Process Modeling</title>
        <p>There has already been some research in the area of collaborative process
modeling investigating the in uence of various factors on the outcome of
collaborative modeling [22, 23]. [22] investigates the impact of end-user involvement and
team composition on perceived model quality and perceived consensus among
the users. Most recently, [23] analyzed how technology capabilities (i.e., ease of
collaboration, ease of modeling, and ease of validation) foster process gains and
subsequently a ect the collaboration outcome (i.e., perceived semantic quality,
perceived usefulness, and satisfaction).</p>
      </sec>
      <sec id="sec-2-3">
        <title>2.2 Research on Collaborative Modeling Environments</title>
        <p>In addition to research on factors in uencing the outcome of collaborative process
modeling, considerable work on collaborative modeling environments fostering
collaboration between stakeholders exists [24{27]. One example of such an
environment is Collaborative Modeling Architecture [24]. The COMA Tool provides
process model collaboration by means of negotiation on proposed models by the
participants. In this collaboration methodology participants are working
asynchronously together. In addition, there exists a collaboration methodology where
participants are working synchronously together on the same model. The
advantage of this approach is the fact that participants are able to track model changes
immediately. Examples are the Signavio Process Editor1 and the Software AG's
ARIS2 collaborative tool where it is possible to work simultaneously together on
one model using a web browser. As another example [25] introduces a 3D BPMN
modeling environment which is integrated into a second life environment. There,
participants are collaboratively modeling using an avatar. An environment
(CoMoMod) for collaborative business process modeling within virtual organizations
is introduced in [26]. CoMoMod allows simultaneously working on one process
model using a variety of di erent modeling languages. Finally, [27] introduces
an infrastructure (CEPE) supporting the building of knowledge about deployed
processes. Therefore, CEPE can be used for process reengineering of existing
processes within organizations.</p>
        <p>These tools and their corresponding research works (cf. Sect. 2.1) focus on the
output of the modeling process rather than the modeling process itself. However,
there exists another stream of research focusing on the creation process itself (cf.
Sect. 2.3).</p>
      </sec>
      <sec id="sec-2-4">
        <title>2.3 Research on the Process of Process Modeling</title>
        <p>
          The importance of the modeling process itself in addition to the actual outcome
is stated in [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ] and has led to an emerging stream of research on the PPM
[
          <xref ref-type="bibr" rid="ref15 ref16">15, 16, 28</xref>
          ]. Research on the PPM focuses on the modeler's interactions with the
modeling environment [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ], i.e., the formalization of a process model as described
in [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ]. During the PPM, modelers are facing the task of creating a syntactically
correct process model re ecting the description of the real world's domain by
interacting with the modeling environment [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ]. The PPM can be described
as a exible, iterative process consisting of the three phases of comprehension,
modeling and reconciliation [
          <xref ref-type="bibr" rid="ref15">15, 28</xref>
          ].
        </p>
        <p>
          Comprehension. According to [29] a problem solver formulates a mental
representation of the problem as a rst step. When creating a process model,
the limitations of working memory prevent modelers from creating a complete
representation in a single step [
          <xref ref-type="bibr" rid="ref15">28, 15</xref>
          ]. Rather, the problem is broken down into
small chunks which are addressed sequentially [
          <xref ref-type="bibr" rid="ref15">28, 15</xref>
          ].
        </p>
        <p>
          Modeling. After formulating a mental representation of the problem, the
modeler utilizes the constructs of the modeling language for creating a formal
process model [
          <xref ref-type="bibr" rid="ref15">28, 15</xref>
          ]. For this purpose, the modeler interacts with the modeling
environment by adding or removing activities, gateways and edges.
        </p>
        <p>Reconciliation. Modelers may reorganize a process model (e.g., renaming of
activities) and utilize its secondary notation (e.g., notation of layout, typographic
cues) to enhance understandability [30].</p>
        <sec id="sec-2-4-1">
          <title>1 http://www.signavio.com/ 2 http://www.softwareag.com/</title>
          <p>Research on the PPM focuses on modeling settings where a single model
engineer creates the process model. However, in order to deal with the complexity of
real life projects various domain experts and model engineers are collaboratively
creating these process models.</p>
        </sec>
      </sec>
      <sec id="sec-2-5">
        <title>2.4 Research on the Collaborative Process of Process Modeling</title>
        <p>
          While we have some insights into the individual processes [
          <xref ref-type="bibr" rid="ref15">15, 28</xref>
          ] within the
PPM, we still lack of detailed insights into the processes additionally involved
when multiple stakeholders are collaboratively creating process models (i.e., the
collaborative process of process modeling (cPPM)). When process models are
created collaboratively, the individual processes (i.e., comprehension, modeling, and
reconciliation) are only one aspect of the problem. In addition, team processes
take place during which teams exchange information, create solution options,
exchange knowledge, evaluate and negotiate alternatives, and assess their own
processes [31]. As a result, the team is building further knowledge and a shared
understanding of the process model [31, 22]. On rst sight these team processes
seem to be more complex than the individual processes and up to now there
has only been little research on those processes. [32] investigates collaborative
modeling settings concentrating on the negotiation phase of this process.
Investigating a closely guided, wizard like conceptualization support is in the focus
of [33, 34]. The team-building processes when creating a model collaboratively
using a proposal based tool (COMA) and allowing face to face communication
are researched in [35] and evaluated using various measures (e.g., number of
proposals per participant, comments per proposal). The practices employed within
a collaborative modeling environment (i.e., ProcessWave3) are observed in [36].
Here, e ectiveness and e ciency are measured using the notation of breakdowns.
        </p>
        <p>As opposed to [32] we want to investigate the team processes involved within
the cPPM on a micro-cognitive level. Moreover, we want to analyze an unguided
model creation process in contrast to [33, 34]. In contrast to [35] our participants
are able to synchronously work on the same process model. Unlike [36], we are
not only interested in observing the di culties participants are facing during the
modeling process, but also the team processes taking place.
3</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Research Question</title>
      <p>The central research question of this thesis is how process models are
collaboratively created. In order to answer this question two sub questions are relevant
and require consideration. RQ1 addresses the question: \How can we collect and
analyze data of the collaborative creation process of process models? " To address
this question an infrastructure capable of collecting and analyzing this data has
to be developed which can subsequently be used to investigate and ultimately
understand the cPPM. RQ2, in turn, is concerned with the analysis of cPPM
using the developed infrastructure and can be stated as follows: \What are the
phases occurring within the cPPM and how do they interact with the individual
ones (i.e., comprehension, modeling, and reconciliation)? " In order to address</p>
      <sec id="sec-3-1">
        <title>3 http://www.processwave.org/</title>
        <p>this question it has to be investigated how teams exchange information, create
solution options, exchange knowledge, evaluate and negotiate alternatives,
assess their own processes [31], and divide workload. In addition, the roles involved
within the cPPM and which actions they perform during the cPPM have to be
analyzed. Moreover, it has to be investigated whether these roles are statically
assigned to the participants during modeling sessions or if these assignments are
subject to change and if yes under which circumstances they occur.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Research Method</title>
      <p>To address the previously stated research questions we follow a mixed method
approach combining design science principles [37] with empirical research (cf.
Fig. 1). On the one hand, to build an infrastructure capable of recording,
measuring and visualizing the cPPM we employ design science principles. The
infrastructure is then used in a subsequent step to conduct modeling sessions and
to investigate the cPPM. For this, exploratory modeling sessions for
hypotheses generation are conducted, which are then tested in con rmatory modeling
sessions. In addition, the platform is iteratively extended and re ned based on
ndings from these modeling sessions. In the following we explain the research
methods that are planned to be used to address RQ1 (cf. Sect 4.1) and RQ2 (cf.
Sect 4.2).</p>
      <sec id="sec-4-1">
        <title>4.1 Collaborative CEP</title>
        <p>We follow the design science approach [37] for building and evaluating our
infrastructure in order to meet our identi ed business needs [38] (i.e., recording and
analyzing the cPPM). Basically, design science methods are guidelines for
building and evaluating novel and innovative artefacts (e.g., tools) during a research
process [38]. In the upcoming section we will introduce our infrastructure.</p>
        <p>Collaborative Cheetah Experimental Platform (cCEP)|an infrastructure for
investigating the cPPM|builds upon Cheetah Experimental Platform (CEP) for
single modeler settings [39]. For this purpose, cCEP provides features
supporting collaboratively creating process models [40]. Beside capturing the cPPM,
investigating the cPPM in a structured manner is essential. Therefore, cCEP
provides visualizations for analyzing the cPPM (e.g., heat maps, active modeler
diagrams) [40]. It is not in our interest to have a fully edged modeling
environment but an environment to investigate the cPPM. An initial version of cCEP
is already in place and can be applied in modeling sessions. Using feedback and
ndings during future modeling sessions we will iteratively re ne and extend
cCEP.</p>
        <p>Collaboration Features. Extensions to the modeling editor of CEP are
necessary to enable users to collaboratively and concurrently edit a business
process model. Therefore, cCEP provides a modeling editor that distributes
the modeling commands to all clients. Meaning, spatially separated participants
are able to see changes made to the process model immediately. Additionally,
spatially distributed participants need a way communicating with each other.
Therefore, we integrate a communication window into cCEP. Using this
communication window participants are able to exchange messages for evaluating and
negotiating alternatives, exchanging knowledge, and assessing their own
processes [31]. After the modeling session ends this window can further be used for
conversation protocol analysis (e.g., using Grounded Theory [41]) by researchers.</p>
        <p>Algorithms. A semiautomatic algorithm for linking messages with the
corresponding model elements is under development, supporting the subsequent
coding of conversation protocols (e.g., using the negotiation patterns [32]). After
linking messages to model elements researchers are able to see by whom, when
and even why elements were created.</p>
        <p>Measures. In [40], we introduced measures for evaluating the cPPM (e.g.,
number of changes per node and number of nodes created per participant). The
measure number of changes per node might indicate model elements that cause
di culties or controversy during the modeling process and number of nodes
created per participant might indicate the participants providing the most domain
knowledge.</p>
        <p>Visualizations. Additionally, cCEP utilizes heat maps illustrating those
measures. Using the heat map illustrating the measure number of changes per
node it is possible to identify the most controversial elements right within the
model.</p>
        <p>Active modeler diagrams are another type of visualizing the cPPM [42]. These
diagrams display changes to the model or messages sent for each participant. For
this, we lter interactions for creating model elements, sending messages, and
laying out model elements and plot them on a time-line using di erent colors for
each participant.</p>
        <p>Beside those visualization techniques, cCEP provides the ability of
replaying the creation process after the modeling process ended. Using this feature
researchers are able to step back and forth within the cPPM.</p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2 Collaborative PPM</title>
        <p>After developing cCEP according to design science principles [37] we are using
cCEP and its analysis techniques (cf. Sect 4.1) for investigating the cPPM. In
order to address RQ2 we apply empirical research methods. More precisely, we
use qualitative research methods followed by quantitative methods.</p>
        <p>During qualitative research we perform exploratory modeling sessions using
cCEP for collecting data. Subsequently, we analyze this data using grounded
theory [41] and derive phases and generate hypotheses describing the cPPM
resulting in an in-depth understanding of the cPPM. More precisely, we want to
investigate how teams exchange information, create solution options, exchange
knowledge, evaluate and negotiate alternatives, assess their own processes [31],
and divide workload. In addition, we want to analyze which roles are involved
within the cPPM, which actions they perform, and under which circumstances
the assignments of these roles are subject to change. Ultimately, we develop a
theory describing the cPPM. This theory will then be tested using
quantitative research methods. In particular, we plan to perform lab experiments for
validating our theory.</p>
        <p>Preliminary results suggest that the cPPM comprises several team
knowledge building phases [31] during which participants try to understand the
requirements to be modeled as well as the model that has been created so far.
Moreover, modelers try to understand the solutions of their companions and try
to convince them of their own ones [32]. After such team knowledge building
phases a modeling and reconciliation phase takes place during which one
participant extends the model (i.e., the driver) and the other one performs layout
changes (i.e., the navigator). Additionally, role changing phases occur during
which the participants switch their roles. Preliminary results give a rst hint,
why these role changing phases occur. When the navigator nds a mistake or
wants additional information being integrated into the model he takes over the
driver role and performs this changes himself. Meanwhile, the participant
normally being the driver becomes the navigator. After an additional negotiation
phase the roles change back into their initial constellation. It is important to
mention that these preliminary results were gained from two modeling sessions
where in each case two modelers were collaboratively creating a process model.
5</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Summary and Outlook</title>
      <p>In this paper a thesis investigating the cPPM is described. Speci cally, the
question how process models are collaboratively created will be answered during this
thesis. Therefore, an infrastructure for recording and analyzing the cPPM will
be developed and subsequently be used to investigate the cPPM. Contribution
of this thesis will be a better understanding of the cPPM.</p>
      <p>So far, an infrastructure for recording and analyzing the cPPM has been
developed. As a next step, exploratory modeling sessions for collecting data will be
conducted. This data will then be analyzed using grounded theory [41]. In
particularly, phases will be derived and hypotheses will be generated ending up in
a theory describing the cPPM. Additionally, cCEP will be iteratively extended
and re ned based on the feedback and ndings during these modeling session.
As a last step, the theory will be validated using further experiments.
Acknowledgements. Particularly, I would like to thank Barbara Weber, the
supervisor of my thesis. Without her support this thesis would not be possible.
Moreover, I would like to thank Jakob Pinggera for discussing my thesis and
providing me with valuable feedback.
20. Mendling, J., Recker, J.C., Wolf, J.: Collaboration features in current bpm tools.</p>
      <p>EMISA Forum 32 (2012) 48{65
21. Williams, L., Kessler, R.R., Cunningham, W., Je ries, R.: Strengthening the Case
for Pair Programming. IEEE Software 17 (2000) 19{25
22. Rittgen, P.: End-user involvement and team factors in business process modeling.</p>
      <p>In: Proc. HICSS '12. (2012) 180{189
23. Recker, J., Mendling, J., Hahn, C.: How collaborative technology supports
cognitive processes in collaborative process modeling: A capabilities-gains-outcome
model. Information Systems (2013)
24. Rittgen, P.: Collaborative business process modeling tool support for solving
typical problems. In: Proc. Conf-IRM '10. (2010)
25. Brown, R.A., Recker, J.C., West, S.: Using virtual worlds for collaborative business
process modeling. Journal of Business Process Management 17 (2011)
26. Dollmann, T., Houy, C., Fettke, P., Loos, P.: Collaborative business process
modeling with comomod - A toolkit for model integration in distributed cooperation
environments. In: Proc. WETICE '11. (2011) 217{222
27. Santoro, F.M., Borges, M.R.S., Pino, J.A.: Cepe: Cooperative editor for processes
elicitation. In: Proc. HICSS '00. (2000)
28. So er, P., Kaner, M., Wand, Y.: Towards understanding the process of process
modeling: Theoretical and empirical considerations. In: Business Process
Management Workshops, Springer (2011) 357{369
29. Newell, A., Simon, H.: Human problem Solving. Prentice Hall (1972)
30. Petre, M.: Why Looking Isn't Always Seeing: Readership Skills and Graphical</p>
      <p>Programming. Commun. ACM (1995) 33{44
31. Fiore, S.M., Smith-Jentsch, K.A., Salas, E., Warner, N., Letsky, M.: Towards
an understanding of macrocognition in teams: developing and de ning complex
collaborative processes and products. Theoretical Issues in Ergonomics Science 11
(2010) 250{271
32. Rittgen, P.: Negotiating Models. In: Proc. CAiSE '07. (2007) 561{573
33. Hoppenbrouwers, S., van Stokkum, W.: Towards combining thinklets and dialogue
games in collaborative modeling : an explorative case. In: Proc. ECSCW '11. (2011)
11{18
34. Hoppenbrouwers, S., Weigand, H., Rouwette, E.A.J.A.: Setting rules of play for
collaborative modeling. IJeC 5 (2009) 37{52
35. Rittgen, P.: The role of editor in collaborative modeling. In: Proc. SAC '12. (2012)
1674{1679
36. Hahn, C., Recker, J., Mendling, J.: An exploratory study of it-enabled collaborative
process modeling. In: Proc. BPM Workshops '10. Volume 66. (2010) 61{72
37. Hevner, A., Chatterjee, S.: Design Research in Information Systems: Theory and</p>
      <p>Practice. Springer (2010)
38. Recker, J.: Scienti c Research in Information Systems. Progress in IS. Springer
(2012)
39. Pinggera, J., Zugal, S., Weber, B.: Investigating the process of process modeling
with cheetah experimental platform. In: Proc. ER-POIS'10. (2010) 13{18
40. Forster, S., Pinggera, J., Weber, B.: Collaborative Business Process Modeling. In:</p>
      <p>Proc. EMISA '12. (2012) 81{94
41. Urquhart, C., Lehmann, H., Myers, M.D.: Putting the theory back into grounded
theory: guidelines for grounded theory studies in information systems. Information
Systems Journal 20 (2010) 357{381
42. Forster, S., Pinggera, J., Weber, B.: Toward an Understanding of the Collaborative
Process of Process Modeling. In: Proc. CAISE '13. (2013) (accepted)</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Indulska</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Recker</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosemann</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Green</surname>
            ,
            <given-names>P.F.</given-names>
          </string-name>
          :
          <article-title>Business process modeling: Current issues and future challenges</article-title>
          .
          <source>In: Proc. CAiSE</source>
          . (
          <year>2009</year>
          )
          <volume>501</volume>
          {
          <fpage>514</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Becker</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosemann</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Uthmann</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Guidelines of business process modeling</article-title>
          .
          <source>In: Business Process Management, Models, Techniques, and Empirical Studies</source>
          , London, UK, Springer-Verlag (
          <year>2000</year>
          )
          <volume>30</volume>
          {
          <fpage>49</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Mukherjee</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dhoolia</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sinha</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rembert</surname>
            ,
            <given-names>A.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nanda</surname>
            ,
            <given-names>M.G.</given-names>
          </string-name>
          :
          <article-title>From informal process diagrams to formal process models</article-title>
          .
          <source>In: Proc. BPM '10</source>
          ,
          <string-name>
            <surname>Springer</surname>
          </string-name>
          (
          <year>2010</year>
          )
          <volume>145</volume>
          {
          <fpage>161</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Rittgen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Quality and perceived usefulness of process models</article-title>
          .
          <source>In: Proc. SAC '10</source>
          . (
          <year>2010</year>
          )
          <volume>65</volume>
          {
          <fpage>72</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Scheer</surname>
            ,
            <given-names>A.W.</given-names>
          </string-name>
          : ARIS - Business Process Modeling. Springer (
          <year>2000</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Krogstie</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sindre</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jorgensen</surname>
          </string-name>
          , H.:
          <article-title>Process models representing knowledge for action: a revised quality framework</article-title>
          .
          <source>EJIS</source>
          <volume>15</volume>
          (
          <year>2006</year>
          )
          <volume>91</volume>
          {
          <fpage>102</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Rittgen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Collaborative modeling of business processes: a comparative case study</article-title>
          .
          <source>In: Proc. SAC '09</source>
          . (
          <year>2009</year>
          )
          <volume>225</volume>
          {
          <fpage>230</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Mendling</surname>
          </string-name>
          , J.:
          <article-title>Metrics for Process Models: Empirical Foundations of Veri cation, Error Prediction and Guidelines for Correctness</article-title>
          . Springer (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Weber</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Refactoring Process Models in Large Process Repositories</article-title>
          .
          <source>In: Proc. CAiSE '08</source>
          . (
          <year>2008</year>
          )
          <volume>124</volume>
          {
          <fpage>139</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <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>Recker</surname>
          </string-name>
          , J.:
          <article-title>Activity Labeling in Process Modeling: Empirical Insights and Recommendations</article-title>
          .
          <source>Information Systems</source>
          <volume>35</volume>
          (
          <year>2010</year>
          )
          <volume>467</volume>
          {
          <fpage>482</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Hallerbach</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bauer</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Capturing Variability in Business Process Models: The Provop Approach</article-title>
          .
          <source>Journal of Software Maintenance</source>
          <volume>22</volume>
          (
          <year>2010</year>
          )
          <volume>519</volume>
          {
          <fpage>546</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Soto</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ocampo</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          , Munch, J.:
          <article-title>The secret life of a process description: A look into the evolution of a large process model</article-title>
          .
          <source>In: Proc. ICSP '08</source>
          . (
          <year>2008</year>
          )
          <volume>257</volume>
          {
          <fpage>268</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Aalst</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hofstede</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Veri cation of work ow task structures: A petri-net-based approach</article-title>
          .
          <source>Information Systems</source>
          <volume>25</volume>
          (
          <year>2000</year>
          )
          <volume>43</volume>
          {
          <fpage>69</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <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: Proc. BIS '06</source>
          . (
          <year>2006</year>
          )
          <volume>1</volume>
          {
          <fpage>12</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Pinggera</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zugal</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weidlich</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fahland</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weber</surname>
            ,
            <given-names>B.</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>
          :
          <article-title>Tracing the Process of Process Modeling with Modeling Phase Diagrams</article-title>
          .
          <source>In: Proc. ER-BPM '11</source>
          . (
          <year>2012</year>
          )
          <volume>370</volume>
          {
          <fpage>382</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Pinggera</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , So er, P.,
          <string-name>
            <surname>Zugal</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weber</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weidlich</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fahland</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reijers</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mendling</surname>
          </string-name>
          , J.:
          <article-title>Modeling Styles in Business Process Modeling</article-title>
          .
          <source>In: Proc. BPMDS '12</source>
          . (
          <year>2012</year>
          )
          <volume>151</volume>
          {
          <fpage>166</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Hoppenbrouwers</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Proper</surname>
          </string-name>
          , H., van der Weide, T.:
          <article-title>A Fundamental View on the Process of Conceptual Modeling</article-title>
          .
          <source>In: Proc. ER '05</source>
          . (
          <year>2005</year>
          )
          <volume>128</volume>
          {
          <fpage>143</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Renger</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kolfschoten</surname>
            ,
            <given-names>G.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>de Vreede</surname>
          </string-name>
          , G.J.:
          <article-title>Using interactive whiteboard technology to support collaborative modeling</article-title>
          .
          <source>In: Proc. CRIWG '08</source>
          . (
          <year>2008</year>
          )
          <volume>356</volume>
          {
          <fpage>363</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Rittgen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Collaborative Modeling { A Design Science Approach</article-title>
          .
          <source>In: Proc. HICSS '09</source>
          . (
          <year>2009</year>
          )
          <volume>1</volume>
          {
          <fpage>10</fpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>