<!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>Checking Business Process Modeling Guidelines in Apromore</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Fabrizio Fornari</string-name>
          <email>fabrizio.fornari@unicam.it</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Stefania Gnesi</string-name>
          <email>stefania.gnesi@isti.cnr.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Marcello La Rosa</string-name>
          <email>m.larosa@qut.edu.au</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andrea Polini</string-name>
          <email>andrea.polini@unicam.it</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Barbara Re</string-name>
          <email>barbara.re@unicam.it</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Giorgio O. Spagnolo</string-name>
          <email>giorgio.oronzo.spagnolo@isti.cnr.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>ISTI-CNR of Pisa</institution>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Queensland University of Technology</institution>
          ,
          <country country="AU">Australia</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Univeristy of Camerino</institution>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>We present the integration of BEBoP - understandaBility vErifier for Business Process models, into the Apromore open-source process analytics platform. Given a BPMN model the tool allows one to verify which understandability modeling guidelines such as layout conventions are violated by the model. Such guidelines are rules that a model designer should follow to guarantee that the designed model is easy to understand by relevant stakeholders. Given the variety of stakeholders that need to interpret these models, and considering the pivotal function that process models play within organizations, understandability becomes a fundamental quality requirement that needs to be taken into account by designers. The tool provides model designers with textual and graphical representations of which understandaiblity guidelines are violated. Designers can then decide to repair models in such a way to guarantee a higher degree of understandability.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        The literature shows that business process modeling has been identified as an important
phase in BPM [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], and the benefits of its use in practice are well recognized [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. At the
same time the quality of models resulting from the modeling phase is critical for the
success of an organization [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. In particular, the designed models must fit with the
reality, and they must be considered understandable by all the stakeholders interested in the
information they convey. Many contributions can be found in the literature which
propose modeling guidelines to guarantee model understandability. However those
guidelines are scattered among many different works [
        <xref ref-type="bibr" rid="ref10 ref11 ref5">5, 10, 11</xref>
        ], which in general do not use
a homogeneous template to describe them [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. In [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] the authors tried to overcome those
issues by collecting understandability guidelines for modeling business processes from
the literature, synthesizing and presenting them in a homogeneous format; for each
guideline they provide a template including the following fields: an ID and a Name to
uniquely identify the guideline, a Description to provide an explanation of the
guideline, References to report the original guidelines source allowing the users to access
additional materials about the guideline itself, Metrics and Thresholds to assess the
adherence of a model to a guideline, an Example to graphically display the application
of the guideline to a practical scenario, and to highlight the differences between good
and bad modeling practices. The result is a list of 50 guidelines [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] which have been
organized into categories. General includes guidelines that impact on different aspects
of the overall BPMN modeling practice. Notation includes guidelines on the usage of
the BPMN syntax. Labeling includes guidelines for the assignment of proper labels to
BPMN elements. Patterns includes guidelines that suggest a specific arrangement of
BPMN elements. Appearance includes guidelines for a clear presentation of the BP
model. In order to validate these guidelines the authors submitted a questionnaire to the
Public Administrations and the Academic contexts targeting employees, students,
researchers, professors and managers. From the obtained answers they wanted to deduct
if the guidelines were perceived being useful and if models designed following the
guidelines would be perceived as more understandable.
      </p>
      <p>
        Although commercial tools are available that check a considerable number of
guidelines, no open source tool existed for this task. The authors of [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] proceeded with their
work developing an open-source tool called BEBoP4 to automatically verify
understandabilty modeling guidelines over BPMN models. This enables BPMN models
designers to obtain feedback on the level of understandability of their designed models.
BEBoP5 has been developed in the context of the European project Learn PAd6 and
allows the automatic checking of understandability guidelines over BPMN models.
BEBoP is developed as a Web service, and its graphical user interface can be accessed
by users through any Web browser.7 The service can be accessed by other software
through its RESTful interface, and the tool can be integrated as a plug-in into other
existing tools, and extended if required. The tool takes as input a BPMN model and
allows one to automatically verify 34 of the 50 guidelines over the selected model; these
34 guidelines are the ones that have an associated metric and thresholds, or refer to the
presence/absence of BPMN elements and their associated labels. For each guideline,
the tool implements an algorithm for its check.
      </p>
      <p>
        Several commercial tools exist to verify quality aspects of BP models. Among such
tools, we have Signavio 10.1,8 No Magic MagicDraw 18,9 Bizagi Process Modeler 3.010
and Camunda Community Edition.11 All these tools provide business process model
editing capabilities besides the ability to check understandability guidelines. With
respect to the 50 guidelines identified in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], BEBoP allows one to automatically verify
34 guidelines, Signavio 22, MagicDraw 8, Bizagi 7, and Camunda 5.
      </p>
      <p>Our tool has been tested over the European Project Budget Reporting scenario
(EPBR), which was a case study for Learn PAd. EPBR refers to a set of processes
4 BEBoP source code: https://goo.gl/zrd6z9
5 BEBoP has been developed by the CNR Institute of Pisa in collaboration with the University
of Camerino
6 Learn PAd website: http://www.learnpad.eu/
7 BEBoP web service interface: https://goo.gl/8XEi6s
8 http://www.signavio.com/products/process-editor/
9 http://www.nomagic.com/products/cameo-business-modeler.html
10 http://www.bizagi.com/en/products/bpm-suite/modeler
11 https://camunda.org/download/modeler/
performed by public administrations that received a research grant from the European
Union.</p>
      <p>
        One tool for managing business processes that has been developed in the BPM
community, and that is under a constant growth, is Apromore12 [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Apromore is the result
of over seven years of ongoing development and is currently in version 5.0. The
platform is implemented via a service-oriented architecture and deployed as a Software as
a Service. The technologies used in Apromore combine Spring as the Java
development framework, Maven as the dependency manager, OSGi as the plugin architecture,
EclipseVirgo as the OSGi-based application server, and ZK as the AJAX front end. The
chosen technologies allow Apromore to be an extensible framework, where new plugins
can be easily added to an ecosystem of advanced business process analytics capabilities.
Since the utility of having guidelines for modeling understandable business processes
is confirmed by the literature [
        <xref ref-type="bibr" rid="ref1 ref9">1, 9</xref>
        ] we decided to introduce this functionality into the
Apromore repository by an integration with the BEBoP web service.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>BEBoP - Apromore integration</title>
      <p>The BEBoP tool has been integrated into Apromore in the form of a plugin for “Portal”
and another for the “Editor” environment. The Apromore Portal provides users with
a way to navigate the model repository, having a general view over the stored models.
Regarding our plugin, from the portal environment one can select a BPMN model in the
.bpmn format from Apromore’s repository and ask for a check of the
understandability modeling guidelines calling the related plugin from the “BEBoP-Guidelines Check”
item under the dropdown menu named “Analyze” as shown on the left-hand side of Fig.
1. Once the user has requested the guidelines check, an additional tab in the portal is
displayed reporting a list of the violated guidelines with name and description as shown
on the right-hand side of Fig.1. This view allows the user to have just an overview of
which guidelines are violated. For a better understanding of which are the involved
elements that do not meet the guidelines, the user is asked to open the model accessing the
Editor environment. The Apromore Editor allows users to create models and regarding
our plugin, from the Editor model designers can ask for a check of the
understandability modeling guidelines over the model they are designing. The user is prompted with
a window listing the violated guidelines and the BPMN elements that violate them, as
shown in Fig.2. From the figure we can notice that one element of type “Task” violates
the “Activity Description” guideline which suggests designers to provide a description
for each activity in the model. The window displayed to the user consists of two parts:
the left part “Guidelines Violated” containing a grid with all the information about the
BPMN elements violating the guidelines, and the right part “Guideline Description”
displaying which guideline has been violated by which BPMN element. While the left
part content is static, basically presenting the information about BPMN elements with:
label, type and id of the element; the content on the right part dynamically changes
based on which element of the grid the user selects. In this way, the name of the
guideline, violated by the selected element, and its description, are displayed to the user as
12 Apromore website: www.apromore.org
shown in Fig. 2. At the same time, when an element is selected from the grid, it is also
highlighted, using the red color, in the actual graphical representation of the model. This
allows a faster recognition of the BPMN element violating the guideline and leaves to
the user the possibility to correct the guideline violation.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Screencast and Links</title>
      <p>A screencast is available at https://youtu.be/8LToEahCf2Q. This video
illustrates a typical scenario where the user requires to check a BPMN model against the
understandability guidelines. The BEBoP integration is embedded as a set of OSGi
plugins into the online process analytics platform Apromore, which has been used for the
screencast (http://apromore.org).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Becker</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosemann</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Von Uthmann</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Guidelines of business process modeling</article-title>
          .
          <source>In Business Process Management</source>
          (pp.
          <fpage>30</fpage>
          -
          <lpage>49</lpage>
          ). Springer Berlin Heidelberg (
          <year>2000</year>
          )
        </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.</given-names>
          </string-name>
          :
          <article-title>Quality assessment strategy: Applying business process understandability guidelines for learning</article-title>
          .
          <source>Tech. Rep. 4</source>
          .1,
          <string-name>
            <surname>ISTI-CNR</surname>
          </string-name>
          , University of Camerino, Italy, URL http://puma.isti.cnr.it/linkdoc.php?idauth=1&amp;idcol=1&amp;
          <string-name>
            <surname>icode=</surname>
          </string-name>
          2015-TR-
          <volume>034</volume>
          &amp;
          <article-title>authority=cnr.isti&amp;collection=cnr.isti&amp;langver=it (</article-title>
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Indulska</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Green</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Recker</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Rosemann</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Business process modeling: Perceived benefits</article-title>
          .
          <source>In International Conference on Conceptual Modeling</source>
          (pp.
          <fpage>458</fpage>
          -
          <lpage>471</lpage>
          ). Springer Berlin Heidelberg (
          <year>2009</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>La</given-names>
            <surname>Rosa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Reijers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. A.</given-names>
            ,
            <surname>Van Der Aalst</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W. M.</given-names>
            ,
            <surname>Dijkman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R. M.</given-names>
            ,
            <surname>Mendling</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Dumas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            , &amp;
            <surname>GarcA-BaUelos</surname>
          </string-name>
          , L.:
          <article-title>APROMORE: An advanced process model repository</article-title>
          .
          <source>Expert Systems with Applications</source>
          ,
          <volume>38</volume>
          (
          <issue>6</issue>
          ),
          <fpage>7029</fpage>
          -
          <lpage>7040</lpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <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>
          , &amp;
          <string-name>
            <surname>van der Aalst</surname>
          </string-name>
          , W. M.:
          <article-title>Seven process modeling guidelines (7PMG)</article-title>
          .
          <source>Information and Software Technology</source>
          ,
          <volume>52</volume>
          (
          <issue>2</issue>
          ),
          <fpage>127</fpage>
          -
          <lpage>136</lpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Moreno-Montes de Oca</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Snoeck</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Pragmatic guidelines for business process modeling (</article-title>
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7. de Oca,
          <string-name>
            <given-names>I. M. M.</given-names>
            ,
            <surname>Snoeck</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Reijers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. A.</given-names>
            , &amp;
            <surname>Rodrguez-Morffi</surname>
          </string-name>
          ,
          <string-name>
            <surname>A.</surname>
          </string-name>
          :
          <article-title>A systematic literature review of studies on business process modeling quality</article-title>
          .
          <source>Information and Software Technology</source>
          ,
          <volume>58</volume>
          ,
          <fpage>187</fpage>
          -
          <lpage>205</lpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Kalpic</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Bernus</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Business process modelling in industrythe powerful tool in enterprise management</article-title>
          . Computers in industry,
          <volume>47</volume>
          (
          <issue>3</issue>
          ),
          <fpage>299</fpage>
          -
          <lpage>318</lpage>
          (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Schuette</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Rotthowe</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>The guidelines of modelingan approach to enhance the quality in information models</article-title>
          .
          <source>In International Conference on Conceptual Modeling</source>
          (pp.
          <fpage>240</fpage>
          -
          <lpage>254</lpage>
          ). Springer Berlin Heidelberg (
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>White</surname>
            ,
            <given-names>S. A.</given-names>
          </string-name>
          :
          <article-title>BPMN modeling and reference guide: understanding and using BPMN. Future Strategies Inc</article-title>
          . (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Silver</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>BPMN Method and Style, with BPMN Implementers Guide: A structured approach for business process modeling and implementation using BPMN 2.0</article-title>
          .
          <string-name>
            <surname>Cody-Cassidy</surname>
            <given-names>Press</given-names>
          </string-name>
          , Aptos, CA,
          <volume>450</volume>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>