<!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>[εm] - Process Analysis using a Meta Modeling Tool</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Dennis M. Riehle</string-name>
          <email>riehle@ercis.uni-muenster.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Steffen Höhenberger</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jens Brunk</string-name>
          <email>brunk@ercis.uni-muenster.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Patrick Delfmann</string-name>
          <email>delfmann@uni-koblenz.de</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jörg Becker</string-name>
          <email>becker@ercis.uni-muenster.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>ERCIS, University of Münster</institution>
          ,
          <addr-line>Münster</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>University of Koblenz-Landau</institution>
          ,
          <addr-line>Koblenz</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Increasing complexity in business processes and the resulting missing manageability are one of the main issues in business process management today. Process owners do not only have to keep track of one aspect of a process (e.g. the correct input and output, the efficiency or the compliance) but of combinations of these. In turn, these aspects are influenced by several possible factors throughout the whole process. Often occurring adjustments and fast changing regulations raise the complexity of monitoring even more. As the manual analysis becomes more and more infeasible, automatic analysis tools are required that support responsible persons in this task. Here, our meta modeling tool [εm] comes into play. For analysis, [εm] enables the user to define specific patterns that describe issues to be detected in business process models. [εm] can search these issues automatically by means of an included algorithm and present the detected parts. Currently existing tools often lack a wide applicability (i.e. only support one modeling language), only allow rather simple patterns or are too difficult to use. The demo presents the flexible applicability of the tool and how it can be used by modeling experts as well as domain experts to benefit from its wide-ranging functionality. Based on a continuous example, the support of arbitrary modeling languages, the creation of complex patterns by using the graphical user interface, and the search of these patterns in business process models are presented.</p>
      </abstract>
      <kwd-group>
        <kwd>Meta Modeling</kwd>
        <kwd>Process Analysis</kwd>
        <kwd>Compliance Checking</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        BPM and the Need of Tool Support
Business processes have indisputably risen from a side issue in companies to one of the
key factors for a company’s success, and the function perspective (“work in silos”) gets
more and more deprecated [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. However, business processes are not self-propelling.
Long-term efficiency and cost savings based on the process perspective are not raising
out of nowhere. Quite the contrary: the appropriate management of business processes
is the key to gain money in the long run and entails certain effort. Business process
management (BPM) is not only the one-time documentation of real processes in a
company. BPM includes the “design, enactment, management, and analysis of operational
business processes” [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. However, the increasing complexity of companies inevitably
leads to a higher amount of more complex business processes. In turn, companies can
only generate value from their business processes, if the business process management
is qualified to handle this constantly raising effort. Besides the process documentation,
in particular the analysis and governance of business processes gains complexity [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>
        The approaches and tools that aim to enable and support the business process
management in companies, as well as their application areas, are manifold. While tools for
the modeling of business processes are widely available, the analysis segment is not so
abundantly equipped. The tools that are equipped with an automated analysis support
for business process models are often not flexible enough [
        <xref ref-type="bibr" rid="ref4 ref5">4, 5</xref>
        ]. While Business
Process Model and Notation (BPMN) is the de facto standard for process modeling today,
the reality is quite more diverse. The landscape of existing modeling languages is large
and the applied language or language type often differs within companies (e.g., the
usage of BPMN elements may even differ from modeler to modeler). Furthermore, most
of the tools only detect very simple issues [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. They enable the user to detect simple
structures, such as predecessors or successors, splits and joins, or a label of a process
step. But when it comes to longer paths, different labels and forbidden nodes, most tools
do not live up to the challenge. Another important aspect for the practical applicability
is the usability of these tools. Most of them require a certain knowledge of complex and
mainly textual modeling notations [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
      <p>Thus, our tool tries to address these issues to provide support for real-world business
process management, not only for modeling experts but also for domain experts.
2</p>
      <p>
        [εm] in Detail
[εm] has been developed over years according to the Design Science methodology of
Peffers et al. [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Still, this is the first comprehensive presentation of the tool in
academia, showing the whole workflow from meta modeling to process analysis. The
initially mentioned problem of the growing complexity of business processes in
combination with more and more aspects to prove, gave birth to the idea of [εm]. To not build
“just another modeling tool”, the wide applicability, the support of complex and
flexible patterns as well as the ease of use has been a focus during the development.
      </p>
      <p>
        [εm] exploits the advantages of meta modeling [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. Due to this fact, all constructs in
our tool follow a predefined “construction manual” that strictly constitutes, what is
possible to model, and what is not. The clue: this construction manual can be freely defined
by any user. This enables the user to use an arbitrary modeling language for creating
process models. There are predefined common languages available, but one can also
create new ones.
      </p>
      <p>Once a modeling language is defined, not only models but also so-called patterns
can be created. Patterns represent (real-world) issues, consisting of nodes and edges
that are to be detected in the process models. For that, a powerful graphical pattern
editor is integrated, which provides the user with a multitude of possibilities on how to
represent the desired issue by a pattern. For both, the nodes and the edges, the editor
provides a lot of adjustment options. The most important options for nodes are captions
(to search particular terms like print or invoice in process models) and the typing (to
search only for events, tasks etc.). A node can have an arbitrary number of captions and
types. It is also possible to define one pattern for more than one language. In that case,
one would have to choose multiple languages (e.g., BPMN and the Event-driven
Process Chain (EPC)), and select types of both languages (i.e., task and function) for a
node. Nodes can also be set as forbidden, so that such a node must not exist within a
process model. The most important options for edges are the direction and the
“extension” of an edge to a path. While an edge only connects two adjacent nodes, a path
denotes that several other nodes may be located in-between the two previously specified
ones. Additionally, the path can be further particularized with several options (such as
forbidding specific element like events on it). A main option here is the pattern on path
setting. It enables the user to require or forbid other complete patterns that have been
created within [εm]. More complex considerations such as calculations (Are incoming
probabilities 100 % in sum?) or comparisons (Is a document used twice within a
process?) are supported by global rules.</p>
      <p>
        For the analysis of the process models (by means of detecting the constructed
patterns), [εm] makes use of graph theory. Eventually, an implemented graph matching
algorithm can detect the patterns within the process models [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>In summary, [εm] aims to address the mentioned problems, by combining the
constructs of meta modeling and graph theory. The tool itself and its documentation are
freely available on the internet.1
3</p>
      <p>[εm] in Use – Currently and in the Future
The development is a lively and ongoing process and design improvements are made
continuously. The prototype has been used and evaluated in research projects and was
part of several publications.</p>
      <p>The usual procedure of analyzing process models comprises the language definition,
the process model creation (or import), the pattern creation (or import) and, eventually,
the search of patterns within the models. This procedure is exemplary shown in our
20minute screencast describing the tool, which accompanies this paper.2</p>
      <p>
        Due to its flexibility and its wide application possibilities, [εm] was used in several
use cases in research projects and is subject to several publications. For business
process improvement, it was used in a study to create over 100 patterns denoting
improvement potential for business processes and to analyze process models of companies of
different domains (retail, supply, consulting and logistics) with over 8000 single nodes.
The results of the study are partly shown by Delfmann and Höhenberger [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
      </p>
      <p>
        Another use case is compliance checking. Within a study with a bank service
provider, Becker et al. identified 49 potential compliance violations in its process models
by analyzing a process model landscape consisting of over 21000 single nodes [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
      </p>
      <p>
        Another, completely different domain is form checking. In an experiment,
Höhenberger and Scholta transformed governmental forms into a specially developed
language in [εm] and searched for inconsistencies and legislation violations described by
patterns [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
1 See http://em.uni-muenster.de/ for software downloads and user guide
2 Screencast available from http://em.uni-muenster.de/videos/
Currently, we are transforming an unstructured process landscape of an association for
working safety into the model structures of [εm]. Within this project we also define
potential weaknesses with experts and continuously analyze the process models.
Automatic continuous analysis will enable organizations to prove they meet compliance
regulations at any time.
      </p>
      <p>In the near future, we will provide a freely accessible catalog of the developed
process weakness patterns of the first study, as well as a catalog of the compliance patterns
used in the second study. Furthermore, import modules for further standardized
modeling languages, such as BPMN or EPC in its different types, are planned.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Weske</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <string-name>
            <surname>Business Process Management - Concepts</surname>
          </string-name>
          , Languages, Architectures. Springer, Berlin/Heidelberg, Germany (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>ter Hofstede</surname>
            ,
            <given-names>A.H.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weske</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Business Process Management: A Survey</article-title>
          .
          <source>In: Business Process Management</source>
          . pp.
          <fpage>1</fpage>
          -
          <lpage>12</lpage>
          . Springer, Berlin/Heidelberg, Germany (
          <year>2003</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Rinderle-Ma</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ly</surname>
            ,
            <given-names>L.T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dadam</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Business Process Compliance (Aktuelles Schlagwort)</article-title>
          .
          <source>In: Proceedings of the EMISA</source>
          <year>2008</year>
          . Sankt Augustin,
          <string-name>
            <surname>Germany</surname>
          </string-name>
          (
          <year>2008</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Rosemann</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vessey</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          :
          <article-title>Toward Improving the Relevance of Information Systems Research to Practice: The Role of Applicability Checks</article-title>
          .
          <source>MIS Q</source>
          .
          <volume>31</volume>
          ,
          <fpage>1</fpage>
          -
          <lpage>22</lpage>
          (
          <year>2008</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Becker</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Delfmann</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Eggert</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schwittay</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Generalizability and Applicability of Model-Based Business Process Compliance-Checking Approaches - A State-of-the-</article-title>
          <source>Art Analysis and Research Roadmap. BuR - Bus. Res</source>
          .
          <volume>5</volume>
          ,
          <fpage>221</fpage>
          -
          <lpage>247</lpage>
          (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Höhenberger</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Riehle</surname>
            ,
            <given-names>D.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Delfmann</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>From Legislation to Potential Compliance Violations in Business Processes - Simplicity Matters</article-title>
          .
          <source>In: Proceedings of the 24th European Conference on Information Systems (ECIS)</source>
          . Istanbul, Turkey (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Peffers</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tuunanen</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rothenberger</surname>
            ,
            <given-names>M.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chatterjee</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <source>A Design Science Research Methodology for Information Systems Research. J. Manag. Inf. Syst</source>
          .
          <volume>24</volume>
          ,
          <fpage>45</fpage>
          -
          <lpage>77</lpage>
          (
          <year>2007</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Strahringer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Metamodellierung als Instrument des Methodenvergleichs - Eine Evaluierung am Beispiel objektorientierter Analysemethoden</article-title>
          . Shaker, Herzogenrath, Germany (
          <year>1996</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Delfmann</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Breuker</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Matzner</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Becker</surname>
            ,
            <given-names>J.: Supporting</given-names>
          </string-name>
          <string-name>
            <surname>Information Systems Analysis Through Conceptual Model Query - The Diagramed Model Query Language (DMQL). Commun</surname>
          </string-name>
          . Assoc. Inf. Syst.
          <volume>37</volume>
          ,
          <fpage>473</fpage>
          -
          <lpage>509</lpage>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Delfmann</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Höhenberger</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Supporting Business Process Improvement through Business Process Weakness Pattern Collections</article-title>
          .
          <source>In: Proceedings of the WI</source>
          <year>2015</year>
          , pp.
          <fpage>378</fpage>
          -
          <lpage>392</lpage>
          . Osnabrück,
          <string-name>
            <surname>Germany</surname>
          </string-name>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Becker</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bergener</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Delfmann</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Burkhard</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Modeling and Checking Business Process Compliance Rules in the Financial Sector</article-title>
          .
          <source>In: ICIS 2011 Proceedings</source>
          , pp.
          <fpage>2291</fpage>
          -
          <lpage>2310</lpage>
          . Shanghai, China (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Höhenberger</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Scholta</surname>
          </string-name>
          , H.:
          <article-title>Will Government Forms Ever be Consistent? Detecting Violations in Form Structures by Utilizing Graph Theory</article-title>
          .
          <source>In: Proceedings of the ECIS</source>
          <year>2017</year>
          . Guimarães,
          <string-name>
            <surname>Portugal</surname>
          </string-name>
          (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>