<!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>Towards the Generalized Criterion for Evaluation of Business Process Model Quality</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>National Technical University “KhPI”</institution>
          ,
          <addr-line>Kyrpychova str. 2, 61002 Kharkiv</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
      </contrib-group>
      <fpage>0000</fpage>
      <lpage>0002</lpage>
      <abstract>
        <p>Business process management has become the most widely-used and reliable approach to organizational management over the last decades. It is also considered as a part of quality management system in an organization. Business process modeling is the core of business process management, which is used for visualization, analysis, and improvement of organizational activities. Moreover, business process modeling plays an important role in the context of business process management maturity of an overall enterprise. Therefore, this paper is focused on the problem of business process model quality evaluation. Existing approaches based on the process modeling guidelines, measures and corresponding thresholds are reviewed, as well as the refined process modeling rules, corresponding quality criteria, the generalized quality criterion, and thresholds for its translation into linguistic values are proposed. The data model and software prototype are developed and the validation results are outlined.</p>
      </abstract>
      <kwd-group>
        <kwd>Business Process Management</kwd>
        <kwd>Business Process Model</kwd>
        <kwd>Process Model Quality</kwd>
        <kwd>Process Model Metric</kwd>
        <kwd>Quality Criteria</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Business process modeling is considered as a key tool of Business Process
Management (BPM). In paper [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] BPM is considered as both art and science of monitoring
organizational activities in order to provide quality of produced products or services
and find ways to improve these activities. According to Dumas et. al. [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], BPM is
about managing entire chains of events, activities and decisions that ultimately add
value to the organization and its customers. Whereas, business processes are
considered as “chains of events, activities and decisions” that seems quite understandable
and clear [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. The BPM lifecycle itself starts with the modeling stage. More formally
BPM is considered as the managerial discipline that uses the technologies for the
process oriented management [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. According to paper [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], a high-level overview of
the BPM lifecycle includes the four key activities: model (create a business process
model to be used for analysis or enactment), enact (use a process model to control and
support concrete cases), analyze (analyze a process using a process model and/or
event log), and manage (all other activities, e.g., adjusting the process, reallocating
resources, or managing large collections of related process models). Business process
models are mostly used in the design and analysis of information systems and are
Copyright © 2020 for this paper by its authors. Use permitted under Creative Commons License Attribution 4.0 International (CC BY 4.0).
considered as a good mechanism for communication among the stakeholders [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>
        Therefore, it is important to ensure high quality of created business process models. A
business process model of poor quality can disturb business process implementation
and execution, as well as its performance [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. While a high-quality model is expected
to be accepted by stakeholders and thus prevents problems of business process
implementation, deployment, execution, and continuous improvement [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
      <p>
        Business process modeling is an essential part of understanding and improving the
activities that an enterprise uses to achieve its business goals, however there was no
generally accepted framework of process model quality [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. To the best knowledge of
the authors there is still no such quality framework nowadays. Therefore, this paper
proposes evaluation criteria of business process model quality, which are based on
existing best practices and guidelines together with measures and their corresponding
thresholds. The objective of such criteria is to calculate a numerical degree to which a
business process model fulfills requirements of process modeling guidelines. This
definition of business process model quality is derived from ISO 9001’s definition of
quality “degree to which a set of inherent characteristics fulfills requirements” [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
      </p>
      <p>
        Nowadays the Business Process Model and Notation (BPMN) is the leading
standard for modeling business processes. It is provided by the Object Management Group
(OMG) and it is used by business professionals as a standard notation allowing not
only internal communication of the business procedures, but business-IT alignment
and collaboration between business partners as well [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. According to the latest
survey in the domain of business process modeling [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], BPMN diagrams are used by
64% of respondents. After the BPMN 2.0 notation came up, and original name
“Business Process Modeling Notation” was changed to “Business Process Model and
Notation”, the graphic notation had been extended with the metamodel, the XML-based
(eXtensible Markup Language) exchange file format, and the execution semantics.
      </p>
      <p>
        Section 2 and its subsections describe related work in the field of business process
quality management, BPM maturity models, and business process model quality
evaluation. Business process modeling guidelines, corresponding measures, derived
criteria of business process model quality, the generalized quality criterion and its
threshold values are outlined in section 3. Section 4 describes how business information,
which BPMN business process models communicate, might be processed for their
further querying and reuse according to an ontology for organizing enterprise
architectural artifacts (to which process models belongs) defined by the Zachman
Framework [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. This section also describes the developed software prototype used to
validate the quality criteria proposed in section 3. Discussion of the obtained results is
outlined, as well as conclusion and future work is formulated.
      </p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <sec id="sec-2-1">
        <title>Business Process Quality Management and Maturity Models</title>
        <p>
          According to Tobias and Kern [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ], BPM has its roots in Total Quality Management
(TQM) appeared in late 1980s and in Business Process Reengineering (BPR)
introduced in early 1990s by Hammer, Champy, and Davenport. One of BPM meanings is
related to a four-step Plan-Do-Check-Act (PDCA) quality management cycle by
Deming and Shewhart [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. PDCA is a continuous cycle that consists of the following
four successive stages: planning for change (plan), execution of the plan (do),
evaluation of results (check) and standardization of the new, improved process (act) [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ].
While TQM takes a scientific, statistical, and evidence-based approach for detecting
and reducing quality anomalies through incremental quality improvement, BPR
focuses on systematically reducing process anomalies through visualization and radical
quality performance improvement [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]. Early BPM concept was focused largely on
the technical aspects of process control, especially those related to production. Under
the TQM paradigm, BPM gradually evolved from the narrow focus on technical
issues toward a more management direction [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. Authors of [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ] define BPM as the
management approach that focuses on business processes. A business process is
defined as a horizontal sequence of activities that transform an input (need) to an output
(result) to meet the needs of customers or stakeholders [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ].
        </p>
        <p>
          BPM took a more concrete form during the major revision of the ISO 9001
standard in 2000, and then in 2008 and 2015. These versions of the standard made the shift
of focus from individual quality management requirements to a more holistic
processoriented approach [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. The ISO 9001:2015 standard considers process approach as
the one of its quality management principles. A process approach means an
organization manages their business as a system of processes. A process is described as a set
of interrelated or interacting activities that use inputs to deliver an intended result.
Process inputs and outputs might be tangible (e.g. materials, components or
equipment) or intangible (e.g. data, information or knowledge) [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. Since the revision of
ISO 9001, BPM has had a central role in the implementation of all standards. Now it
has a role of an integrated mechanism of managing the processes [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ].
        </p>
        <p>
          Since BPM is heterogeneously defined in the literature, a need of a standardized
BPM framework has inspired appearance of BPM Maturity Models (BPMMM) [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ].
Authors of review [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ] refer to a maturity model as to the sequence of discrete
maturity levels used to assess processes in one or multiple business domains. Maturity levels
represent expected or typical evolution of these processes [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ]. For example,
Capability Maturity Model Integration (CMMI) in the area of software engineering emerged
at the beginning of 1990s as a means to improve software development processes to
achieve higher quality, and has been used since then by hundreds of organizations
worldwide. The success of CMMI inspired the development of several maturity
models in other domains, including BPM [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ]. In paper [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ], the importance and impact of
an organization’s business process maturity on overall performance has been
presented. BPMMM presented in this study is based on the maturity model that was defined
for the maturity of software development capability [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]. According to [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ], with the
increasing level of an organization’s BPM maturity, the importance and impact of
BPMN models (since BPMN is considered as de-facto standard in business process
modeling) is increasing and becoming critical for overall BPM success.
        </p>
        <p>
          Table 1 describes BPM maturity levels with respect to the dimensions of awareness
of business processes (ABP), documentation of business processes (DBP), monitoring
of business processes (MBP), and refinement of business processes (RBP).
Therefore, to the best our knowledge, the maturity model presented in [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ] is the only
maturity model that, unlike BPMMMs reviewed in [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ], presents the role of business
process modeling and supporting tools in different process maturity levels.
2.2
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>Business Process Model Quality</title>
        <p>
          The goal of business process modeling is the representation of organizational
activities, so that current processes may be analyzed and improved. Business process
modeling is not only a requirement for ISO 9001 quality standards or BPM maturity
models; it plays an important role in the implementation of work-flow management [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ].
        </p>
        <p>
          Modeling helps visualize the important steps in a business process, how they are
related to each other, which actors and information systems are involved in carrying
out various activities, and where communication takes place with external parties.
Business process models are usually described in a visual way, using figures that are
connected to each other and supported by textual annotations [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ]. Graphical notation
of the BPMN 2.0 specification includes following elements to describe business
processes (see Fig. 1) [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ].
        </p>
        <p>
          BPMN business process diagrams basically describe business processes in terms of
events and actions connected through control flows that indicate valid sequences in
the process execution. Gateways are special nodes connected through control flows
that indicate whether the process executes in parallel (AND), alternatively (XOR) or
optionally (OR). The beginning of the process is denoted by a start event and its
conclusion by a set of end event nodes. Each pool represents a process itself, while each
lane represents a human participant in the activity [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ].
        </p>
        <p>
          Authors of [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ] proposed a business process model quality framework called SIQ
(it is “Simple enough to be practically applicable, Integrates the most relevant insights
from the BPM field, and deals with Quality” [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ]). SIQ defines three quality
categories of the business process model: syntactic quality (conformance to the rules of a
modeling notation), semantic quality (conformance to a captured process), and
pragmatic quality (understandability by readers) [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ].
        </p>
        <p>
          While syntactic quality of designed business process models is checked by
modeling software tools and checking semantic quality is hardly possible without human
involvement (it requires understanding the domain in question and the exact purpose
of the process model [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ]), checking pragmatic quality is of interest for research in
terms of its automation. Mendling, Reijers, and van der Aalst defined Seven Process
Modeling Guidelines (7PMG) framework for creating understandable models that are
less error-prone or improving the quality of existing models [
          <xref ref-type="bibr" rid="ref17 ref19">17, 19</xref>
          ].
        </p>
        <p>
          As for quantitative process model quality indicators, various metrics and thresholds
for such metrics were proposed for BPMN process models [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ], such as:
• Size (number of events, gateways, tasks, and sequence flows).
• Gateway mismatch (sum of gateway pairs that do not match each other).
• Connectivity coefficient (ratio of the number of arcs to the number of nodes).
• Control flow complexity (sum over all gateways weighted by their potential
combinations of states after the split).
2.3
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>Conclusion on Related Work Review</title>
        <p>Performed review demonstrates that, despite the lack of clear definition and standards,
BPM is the dynamically growing management approach adopted by many
organizations and considered as the one of quality management principles of ISO 9001
standard. Business process modeling, being the core technique of BPM, plays an important
role in business process analysis and improvement, and also facilitates increasing of
BPM maturity of an overall organization. Present State-of-the-Art shows there are
heterogeneous metrics and corresponding thresholds used to measure business process
model quality. The generalized measure that could combine viewpoints of size,
gateway mismatch, nodes connectivity, and control flow complexity is not revealed yet.
3
3.1</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Business Process Model Quality Evaluation</title>
      <sec id="sec-3-1">
        <title>Business Process Model Measures</title>
        <p>
          Out of the seven process modeling guidelines provided by the 7PMG framework, we
have left only five by merging G1 and G7, and avoiding the guideline G6 [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ]. It is
suggested, that G7 “Decompose a model with more than 31 elements” might be
applied as the consequence of G1 “Do not use more than 31 nodes”, so that is why these
guidelines were merged into the single rule R1 “Do not use more than 31 nodes or
decompose a model with more than 31 elements if possible”. The guideline G6 “Use
verb-object activity labels” is avoided, since it belongs to the semantic process model
quality, while the pragmatic quality is considered in this study. Remaining four
guidelines G2 – G5 are adopted as rules R2 – R5 respectively (see Table 2). For the
selected five BPMN modeling rules based on the 7PMG guidelines we need to define
criteria that might quantifiably evaluate the degree of fulfillment of each of the modeling
rules R1 – R5 by the analyzed BPMN process model. Such criteria might be derived
from the following measures.
nodes,
        </p>
        <p>= | |.</p>
        <p>Total number of nodes (TNN). The size of the collection of business process model
Number of invalid elements (NIE). Number of nodes with invalid inputs or outputs
(G2 recommendation should be applied for all types of nodes, not only gateways):

= ∑ ∈ (|  | ≠ 1 ∨ |</p>
        <p>| ≠ 1) + ∑ ∈ (|  | &gt; 1 ∨ |  | &gt; 1) +
+ ∑ ∈ ¬[(|  | = 1 ∧ |  | &gt; 1) ∨ (|  | &gt; 1 ∧ |  | = 1)] .
(1)
Where:
gateways  ∈  ;
puts of the node,  ∈  =  ∪  ∪  .
─  is the collection of tasks  ∈  ,  is the set of events  ∈  ,  is the collection of
─ |  | is the size of the set of inputs of the node, |  | is the size of the set of
outNumber of start events (NSE). The size of the set of start events, which is the subset
of the collection of events, 
of the collection of events, 
= |  ⊆  |.</p>
        <p>= |  ⊆  |.</p>
        <p>Number of end events (NEE). The size of the set of end events, which is the subset
Number of mismatched gateways (NMG). The count of gateways that do not have
matching gateways. It is calculated as the difference between numbers of split
gateways (with 1 input and more than 1 output) and join gateways (with more than 1 input
and 1 output):
= |∑ ∈ (|  | = 1 ∧ |  | &gt; 1) − ∑ ∈ (|  | &gt; 1 ∧ |  | = 1)|.
(2)</p>
      </sec>
      <sec id="sec-3-2">
        <title>Total number of gateways (TNG). The size of the set of gateways,</title>
        <p>= | |.</p>
      </sec>
      <sec id="sec-3-3">
        <title>Total number of inclusive (OR) gateways (TNI). The size of the collection of inclu</title>
        <p>sive (OR) gateways, which is the subset of the set of gateways, 
= | 
⊆  |.
3.2</p>
      </sec>
      <sec id="sec-3-4">
        <title>Criteria of Business Process Model Quality</title>
        <p>
          Using business process model measures proposed in the previous subsection, we have
formulated criteria of business process model quality   ,  = ̅1̅,̅5̅ (see Table 2). These
criteria are based on the set of modeling rules R1 – R5 derived from the 7PMG
recommendations for business process modeling [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ].
1
− 1)2
}
BPMN modeling rule
R1: Do not use more than 31 nodes or
decompose a model with more than 31
elements if possible (merged G1 and G7)
R2: Avoid nodes with invalid inputs or
outputs (refined G2)
R3: Avoid usage of multiple start or
multiple end events or missing events (G3)
R4: Avoid gateways mismatch (G4)
R5: Avoid inclusive (OR) gateways (G5)
        </p>
        <p>Criteria equation
 3 = min {
1 + (</p>
        <p>1, 
 1 = { 31</p>
        <p>
          ≤ 31,
, 
Each of these criteria   ,  = 1̅̅,̅5̅ serves to quantifiably evaluate the degree to which
the analyzed business process model fulfills corresponding rules R1 – R5. Therefore,
calculated values of these criteria belong to the interval   ∈ [
          <xref ref-type="bibr" rid="ref1">0,1</xref>
          ],  = ̅1̅,̅5̅. By
introducing these criteria we did contribute to the State-of-the-Art, however, the need for
the generalized quality criterion of business process models still exists.
Weighted sum model. In order to define the generalized criterion for BPMN process
model quality evaluation, we used the weighted sum model (WSM) [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ]. It is
applicable in this case, since all the criteria are expressed in the same unit. Hence the
generalized criterion of business process model quality might be defined as following:

= ∑5=1   ⋅   .
(3)
Where   ,  = ̅1̅,̅5̅ are the relative weights of importance of the criteria   ,  = ̅1̅,̅5̅.
        </p>
        <p>
          Values of the relative weights are based on the ranks of 7PMG recommendations
defined in [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ] (see Table 3). Therefore, the generalized quality criterion takes values
in the interval  ∈ [
          <xref ref-type="bibr" rid="ref1">0,1</xref>
          ], where 0 stands for the lowest quality, while 1 indicates
the highest quality of a business process model.
Quality criterion values translation into linguistic values. Inspired by the approach
shown in [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ], we propose the procedure of translation from crisp quality values
represented by the  criterion into linguistic values (see Table 4). However, while [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]
proposes fuzzification of multiple business process model measures and inference
procedure in order to obtain the linguistic values of process model understandability
and modifiability, our approach is based on the translation of the generalized quality
criterion into the single linguistic value according to the Harrington desirability scale
(see Table 4) [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ], which describes the quality of the business process model based on
multiple criteria (see Table 2).
Software Prototype. In order to store analyzed BPMN models in a way they can be
queried and reused, we have applied the ontology defined in Zachman Framework
and elaborated by authors of [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] (see Fig. 2). We also used practitioners experience
in categorization of BPMN artifacts according to the Zachman Framework [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ].
        </p>
        <p>As it is shown in Fig. 2, the software prototype operates over the two-tier data
storage. The lower layer is based on the in-memory H2 relational database that stores raw
measures of process models, while higher layer is implemented in a form of RDF
(Resource Description Framework) graph under the control of the Apache Jena
framework that offers tools for querying linked data about business process models.</p>
        <p>The overall architecture of the software prototype is quite simple (see Fig. 3); it is
based on the Spring Boot Java framework on the server side and the single-page
AngularJS web application on the front-end side. The Camunda BPMN Model API
(Application Programming Interface) library is used to process XML-based files that
contain BPMN 2.0 definitions of business process models.</p>
        <p>In order to visualize summary results we used the Microsoft Power BI dashboard
as the alternative for the web-interface under development (see Fig. 4).</p>
        <p>
          Validation Results. At this moment the software prototype allows loading and
processing of BPMN 2.0 documents in order to evaluate their quality in both numerical
and linguistic forms. It also implements simple querying using the
“subject-predicateobject” form over the stored business process models data. The software usage
example is shown in Fig. 5. 3390 BPMN 2.0 definitions of business processes from
different domains provided in the GitHub public repository of Camunda [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ] were
processed using the developed prototype.
        </p>
        <p>Out of these models, 2606 are of very high quality (see Fig. 4), 470 are of high
quality, and remaining 314 are of medium quality. However, only 1250 models are
considered as those fully conform to the introduced quality criteria (see Fig. 4). It
means, that 1250 models have  = 1, while remaining 1356 very high-quality
process models still could be improved ( &lt; 1), as well as the 784 models of high
and medium quality. As it is shown in Fig. 3, R2 is the most commonly violated
business process modeling rule (avoid nodes with invalid inputs or outputs). Other
commonly violated business process modeling rules are R4 (avoid gateways mismatch)
and R3 (do not use multiple start or multiple end events). Examples of rules violations
detected in the analyzed set of BPMN models are shown in Fig. 6.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Conclusion and Future Work</title>
      <p>
        In this paper we have introduced the set of business process model measures used to
evaluate the degree to which a business process model fulfills each of the business
process modeling rules derived from the 7PMG framework. By applying the WSM
model [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ] and Harrington scale [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ], we have obtained the generalized quality
criterion, which crisp values could be translated into linguistic values. The data model and
developed software prototype allow storing data about processed BPMN models in
order to simplify their querying and reusing. Early results of business process model
quality evaluation are demonstrated and discussed. Future work includes elaboration
on the data model and the software solution (compliance with the Zachman
Framework ontology, advanced querying and versions traceability of BPMN models), and
new results analysis.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Dumas</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>La</given-names>
            <surname>Rosa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Mendling</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Reijers</surname>
          </string-name>
          , H.:
          <article-title>Introduction to Business Process Management</article-title>
          . In:
          <article-title>Fundamentals of business process management</article-title>
          . Heidelberg: Springer (
          <year>2013</year>
          ). doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>642</fpage>
          -33143-
          <issue>5</issue>
          _
          <fpage>1</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Pavlicek</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hronza</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pavlickova</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jelinkova</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>The business process model quality metrics</article-title>
          .
          <source>Workshop on Enterprise and Organizational Modeling and Simulation</source>
          ,
          <volume>134</volume>
          -
          <fpage>148</fpage>
          . Springer, Cham (
          <year>2017</year>
          ). doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>319</fpage>
          -68185-6_
          <fpage>10</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Van der Aalst</surname>
          </string-name>
          , W. M.:
          <article-title>Business process management: a comprehensive survey</article-title>
          .
          <source>Hindawi Publishing Corporation: ISRN Software Engineering</source>
          (
          <year>2013</year>
          ). doi:
          <volume>10</volume>
          .1155/
          <year>2013</year>
          /507984
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Kahloun</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghannouchi</surname>
            ,
            <given-names>S. A.</given-names>
          </string-name>
          :
          <article-title>A Classification Algorithm for Assessing the Quality Criteria for Business Process Models</article-title>
          .
          <source>International Conference on Health Information Science</source>
          ,
          <volume>71</volume>
          -
          <fpage>81</fpage>
          . Springer, Cham (
          <year>2017</year>
          ). doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>319</fpage>
          -76351-
          <issue>4</issue>
          _
          <fpage>8</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Oukharijane</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yahya</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Boukadi</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Abdallah</surname>
          </string-name>
          , H. B.:
          <article-title>Towards an approach for the evaluation of the quality of business process models</article-title>
          .
          <source>AICCSA</source>
          <year>2018</year>
          ,
          <volume>1</volume>
          -
          <fpage>8</fpage>
          (
          <year>2018</year>
          ). doi:
          <volume>10</volume>
          .1109/AICCSA.
          <year>2018</year>
          .8612811
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Yahya</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Boukadi</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ben-Abdallah</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maamar</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          :
          <article-title>Application of Fuzzy Logic to Assess the Quality of BPMN Models</article-title>
          .
          <source>ICSOFT</source>
          <year>2017</year>
          ,
          <volume>188</volume>
          -
          <fpage>209</fpage>
          . Springer (
          <year>2018</year>
          ). doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>319</fpage>
          -93641-
          <issue>3</issue>
          _
          <fpage>9</fpage>
        </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>
            ,
            <surname>Rodriguez-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 58</source>
          ,
          <fpage>187</fpage>
          -
          <lpage>205</lpage>
          (
          <year>2015</year>
          ). doi:
          <volume>10</volume>
          .1016/j.infsof.
          <year>2014</year>
          .
          <volume>07</volume>
          .011
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Tricker</surname>
          </string-name>
          , R.: ISO 9001:
          <article-title>2015 for Small Business</article-title>
          . Taylor &amp;
          <string-name>
            <surname>Francis</surname>
          </string-name>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Bonnet</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Decker</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dugan</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kurz</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Misiak</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ringuette</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <string-name>
            <surname>Making</surname>
            <given-names>BPMN</given-names>
          </string-name>
          <article-title>a true lingua franca</article-title>
          .
          <source>BPM Trends</source>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Harmon</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <source>The State of Business Process Management</source>
          <year>2016</year>
          .
          <source>BPTrends</source>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>J. Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ahn</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Applying OWL Ontology to Zachman Framework for Requirement Analysis</article-title>
          .
          <source>Advanced Science and Technology Letters</source>
          ,
          <volume>46</volume>
          ,
          <fpage>34</fpage>
          -
          <lpage>37</lpage>
          (
          <year>2014</year>
          ). doi:
          <volume>10</volume>
          .14257/astl.
          <year>2014</year>
          .
          <volume>46</volume>
          .08
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Roeser</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kern</surname>
            ,
            <given-names>E. M.:</given-names>
          </string-name>
          <article-title>Surveys in business process management - a literature review</article-title>
          .
          <source>Business Process Management Journal</source>
          <volume>21</volume>
          (
          <issue>3</issue>
          ),
          <fpage>692</fpage>
          -
          <lpage>718</lpage>
          (
          <year>2015</year>
          ). doi:
          <volume>10</volume>
          .1108/BPMJ-07- 2014-0065
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Chountalas</surname>
          </string-name>
          , P. T.,
          <string-name>
            <surname>Lagodimos</surname>
            ,
            <given-names>A. G.</given-names>
          </string-name>
          :
          <article-title>Paradigms in business process management specifications: a critical overview</article-title>
          .
          <source>BPM Journal</source>
          <volume>25</volume>
          (
          <issue>5</issue>
          ),
          <fpage>1040</fpage>
          -
          <lpage>1069</lpage>
          (
          <year>2019</year>
          ). doi:
          <volume>10</volume>
          .1108/BPMJ01-2018-0023
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Saab</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Helms</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zoet</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Predictive quality performance control in BPM: proposing a framework for predicting quality anomalies</article-title>
          .
          <source>Procedia computer science</source>
          ,
          <volume>138</volume>
          ,
          <fpage>714</fpage>
          -
          <lpage>723</lpage>
          (
          <year>2018</year>
          ). doi:
          <volume>10</volume>
          .1016/j.procs.
          <year>2018</year>
          .
          <volume>10</volume>
          .094
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Tarhan</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Turetken</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reijers</surname>
            ,
            <given-names>H. A.</given-names>
          </string-name>
          :
          <article-title>Business process maturity models: A systematic literature review</article-title>
          .
          <source>Information and Software Technology</source>
          ,
          <volume>75</volume>
          ,
          <fpage>122</fpage>
          -
          <lpage>134</lpage>
          (
          <year>2016</year>
          ). doi:
          <volume>10</volume>
          .1016/j.infsof.
          <year>2016</year>
          .
          <volume>01</volume>
          .010
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Polancic</surname>
          </string-name>
          , G.:
          <article-title>Process Maturity and BPMN</article-title>
          . Orbus
          <string-name>
            <surname>Software</surname>
          </string-name>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Reijers</surname>
            ,
            <given-names>H. A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mendling</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Recker</surname>
          </string-name>
          , J.:
          <article-title>Business process quality management</article-title>
          .
          <source>In Handbook on Business Process Management</source>
          <volume>1</volume>
          ,
          <fpage>167</fpage>
          -
          <lpage>185</lpage>
          . Springer, Berlin, Heidelberg (
          <year>2010</year>
          ). doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>642</fpage>
          -45100-
          <issue>3</issue>
          _
          <fpage>8</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Ceballos</surname>
            ,
            <given-names>H. G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Flores-Solorio</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Garcia</surname>
            ,
            <given-names>J. P.:</given-names>
          </string-name>
          <article-title>A Probabilistic BPMN Normal Form to Model and Advise Human Activities</article-title>
          .
          <source>International Workshop on Engineering Multi-Agent Systems</source>
          ,
          <volume>51</volume>
          -
          <fpage>69</fpage>
          . Springer, Cham (
          <year>2015</year>
          ). doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>319</fpage>
          -26184-
          <issue>3</issue>
          _
          <fpage>4</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <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>
          , Re,
          <string-name>
            <given-names>B.</given-names>
            ,
            <surname>Spagnolo</surname>
          </string-name>
          ,
          <string-name>
            <surname>G. O.</surname>
          </string-name>
          :
          <article-title>Quality Assessment Strategy: Applying Business Process Modelling Understandability Guidelines</article-title>
          . University of Camerino, Italy (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Mendling</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reijers</surname>
          </string-name>
          , H. A.,
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W. M. P.</given-names>
          </string-name>
          :
          <article-title>Seven process modeling guidelines (7PMG)</article-title>
          .
          <source>Information and Software Technology</source>
          <volume>52</volume>
          ,
          <fpage>127</fpage>
          -
          <lpage>136</lpage>
          (
          <year>2010</year>
          ). doi:
          <volume>10</volume>
          .1016/j.infsof.
          <year>2009</year>
          .
          <volume>08</volume>
          .004
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Ghosh</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mal</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Majumdar</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Advanced Optimization and Decision-Making Techniques in Textile Manufacturing</article-title>
          . CRC Press (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Voronin</surname>
          </string-name>
          , A.:
          <article-title>Multi-Criteria Decision Making for the Management of Complex Systems</article-title>
          .
          <source>IGI Global</source>
          (
          <year>2017</year>
          ). doi:
          <volume>10</volume>
          .4018/978-1-
          <fpage>5225</fpage>
          -2509-7
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Deconstruct</surname>
          </string-name>
          <article-title>Business Process Model using Zachman Framework Principles, 5 part videos</article-title>
          . https://sunilduttjha.wordpress.com/
          <year>2012</year>
          /03/16/deconstruct-business
          <article-title>-process-model-usingzachman-framework-principles-5-part-videos/</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>24. Camunda - BPMN for research. https://github.com/camunda/bpmn-for-research</mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>