<!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>
      <journal-title-group>
        <journal-title>SCME, Doctoral Consortium, Tutorials, Project Exhibitions, Posters and Demos, October</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>A Catalog of BPMN Extensions</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Milene Cavalcante</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Enyo Gonçalves</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>João Araújo</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Tiago Heineck</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Federal Institute of Catarinense</institution>
          ,
          <addr-line>IFC</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Federal University of Ceará</institution>
          ,
          <addr-line>UFC</addr-line>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>NOVA University of Lisbon</institution>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2025</year>
      </pub-date>
      <volume>2</volume>
      <fpage>0</fpage>
      <lpage>23</lpage>
      <abstract>
        <p>BPMN is a business modeling language that has been extended since its creation. Creating a new BPMN extension or using an existing extension involves searching for existing extensions and their constructs as a starting point. This identification of extensions can be done through searches in scientific libraries or through a systematic review, which requires efort and time and is subject to failure. In this context, catalogs have proven to be efective for gathering and organizing knowledge, including information on modeling language extensions. Therefore, the existence of a catalog of BPMN extensions and their constructs can make this identification faster, with less efort and less prone to failure. Motivated by this scenario, this work proposes a catalog containing 80 BPMN language extensions and 409 extended constructs, classified into three main categories: those that cater to specific domains, application areas and those aimed at general language improvements. The results indicate that the proposed catalog is useful for retrieving information and stands out for its ease of use.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;BPMN</kwd>
        <kwd>Extension</kwd>
        <kwd>Catalog</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Business Process Model and Notation (BPMN) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] is a diagrammatic modeling language widely used
to represent and manage business processes. It ofers a standardized set of symbols that facilitate the
visual representation of processes, making them more understandable to users [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. The main objective
of BPMN is to increase the competitiveness of organizations by optimizing employee productivity and
improving the definition and organization of internal processes [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>
        An extension of a modeling language refers to the broadening of its original capabilities by adding
new constructs or adapting existing ones in the standard definition. These extensions are particularly
useful to meet the specific needs of a domain, an application area or to introduce general improvements
[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. They ofer greater flexibility and practicality, without the need to create a new language or make
direct changes to the original definition. In this context, BPMN has often been extended to meet diferent
demands, such as those found in healthcare, logistics and the Internet of Things (IoT).
      </p>
      <p>
        Several modeling languages, such as UML [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], iStar [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] and KAOS [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], have sought to identify
and document their existing extensions, with the aim of supporting the community and providing
a comprehensive view of the work done to extend these languages, as presented by [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] and [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
This extension process is generally motivated by two main factors: improving existing elements and
adapting the language to meet the needs of specific domains. The first approach focuses on improving
aspects of the language that are considered relevant, while the second aims to adjust it to particular
contexts, such as application areas.
      </p>
      <p>
        In this context, adopting extensions is preferable to creating a new modeling language, since
developing a language from scratch can be more costly and time-consuming. Extensions ofer the flexibility
needed to meet specific demands while preserving the benefits of the original language, such as
standardization and tool support. This optimizes the development and application of complex business
models, as discussed in [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
      </p>
      <p>
        Identifying BPMN extensions can be a complex, time-consuming and error-prone task when
performed without adequate support. Two possible approaches to performing this task include: conducting
a database search, selecting the extensions and then analyzing the results; or analyzing articles obtained
through a systematic review, seeking to identify the desired information [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. However, the use of tools
such as catalogs can help to systematize the presentation of data and facilitate search and retrieval tasks.
These tools include catalogs, which have been widely and successfully used to gather accumulated
knowledge, including language extensions.
      </p>
      <p>
        In this context, this paper proposes a web catalog for extensions of the BPMN process modelling
language, with the aim of supporting teams in formalizing processes. In addition, we carried out an
evaluation of the BPMN extensions catalog with users. Previous studies presented in [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] 1 identified
80 BPMN extensions from 2019 to 2024, which were gathered in the catalog developed in this work.
This study is part of a set of initiatives that seek to analyze and systematize extensions to modelling
languages, following similar approaches to those carried out by [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] for iStar extensions and by [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] for
KAOS extensions.
      </p>
      <p>This article is organized as follows: Section 2 presents the theoretical framework, covering modeling
languages, BPMN, its extensions, and catalogs. Section 3 discusses related works. The methodology
adopted is detailed in Section 4. Section 5 presents the catalog of BPMN extensions. The evaluation of
the catalog is described in Section 6. Finally, the conclusions of the study are presented in Section 7.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Background</title>
      <sec id="sec-2-1">
        <title>2.1. BPMN Language Overview</title>
        <p>
          BPMN is defined in [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ] as a modeling language that is widely used to represent business processes and
is recognized in both academia and industry. BPMN is standardized by the Object Management Group
(OMG) and has an ISO standard specification. This work deals with version 2.0 of BPMN [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ], its most
recent version, which presents significant changes in relation to the previous version. The most recent
formalization of the standard addresses the execution semantics of all BPMN elements, establishes an
extensibility mechanism and resolves inconsistencies and ambiguities, among other important advances
[
          <xref ref-type="bibr" rid="ref17">17</xref>
          ].
        </p>
        <p>
          BPMN elements are organized into five main categories: flow objects, data, connection objects, lanes
and artifacts. The language is widely valued for its semantic robustness and expressiveness, facilitating
the interpretation of models and reducing the risk of misunderstandings. In addition, BPMN is supported
by various modeling tools, such as Activiti, BPMN2 Modeler and Bizagi, which allow models to be
converted into executable languages eficiently [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ].
2.1.1. BPMN Extension Mechanism
As mentioned earlier, BPMN 2.0 introduces an extensibility mechanism that allows new attributes
and/or improvements to be added to standard constructs, with the aim of meeting the specific needs
of diferent domains, without contradicting the originality of the modeling language. According to
[
          <xref ref-type="bibr" rid="ref16">16</xref>
          ], extension attributes must be compatible with the semantics of the original elements and must not
lead to contradictions. Even with the possibility of adapting or proposing a new element, the diagrams
generated must maintain their basic visual structure to ensure that they are easily understood by any
tool or viewer, as illustrated in Figure 1.
        </p>
        <p>This feature is essential for representing concepts that are specific to certain contexts in
generalpurpose modeling languages. It also facilitates the integration of essential information for transforming
models into formats that can be adapted to specific platforms or codes [ 20]. BPMN stands out by</p>
        <sec id="sec-2-1-1">
          <title>1https://sites.google.com/view/systematicreviewbpmnextensions</title>
          <p>
            ofering generic extension elements, allowing adaptations to be created for diferent domains, while
ensuring that the core elements are preserved [
            <xref ref-type="bibr" rid="ref3">3</xref>
            ]. Recently, Braun et al. [
            <xref ref-type="bibr" rid="ref18">18</xref>
            ] proposed a new approach
to developing these extensions, broadening the possibilities for customizing and adapting the language.
          </p>
          <p>As an example of an extension, we present an adaptation of the activity element proposed in [21].
This adaptation provides a clearer representation of a real-time process by incorporating a circle at the
top of the activity builder with the initials ’RT’. Thus, the activity illustrated in Figure 2 represents tasks
that are taking place in real time.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Related Works</title>
      <p>
        According to [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], catalogs are a widely used solution to support software engineers in obtaining
practical resources for their projects. A catalog consists of a body of knowledge, which can include
general information, such as that found in books etc., or more specific knowledge, such as the SLR
developed in [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] on BPMN extensions. Often, catalogs are created with the aim of facilitating the reuse
of resources in diferent contexts, as evidenced by [ 22] in the elicitation of non-functional requirements.
      </p>
      <p>
        Catalogs related to modeling language extensions have been identified, as detailed below. A related
piece of research was proposed in Gonçalves et al. [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], in which the authors present a list of extensions
to the iStar modeling language, resulting from a Systematic Literature Review (SLR). The aim of the
study was to identify and analyze existing extensions to the language, based on an SLR that resulted in
96 articles and 307 identified constructs. As future work, the authors developed and published a catalog
of iStar extensions, presented in Gonçalves et al. [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. That catalog, similar to the one presented here,
shows a list of studies that have proposed new extensions for modeling languages, all of them obtained
from an SLR.
      </p>
      <p>
        Similarly, Sousa’s work [23] aimed to identify and analyze extensions to the KAOS language. The SLR
identified 35 articles in seven electronic databases, considering publications up to 2019. Subsequently,
the review was updated by Gonçalves and Monte [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], finally reaching the identification of 50 KAOS
extensions. The data collected was incorporated into the catalog of KAOS extensions proposed in [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ],
following procedures similar to those adopted in the work on iStar extensions and in this study.
      </p>
      <p>
        The SLR on which our catalog is based is described in [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. We identified reviews on BPMN extensions
proposed in three periods, according to the articles respectively: from 2007 to 2014, from 2014 to 2018
and, more recently, from 2019 to 2025. The studies collected were incorporated into the database that
makes up the catalog.
      </p>
      <p>Although the objective of this work is similar to that of the aforementioned studies - to catalog
modeling language extensions based on SLRs - it difers in that it deals exclusively with the BPMN
language, while the previous works focus on the iStar and KAOS languages. In addition, our analysis
is more focused and objective, considering specific aspects such as types of extensions, compatibility
between syntaxes, tool support, among others.</p>
      <p>Adopting the catalog in the process of identifying BPMN extensions provides significant benefits by
minimizing the time and efort required to consult multiple sources or rely on experts. In this sense,
the reuse of extensions is a more eficient and advantageous alternative to developing new ones, as
illustrated in this paper.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Methodology</title>
      <p>This section presents, in detail, the methodological procedures adopted for the development of the
BPMN language extension catalog. The process was conducted based on clearly defined objectives and
research questions that guided each stage of the study.</p>
      <p>From a previously conducted SLR, a solid database was extracted to compose the catalog, which was
later implemented in web format to ensure accessibility and organization. The system structure was
designed to allow detailed and transparent registration of extensions, encouraging their reuse.</p>
      <p>After filling the catalog with the extracted data, a validation stage was carried out through the
application of a survey [24] structured based on the UTAUT model [25], with the objective of evaluating
the acceptance and perceived efectiveness of the tool by users. Each of these phases—extraction,
implementation, feeding, and validation—is described individually and systematically in the following
subsections.</p>
      <sec id="sec-4-1">
        <title>4.1. Objectives</title>
        <p>General Objective. To develop and evaluate an online catalog of extensions for the BPMN modeling
language, with the aim of providing an organized, accessible and useful tool for consulting and registering
extensions, contributing to the BPMN community.</p>
        <p>Specific Objectives.</p>
        <p>• Propose an online tool for cataloging and consulting BPMN extensions.</p>
        <p>• Evaluate the accuracy and efectiveness of the catalog.</p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Research Questions</title>
        <p>The research questions of this study address the central aspects related to the catalog of BPMN language
extensions.</p>
        <p>• RQ1: How can the existing BPMN language extensions be catalogued? This question
investigates the main extensions proposed for the BPMN language, with a view to identifying
and organizing them in a catalog. In addition, essential criteria are analyzed to ensure that the
most relevant information is included in the catalog in a structured way.
• RQ2: How eficient is the catalog developed to BPMN extensions? This question assesses
the eficiency of the catalog developed, considering its ability to facilitate the organization and
consultation of BPMN extensions, promoting a more efective and intuitive interaction for users.
To do this, metrics were used based on the UTAUT (Unified Theory of Acceptance and Use of
Technology) model, which includes factors such as intention to use, expectation of performance,
expectation of efort and facilitating conditions.</p>
      </sec>
      <sec id="sec-4-3">
        <title>4.3. Study Steps</title>
        <p>
          This subsection describes the steps followed to develop the catalog of BPMN extensions. The procedures
are presented in the subsections below, highlighting that the results of the SLR on BPMN extensions
[
          <xref ref-type="bibr" rid="ref12">12</xref>
          ] served as the starting point for the activities carried out in this work.
        </p>
        <p>
          Extracting the Extensions. The extraction of existing extensions is based on a database drawn up
from the SLR research questions [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ], containing all the information needed to complete the catalog.
In addition, this stage includes storing the data of all the builders, which will now be preserved to be
attached to their respective publication - an aspect that had not been addressed in the review.
        </p>
        <p>
          Catalog implementation. The BPMN Extension Catalog is developed in a web version, using
the PHP language 2, in conjunction with the Laravel framework 3. The adoption of Laravel enables
the application of the MVC (Model-View-Controller) architectural pattern, favoring the separation
of responsibilities between layers and code maintainability. The database used is MySQL 4, which
ensures query optimization and broad compatibility with analysis and integration tools. The entire
application is packaged in Docker containers 5, allowing it to run in heterogeneous environments with
high portability and facilitating the continuous deployment process. The catalog is pre-structured to
allow the inclusion of data through forms, enabling the registration of the fields necessary to feed each
publication. These fields are based on the research questions addressed by SLR [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ], providing better
organization and availability of information. In addition, the catalog is unique in that it includes a
review mechanism that lists all extended constructs, allowing them to be reused by the community.
        </p>
        <p>Inclusion in the Catalog. With the information gathered and the catalog available, the final
update is made to include the necessary data, completing the process of registering extensions. Each
publication receives the information according to the topics listed below, plus the addition of image-type
attachments representing the extended constructs in cases where there is concrete extended syntax,
accompanied by an example of their use.</p>
        <p>Catalog Validation. To assess the acceptance of the BPMN Extension Catalog, a survey [25] based on
the UTAUT model was conducted. The study involved 17 master’s students, who answered a
questionnaire structured around the main constructs of the model: Performance Expectancy, Efort Expectancy,
Social Influence, and Facilitating Conditions. The answers were recorded on a five-point Likert scale,
ranging from “Strongly Disagree” to “Strongly Agree”. Before the final application, a pilot test was
carried out with five master’s students, whose suggestions were incorporated to ensure the clarity and
suitability of the questionnaire. The suggestions obtained were analyzed and incorporated into the final
version of the questionnaire, ensuring its clarity and suitability. The UTAUT model, proposed by [25],</p>
        <sec id="sec-4-3-1">
          <title>2https://www.php.net 3https://laravel.com/ 4https://www.mysql.com/ 5https://www.docker.com/</title>
          <p>is widely used to study technology adoption and integrates eight theories on technological acceptance,
including the Theory of Reasoned Action (TRA), the Technology Acceptance Model (TAM) and the
Theory of Planned Behavior (TPB). Its main objective is to understand the factors that influence the
intention to use a system, with four constructs having a direct impact on this process: Performance
Expectancy, Efort Expectancy, Social Influence and Facilitating Conditions. Thus, this study seeks to
identify whether these factors influence the adoption of the catalog, helping to understand its acceptance
and feasibility of implementation in the BPMN community.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. The BPMN extension Catalog</title>
      <p>The catalog is available online at 6, where you can view the complete list of registered extensions and
select any of them to access detailed information about their attributes and respective constructions.
Figure 3 shows the conceptual model of the tool, while Table 1 illustrates an example of how
categorybased evaluation is applied to one of the extensions.</p>
      <p>The tool ofers search capabilities by author or title and allows filters to be applied by various
categories, such as application area, specific domain, proposed improvements, presentation of new
constructs, type of conservativity, compliance with OMG standards, type of representation, availability
of support tools, syntax level and compatibility between diferent syntaxes.</p>
      <p>Figure 4 shows the list of extensions cataloged, including the information mentioned and a link to
access the full details of each extension. Figure 5 shows the details of an extension, where the title
is clickable and provides all the information previously described. Figure 6 highlights the extended
constructs related to the extension.</p>
      <p>In addition, more detailed information can be accessed via the “Details” option, as illustrated in Figure
7. This detailed information ofers a comprehensive view of each extension and its specific features.</p>
      <sec id="sec-5-1">
        <title>6http://bpmnextensionscatalogue.quixada.ufc.br/</title>
        <p>Example of applying categories in an extension</p>
        <p>Similar to the list of extensions, you can also access the list of all cataloged constructs. The tool
allows you to search for constructs by name or apply specific filters, such as Shape (construct format),
Type (Node or Link) and Classification (Adaptation or New Representation), as shown in Figure 8. By
clicking on the name of a construct, detailed information is displayed on a dedicated page, the same
one accessed via publications, as shown in Figure 7.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6. Preliminary Evaluation of the BPMN Catalog</title>
      <p>The questionnaire was administered after an introductory presentation lasting approximately one hour,
covering BPMN notation, its extensions, and the usual process of searching for these extensions on an
ad hoc basis. The session also included a practical demonstration using the catalog developed. Due to
the large number of items, the complete questionnaire is also available online at: 7.</p>
      <p>Seventeen master’s students in Computer Science participated in the evaluation, all with prior
knowledge of Unified Modeling Language (UML), which facilitated their understanding of the BPMN
notation presented. Although some were already familiar with BPMN, the initial presentation aimed
to level the participants’ knowledge and provide an introductory experience in the use of notation
extensions.</p>
      <p>Before the oficial application, a pilot test was conducted with five other master’s students to review
and adjust the collection instrument. The questionnaire was structured based on an adaptation of the
UTAUT model, covering dimensions such as prior knowledge of BPMN and extensions, intention to
use, performance expectations, efort expectations, facilitating conditions, and efective use. Each of
these dimensions was evaluated using multiple statements, answered on a Likert scale of agreement.</p>
      <p>The research was conducted with master’s students, a group often considered appropriate in
experimental studies in the field of Software Engineering. According to Tichy [26], the use of students
is particularly valid in experiments whose objective is to compare methods or tools, provided that
the participants’ level of experience is clearly described. This recommendation was followed in this
study, considering that the participating students were already familiar with UML and received a formal
introduction to BPMN notation before completing the questionnaire.</p>
      <p>In addition, the study by Höst et al. [27] demonstrated that, in specific tasks, data collected from
students can be comparable to that obtained from professionals in the field, especially when participants
are properly trained. Thus, the profile of the subjects and the design adopted reinforce the validity of
the results obtained in this research.</p>
      <p>Of the participants, 82.4% (14) said they had beginner-level knowledge of BPMN, while 11.8% (2)
were intermediate and only 5.9% (1) said they had advanced knowledge. With regard to knowledge of
BPMN extensions, 88.2% (15) classified themselves as beginners and 11.8% (2) as intermediate, with no
participants having advanced knowledge in this category.</p>
      <p>The survey data was analyzed based on the levels of the 5-point Likert scale used in the questionnaire,
in which participants indicated their degree of agreement with each statement (1 = Strongly disagree;
5 = Strongly agree). The answers were quantified in order to calculate averages per construct of the
UTAUT model, allowing a numerical assessment of users’ perceptions of the catalog. However, some
statements were deliberately worded negatively, such as: “I don’t want to use the catalog” or “The
catalog will not be compatible with other tools I use”. In these cases, the answers were reversed (5 =
Strongly disagree; 1 = Strongly agree) in order to maintain the interpretative consistency of the scores
i.e. to ensure that higher values represent more positive perceptions across all items.</p>
      <p>After this normalization, the averages per participant and per construct were calculated, covering:
intention to use, expectation of performance, expectation of efort, facilitating conditions and use. Based
on this normalization, the interpretation of the results considers that the closer the averages obtained
are to 5, the more positive the participants’ perceptions of the catalog are.</p>
      <p>Tables 2 and 3 provide a comprehensive overview of the participants’ perceptions, based on the
answers collected through the survey. Table 2 shows the detailed results by item, enabling a more
precise analysis of individual opinions on specific aspects evaluated in the UTAUT model. In turn,
Table 3 consolidates this information by construct, facilitating a general understanding of the levels of
acceptance and perceived usability. This data helps to assess the potential for adoption of the catalog
and points to areas that require improvement, such as strengthening support conditions and adopting
strategies to encourage continued use of the tool.</p>
      <p>The results obtained show a positive intention to use the catalog on the part of the participants, with
an overall average of 4.44 in the Intention to Use construct, indicating agreement with statements that
recognize the relevance and usefulness of the tool. Items such as “The catalog is relevant for searching
for BPMN extensions” (average of 4.82) and “The catalog will make the search process more agile” (4.59)
reinforce this perception. In addition, Performance Expectation had an average of 4.50, showing that
users believe the catalog can improve their productivity, speed up tasks and increase the chances of
ifnding suitable extensions, as indicated by the high value of the item “Using the catalog will give me a
better chance of finding the extension I need” (4.88).</p>
      <p>The perception of ease of use was also favorable, with an average of 4.18 in Efort Expectation,
suggesting that participants find the catalog accessible and intuitive. However, the Facilitating Conditions
construct obtained a lower average (3.51), with a negative highlight for the item “A specific person or
group will be available to help me when I have dificulties” (2.88), pointing to the need for institutional
or technical support.</p>
      <p>Finally, although the intention to use was high, the average for the Use construct was 3.26, indicating
a more moderate willingness to adopt the catalog immediately. This diference may be related to factors
pointed out in the statements themselves, such as uncertainty about using it in the coming months
(averages of 2.65 and 2.59), the relatively low level of intention to exploit its functionalities to the full
(2.94), or even hesitation in adopting it as a first choice over other options (3.76). These results suggest
possible external barriers, such as a lack of ongoing familiarity with the tool, the absence of institutional
Intention to use [I don’t want to use the catalog]
Intention to use [Although it can be useful, using the catalog can make
work more complex]
Intention to use [Using the catalog will not make extension development
more productive]
Intention to use [The catalog is relevant to the BPMN extension search]
Intention to use [The catalog will make the extension search process more
agile]
Performance expectation [I believe the catalog will be useful when
searching for BPMN extensions]
Performance expectation [Using the catalog will allow me to perform
activities more quickly]
Performance expectation [Using the catalog will increase my productivity]
Performance expectation [Using the catalog will give me a better chance of
finding the extension I need]
Efort expectation [My interaction with the catalog will be clear and easy
to understand]
Efort expectation [It will be easy for me to become a catalog user]
Efort expectation [I think the catalog will be easy to use]
Efort expectation [Learning to use the catalog will be easy for me]
Facilitating conditions [I will have the necessary resources to use the
catalog]
Facilitating conditions [I will have the necessary knowledge to use the
catalog]
Facilitating conditions [The catalog will not be compatible with other tools
I use]
Facilitating conditions [A specific person or group will be available to help
me when I have dificulties]
Use [I plan to use the catalog in the coming months]
Use [I will use the catalog in the coming months]
Use [I will explore the catalog to the fullest]
Use [I plan to discover new ways to use the catalog when looking for
BPMN extensions]
Use [Even when other options are available, the catalog will always be my
first choice]
Use [I plan to make the most of the information provided by the catalog
about BPMN extensions]</p>
      <p>Use [I plan to integrate the catalog when developing BPMN extensions]
incentives or not perceiving an immediate need to use it at the moment.</p>
      <p>To better visualize these patterns and diferences across constructs, Figures 9a, 9b, 10a, 10b, and 11
present the distribution of responses for each statement in the questionnaire. It can be observed that
responses related to Intention to Use, Performance Expectation, and Efort Expectation have higher
values and less dispersion, reflecting a positive and consistent perception of the catalog. In contrast, the
constructs of Use and Facilitating Conditions show more moderate averages and greater variability,
highlighting areas in which participants demonstrated greater hesitation or perceived dificulties. These
graphical representations corroborate the previous analyses and underscore aspects that may require
attention to encourage efective adoption of the tool.</p>
      <p>(a) Intention to Use construct
(b) Performance Expectation construct</p>
      <sec id="sec-6-1">
        <title>6.1. Threats to Validity</title>
        <p>This section discusses the main threats to the validity of the survey instrument used in this study, based
on the four criteria proposed by [24]: face validity, content validity, conclusion validity and construct
validity.</p>
        <p>Face Validity refers to the preliminary assessment of the clarity, readability and comprehensibility
of the instrument’s items by people with no prior knowledge of the subject. For this stage, we applied
the pilot of the questionnaire described in the previous section, collecting the results which led to
improvements in the fluidity and wording of the questions.</p>
        <p>Content Quality refers to the qualitative assessment of the adequacy, comprehensiveness and
relevance of the items by experts or people familiar with the topic. To this end, the form was reviewed
by two experts in the field, ensuring that all the important dimensions of the object of study were
covered.</p>
        <p>Completion Validity refers to the instrument’s ability to achieve its objective, considering the
reliability of the data collected and the possibility of carrying out robust statistical analyses. In this
study, 17 students took part in the face-to-face application of the questionnaire. Although this number
was suficient to obtain an initial overview of usability, it limits the ability to make more in-depth
statistical inferences, thus restricting the validity of the quantitative conclusions.</p>
        <p>Construct Validity assesses whether the instrument efectively measures the constructs it sets out
to investigate in the context of the research. To mitigate threats related to this validity, the questionnaire
was developed with clear, objective questions and was reviewed and validated in the pilot stages,
ensuring that the answers consistently reflected the participants’ perceptions of the catalog’s usability.</p>
        <p>Despite the care taken, these threats to validity should be considered when interpreting the results,
and indicate the need for future research with larger samples and complementary methodologies to
strengthen the evidence obtained.</p>
      </sec>
    </sec>
    <sec id="sec-7">
      <title>7. Conclusion</title>
      <p>
        Since the creation of BPMN, several extensions have been proposed. However, identifying an extension
based on its characteristics or finding a builder that meets a specific need can be a complex task,
requiring time and efort. To mitigate this challenge, this article presents an online catalog of BPMN
extensions, making them easier to identify and view. The catalog, available online, brings together all
the extensions found in the SLR [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] and provides detailed information on each one. In addition, the
tool ofers advanced features, such as searching by title or author and filters for constructs, allowing
refinement by area of application, format and type. This study contributes to the systematization and
analysis of BPMN extensions.
      </p>
      <p>The analysis of the results begins with the Intention to use construct, which showed high averages,
indicating that the participants show a strong predisposition to use the BPMN extensions catalog. This
positive intention suggests that the tool arouses interest and is perceived as relevant in the context of
process modeling. However, when looking at the results of the Use construct, a discrepancy can be
seen: the averages were considerably lower, suggesting that, despite the intention, actual use has not
yet materialized.</p>
      <p>This contrast may point to the presence of external barriers - such as lack of time, institutional
support or low urgency at the time of application - which hinder the immediate adoption of the tool.
Complementing this analysis, the high scores in Performance Expectancy and Efort Expectancy indicate
that participants perceive the catalog as a useful and easy-to-use tool, which reinforces its potential for
positive impact. On the other hand, the lower values in Facilitating conditions, especially in the item
referring to the availability of support, reveal a possible gap in terms of the infrastructure or support
needed for continued use of the tool, which could negatively influence its adoption in the long term.</p>
      <p>As future work, we plan to deepen the usability analysis by means of a heuristic evaluation conducted
by experts. We also plan to carry out a comparative experiment to measure the time needed to identify
extensions and their constructs using the SLR and the catalog, dividing participants into two groups
and comparing their execution times. Finally, we intend to incorporate a system for recommending
extensions based on users’ preferences from the catalog, as well as providing the option to export the
construction to a structured file in .json format, in order to facilitate its integration with external tools
that support the format and its reuse.</p>
    </sec>
    <sec id="sec-8">
      <title>Declaration on Generative AI</title>
      <p>During the preparation of this work, the authors used ChatGPT and DeepL Translate for: sentence
rephrasing and translation. After using these tools/services, the authors reviewed and edited the content
as necessary and assume full responsibility for the content of the publication.
[20] L. J. R. Stroppi, O. Chiotti, P. D. Villarreal, Extending BPMN 2.0: Method and Tool Support,</p>
      <p>Springer-Verlag Berlin Heidelberg, 2011.
[21] A. Ouarhim, J. Lakhrouit, K. Baïna, A bpmn extension for real time handling - application to
covid-19 management, 2020.
[22] L. M. Cysneiros, Evaluating the efectiveness of using catalogues to elicit non-functional
requirements, in: Proceedings of WER, 2007, pp. 107–115.
[23] S. C. de Sousa, Uma revisão sistemática de literatura das extensões da kaos, 2019.
[24] B. Kitchenham, S. L. Pfleeger, Principles of survey research part 4: questionnaire evaluation, ACM</p>
      <p>SIGSOFT Software Engineering Notes 27 (2002) 20–23.
[25] V. Venkatesh, M. G. Morris, G. B. Davis, F. D. Davis, User acceptance of information technology:</p>
      <p>Toward a unified view, MIS Quarterly 27 (2003) 425–478.
[26] W. F. Tichy, Hints for reviewing empirical work in software engineering, Empirical Software</p>
      <p>Engineering 5 (2000) 309–312.
[27] M. Höst, B. Regnell, C. Wohlin, Using students as subjects—a comparative study of students and
professionals in lead-time impact assessment, Empirical Software Engineering 5 (2000) 201–214.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>S. A.</given-names>
            <surname>White</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Miers</surname>
          </string-name>
          , BPMN Modeling and
          <article-title>Reference Guide: Understanding and Using BPMN, Future Strategies Inc</article-title>
          .,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>M.</given-names>
            <surname>Kocbek</surname>
          </string-name>
          , G. Jošt,
          <string-name>
            <given-names>M.</given-names>
            <surname>Heričko</surname>
          </string-name>
          , G. Polančič,
          <article-title>Business process model and notation: The current state of afairs</article-title>
          ,
          <source>Computer Science and Information Systems</source>
          <volume>12</volume>
          (
          <year>2015</year>
          )
          <fpage>509</fpage>
          -
          <lpage>539</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>R. M.</given-names>
            <surname>Pillat</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T. C.</given-names>
            <surname>Oliveira</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. S. C.</given-names>
            <surname>Alencar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. D.</given-names>
            <surname>Cowan</surname>
          </string-name>
          ,
          <article-title>Bpmnt: A bpmn extension for specifying software process tailoring</article-title>
          ,
          <source>Information and Software Technology</source>
          <volume>57</volume>
          (
          <year>2015</year>
          )
          <fpage>95</fpage>
          -
          <lpage>115</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>Object</given-names>
            <surname>Management</surname>
          </string-name>
          <article-title>Group (OMG), Unified modelling language</article-title>
          ,
          <source>specification 2.5.1</source>
          ,
          <year>2017</year>
          . Available at https://www.omg.org/spec/UML/2.5.1/.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>E.</given-names>
            <surname>Yu</surname>
          </string-name>
          ,
          <article-title>Modeling strategic relationships for process reengineering</article-title>
          ,
          <source>Ph.D. thesis</source>
          , University of Toronto,
          <year>1995</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>A.</given-names>
            <surname>Dardenne</surname>
          </string-name>
          , A. van
          <string-name>
            <surname>Lamsweerde</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Fickas</surname>
          </string-name>
          ,
          <article-title>Goal-directed requirements acquisition</article-title>
          ,
          <source>Sci. Comput</source>
          . Program.
          <volume>20</volume>
          (
          <year>1993</year>
          )
          <fpage>3</fpage>
          -
          <lpage>50</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>J. P. S.</surname>
          </string-name>
          da Silva,
          <string-name>
            <given-names>M.</given-names>
            <surname>Ecar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. S.</given-names>
            <surname>Pimenta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G. T. A.</given-names>
            <surname>Guedes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. P.</given-names>
            <surname>Franz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Marchezan</surname>
          </string-name>
          ,
          <article-title>A systematic literature review of uml-based domain-specific modeling languages for self-adaptive systems</article-title>
          ,
          <source>in: 13th International Conference on Software Engineering for Adaptive and Self-Managing Systems (SEAMS)</source>
          ,
          <year>2018</year>
          , pp.
          <fpage>87</fpage>
          -
          <lpage>93</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>E.</given-names>
            <surname>Gonçalves</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Castro</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Araújo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Heineck</surname>
          </string-name>
          ,
          <article-title>A systematic literature review of i* extensions</article-title>
          ,
          <source>Journal of Systems and Software</source>
          <volume>137</volume>
          (
          <year>2018</year>
          )
          <fpage>1</fpage>
          -
          <lpage>33</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>E.</given-names>
            <surname>Gonçalves</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Monte</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Souza</surname>
          </string-name>
          , M. de Oliveira,
          <string-name>
            <given-names>J.</given-names>
            <surname>Araujo</surname>
          </string-name>
          ,
          <article-title>A systematic literature review of kaos extensions</article-title>
          , in: International Working Conference on Requirements Engineering: Foundation for Software Quality, Springer,
          <year>2025</year>
          , pp.
          <fpage>166</fpage>
          -
          <lpage>180</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>R.</given-names>
            <surname>Braun</surname>
          </string-name>
          , W. Esswein,
          <article-title>Extending bpmn for modeling resource aspects in the domain of machine tools</article-title>
          ,
          <source>WIT Transactions on Engineering Sciences</source>
          <volume>87</volume>
          (
          <year>2014</year>
          ). doi:
          <volume>10</volume>
          .2495/AMITP20130531.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>L.</given-names>
            <surname>Chung</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B. A.</given-names>
            <surname>Nixon</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Yu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Mylopoulos</surname>
          </string-name>
          ,
          <article-title>Non-functional Requirements in Software Engineering</article-title>
          , volume
          <volume>5</volume>
          , Springer,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>M.</given-names>
            <surname>Cavalcante</surname>
          </string-name>
          , E. Gonçalves,
          <article-title>Bpmn extensions updated: A systematic literature review, under review or a copy contact us cavalcantemilene01@alu</article-title>
          .ufc.br (
          <year>2025</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>E. J. T.</given-names>
            <surname>Gonçalves</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Heineck</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Araújo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Castro</surname>
          </string-name>
          ,
          <article-title>A catalogue of istar extensions</article-title>
          ,
          <source>in: WER</source>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>P. R. de Carvalho Junior</surname>
            ,
            <given-names>E. J. T.</given-names>
          </string-name>
          <string-name>
            <surname>Gonçalves</surname>
            ,
            <given-names>R. M.</given-names>
          </string-name>
          <string-name>
            <surname>Carvalho</surname>
          </string-name>
          ,
          <string-name>
            <surname>M. A. de Oliveira</surname>
          </string-name>
          ,
          <article-title>A catalogue of kaos extensions</article-title>
          ,
          <source>in: WER</source>
          ,
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>M.</given-names>
            <surname>Chinosi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Trombetta</surname>
          </string-name>
          ,
          <string-name>
            <surname>Bpmn:</surname>
          </string-name>
          <article-title>An introduction to the standard</article-title>
          ,
          <source>Elsevier</source>
          <volume>34</volume>
          (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>Object</given-names>
            <surname>Management</surname>
          </string-name>
          <article-title>Group (OMG), Business process model and notation (bpmn) - version 2</article-title>
          .0,
          <year>2011</year>
          . Available at https://www.omg.org/spec/BPMN/2.0/, accessed 2024-
          <volume>11</volume>
          -27.
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>G.</given-names>
            <surname>Aagesen</surname>
          </string-name>
          ,
          <source>J. Krogstie, Bpmn</source>
          <volume>2</volume>
          .
          <article-title>0 for modeling business processes</article-title>
          ,
          <source>in: Handbook on Business Process Management</source>
          <volume>1</volume>
          :
          <string-name>
            <surname>Introduction</surname>
            ,
            <given-names>Methods,</given-names>
          </string-name>
          <source>and Information Systems</source>
          , Springer,
          <year>2015</year>
          , pp.
          <fpage>219</fpage>
          -
          <lpage>250</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>R.</given-names>
            <surname>Braun</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Schlieter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Burwitz</surname>
          </string-name>
          , W. Esswein,
          <article-title>Bpmn4cp revised - extending bpmn for multiperspective modeling of clinical pathways</article-title>
          ,
          <source>in: Proceedings of the 49th Hawaii International Conference on System Sciences (HICSS)</source>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>K.</given-names>
            <surname>Zarour</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Guermouche</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Benmerzoug</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Drira</surname>
          </string-name>
          ,
          <source>The practice of enterprise modeling: 7th ifip wg 8</source>
          .1 working conference,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>