<!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>S. Guerreiro); pedro.manuel.sousa@tecnico.ulisboa.pt (P. Sousa)
 https://github.com/SemantifyingBPMN/SemantifyingBPMN (S. Guerreiro)</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>SemantifyingBPMN: a tool to generate BPMN models using DEMO</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Sérgio Guerreiro</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Pedro Sousa</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>INESC-ID</institution>
          ,
          <addr-line>R. Alves Redol 9, 1000-029 Lisbon</addr-line>
          ,
          <country country="PT">Portugal</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Instituto Superior Técnico, University of Lisbon</institution>
          ,
          <addr-line>Av. Rovisco Pais 1, 1049-001 Lisbon</addr-line>
          ,
          <country country="PT">Portugal</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Link Consulting SA</institution>
          ,
          <addr-line>Av. Duque de Ávila 23, 1000-138 Lisbon</addr-line>
          ,
          <country country="PT">Portugal</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2022</year>
      </pub-date>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0002</lpage>
      <abstract>
        <p>BPMN is a specification language widely used by industry and researchers for business process modeling and execution. It defines how to articulate its concepts, but no method is provided on how to design the business process models. We address this problem proposing a tool (SemantifyingBPMN) that generates the BPMN models using a social interaction pattern grounded in DEMO, so that models can be discovered and enhanced with a bounded efort. The SemantifyingBPMN tool covers the patterns of: happy-flow, declination, rejection, revocation, customized view and composition of business transactions.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;BPMN</kwd>
        <kwd>business transaction</kwd>
        <kwd>DEMO</kwd>
        <kwd>model</kwd>
        <kwd>pattern</kwd>
        <kwd>social interaction</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>1. Introduction
A business process is a collection of events, activities, and decisions that brings value to the
customers of an organization. Business Process Model and Notation1 is the de facto standard
used by industry and researchers for business process modeling and execution. It is also available
under the standard ISO/IEC 19510:2013.</p>
      <p>
        As corroborated in the literature, BPMN defines very clearly how to articulate its concepts,
but do not provide a semantic for the consequent model. The meaning is usual expressed in
the natural language words that are used to name the activities, events, gateways, etc. [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ].
Accordingly with [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], “a language is considered to be formal if both its syntax and semantics
can be precisely defined. When the semantics is formally defined, sentences in the language then
have a unique interpretation”, this property does not hold in BPMN models. In fact, it is on the
modeler’s responsibility side to interpret the meaning of a given BPMN model. Conversely,
any other modeler could interpret the same model diferently, e.g., uBPMN [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] extends BPMN
with more notations to deal with ubiquitous computing technologies alleging that BPMN do
not ofer support for this domain. The study in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] corroborates this problem statement and
reinforces it when remote environments are imposed driving to more coordination problems,
e.g., due to of-shore teams allocation
      </p>
      <p>
        The business processes expressed by customers usual refers only to the “happy flow" and
disregards some other forms of exception handling [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. This option is not acceptable in business
process models under scenarios subject to uncertainty [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Therefore, real business processes
implementations usually relies on those incomplete semantic models, and then, this problem is
further propagated, and amplified, to the BPMN executable process models. The implications
of this problem within organizations are manifold (i) misunderstanding in business process
modeling, reflecting in implementation failures, and (ii) inconsistent design in the business
process models, reflecting in time consuming tasks for implementation, re-engineering and
knowledge dissemination due to an higher learning curve.
      </p>
      <p>
        To address this problem we propose a tool that enforces the social interaction pattern
available in the Enterprise Ontology [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] body of knowledge, specifically in the Design &amp;
Engineering Methodology for Organizations (DEMO) theory, onto BPMN models2. DEMO
Ψ -theory (Performing in Social Interaction-theory) is a communication-centric view proposal
that considers the people’ cooperation in enterprises, and is detailed in [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. This pattern-based
approach is also found in the literature. [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] shows that many publications discuss their patterns
in isolation, and no embracing pattern exists for the many business process modeling patterns
proposals available. We stress that our goal is to study solutions that improve the BPMN models
discover and enhancement using knowledge available from other semantic-based approach,
and not to change the BPMN language itself nor to add new construct to the language.
      </p>
      <p>This work was supported by national funds through Fundação para a Ciência e a Tecnologia
(FCT) with reference UIDB/50021/2020 (INESC-ID).
2. Mapping DEMO complete pattern onto BPMN models
To explain the mapping of DEMO onto BPMN a motivating example is used. Considering
a single business transaction of producing a product, at least two business actors need to be
considered: the transaction initiator (TI) and the transaction executor (TE). Considering that
both actors are located on two diferent organizations, then two BPMN pools are considered
(cf. Figure 1). When TI decides to request a product, the task of Request product is executed
resulting in (i) the emission of a communication act (C-act) with the purpose of Requesting a
product to the TE, and (ii) the creation of a new communication fact (C-fact) in the world. This
double outcome is repeated in all the business transaction steps, except on the Execute product
step where no C-act is expected but a P-act is. Figure 1 expands all the business transaction
steps included in a DEMO pattern, clarifying how the sequence of states originate a new P-fact
in the world. Whenever an actor role is expecting a C-act from the other, a BPMN intermediate
catching and an intermediate throwing message events are used. All the business transactions
respect this pattern, even when some acts or facts are not observable. In that situation, the acts
or facts are considered implicit in the execution of the business transaction.</p>
      <p>If a business actor disagrees with another, then a decision point is achieved.
2All the models presented in this paper are publicly available at https://github.com/SemantifyingBPMN/DEMO_
complete_pattern_in_BPMN
In case of a declination3, it is up to the TI to issue a new request; on
the contrary, in case of rejection, the TE needs to evaluate the rejection
arguments before deciding between stopping or re-declaring the product.
On the one hand, the C-act decline corresponds to an
impossibility of producing a product (e.g., due to stock
tscdphhoereouoclclroidtentasdhegse.eecrWflo)iwdhahean.entdnTodeth,ervmTeiegIrirgtueaeajpreTnsocIenttwihroteehnrceeTeCqiErvue-eaeecsscnettapdotiCoriso-fasnalpyscoromtofdtmcoaeecsedslttseaorcrfloipeclwihntw.ihasOiet/tihnhnoenar iiItttrrcsonaaonanT requestDoefcipdoreorddtheuercttyope No MrYeaeqksueenset?w ReDqueecdsidotepnrweohxdtautcto decline promise dCehcelacrkeproduct Agre swtoitpRhIsejpeNrcootdpurcotodku?ct Yes Acerpetjepcrtoductacept
pdUrenoldidveuercrstetadcnhpdercionkdgiustchptaettrhfPoe-nrfmaacetCda.-alIrfcetTaoIdfdyoreenxjeiosctttsaioginnreiteshweemiwthiotttrehldde,. ittrrscxcnaooanueTE Verpipfryooisdfueicbxtleeicsute DoekctloinperopdrNouodceu?Ycets Promiseproduct Ex(ePcruotdeupctrioodnu)ct NaroagArrDgugeuemrjeemceclYeatnwinerotestsintsh?pforroductargEruevmjaeelcuntiaottsnefor
is on the TE responsibility to decide if the rejection product(P-fact)
is valid or not. If so, a stop C-act is emitted and the
TI and TE process flow ends. Otherwise, the declare Figure 1: The DEMO standard pattern
C-act is re-emitted and the loop is restarted. Again, a of a transaction between two
possible deadlock could occur, and in the limit can only actors in BPMN.
be solved using litigation.</p>
      <p>
        For revocations (revoke a request, revoke a promise,
revoke a declare and revoke a accept) please refer to the full paper available at [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>
        In real environments, instead of a single business transaction, they are defined within the
scope of a network of actors and business transactions, e.g., a Payment transaction succeeds
a Production transaction. Therefore, the composition between them needs to be addressed.
Applied scenarios of these situations are detailed in the proof-of-concepts section. A composition
pattern occurs whenever an executor actor role assumes the responsibility of initiating another
transaction. The known transaction composition patterns are: request after execution (RaE)
and request after declare (RaD) (cf. explained in [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]).
2.1. Tool usage and performance
This DEMO mapping onto BPMN is implemented in an open-source software tool named as
SemantifyingBPMN and is publicly available online4. The required inputs of the software tool
are: (i) a list of actors, (ii) a list of transactions where the actors are involved and specifying the
result expected, and (iii) the transactions dependencies (RaP, RaE or RaD). The output is a BPMN
model file based in the available BPMN 2.0 XSD definition. To facilitate the rendering, each
business transaction view, can be configured as happy flow, or happy flow with declinations
and rejections, or the complete pattern. Figure 2 depicts some preliminary performance results
to generate BPMN models by the SemantifyingBPMN tool. The median of the operating time is
around 1 second to produce a BPMN model containing 1 business transaction. Yet, computing
time increases along with the increasing number of elements that are configured in TKView.
3A declination is considered in this paper as the formal refusal of a participant.
4https://github.com/SemantifyingBPMN/SemantifyingBPMN
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>R. M.</given-names>
            <surname>Dijkman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Dumas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Ouyang</surname>
          </string-name>
          ,
          <article-title>Semantics and analysis of business process models in BPMN, INFORMATION</article-title>
          AND SOFTWARE TECHNOLOGY
          <volume>50</volume>
          (
          <year>2008</year>
          )
          <fpage>1281</fpage>
          -
          <lpage>1294</lpage>
          . doi:{
          <volume>10</volume>
          . 1016/j.infsof.
          <year>2008</year>
          .
          <volume>02</volume>
          .006}.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>G.</given-names>
            <surname>Jošt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Huber</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Heričko</surname>
          </string-name>
          ,
          <string-name>
            <surname>G. Polančič,</surname>
          </string-name>
          <article-title>An empirical investigation of intuitive understandability of process diagrams</article-title>
          ,
          <source>Computer Standards &amp; Interfaces</source>
          <volume>48</volume>
          (
          <year>2016</year>
          )
          <fpage>90</fpage>
          -
          <lpage>111</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>H.</given-names>
            <surname>Mili</surname>
          </string-name>
          , G. Tremblay,
          <string-name>
            <given-names>G. B.</given-names>
            <surname>Jaoude</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Lefebvre</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Elabed</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G. E.</given-names>
            <surname>Boussaidi</surname>
          </string-name>
          ,
          <article-title>Business process modeling languages: Sorting through the alphabet soup</article-title>
          ,
          <source>ACM Comput. Surv</source>
          .
          <volume>43</volume>
          (
          <year>2010</year>
          ). URL: https://doi.org/10.1145/1824795.1824799. doi:
          <volume>10</volume>
          .1145/1824795.1824799.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>A.</given-names>
            <surname>Yousfi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Bauer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Saidi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. K.</given-names>
            <surname>Dey</surname>
          </string-name>
          ,
          <article-title>ubpmn: A bpmn extension for modeling ubiquitous business processes</article-title>
          ,
          <source>Information and Software Technology</source>
          <volume>74</volume>
          (
          <year>2016</year>
          )
          <fpage>55</fpage>
          -
          <lpage>68</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>E.</given-names>
            <surname>Poppe</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Brown</surname>
          </string-name>
          , J.
          <string-name>
            <surname>Recker</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Johnson</surname>
          </string-name>
          , I. Vanderfeesten,
          <article-title>Design and evaluation of virtual environments mechanisms to support remote collaboration on complex process diagrams</article-title>
          ,
          <source>INFORMATION SYSTEMS 66</source>
          (
          <year>2017</year>
          )
          <fpage>59</fpage>
          -
          <lpage>81</lpage>
          . doi:{
          <volume>10</volume>
          .1016/j.is.
          <year>2017</year>
          .
          <volume>01</volume>
          .004}.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>S.</given-names>
            <surname>Guerreiro</surname>
          </string-name>
          ,
          <string-name>
            <surname>S. J. van Kervel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Vasconcelos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Tribolet</surname>
          </string-name>
          ,
          <article-title>Executing enterprise dynamic systems control with the demo processor: the business transactions transition space validation</article-title>
          ,
          <source>in: Mediterranean Conference on Information Systems</source>
          , Springer,
          <year>2012</year>
          , pp.
          <fpage>97</fpage>
          -
          <lpage>112</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>A.</given-names>
            <surname>Jiménez-Ramírez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Weber</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.</given-names>
            <surname>Barba</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Del Valle</surname>
          </string-name>
          ,
          <article-title>Generating optimized configurable business process models in scenarios subject to uncertainty</article-title>
          ,
          <source>Information and Software Technology</source>
          <volume>57</volume>
          (
          <year>2015</year>
          )
          <fpage>571</fpage>
          -
          <lpage>594</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>J. L.</given-names>
            <surname>Dietz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. B.</given-names>
            <surname>Mulder</surname>
          </string-name>
          , Enterprise Ontology:
          <article-title>A Human-Centric Approach to Understanding the Essence of Organisation</article-title>
          , Springer Nature,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>S.</given-names>
            <surname>Guerreiro</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Sousa</surname>
          </string-name>
          ,
          <article-title>A framework to semantify bpmn models using demo business transaction pattern</article-title>
          ,
          <year>2020</year>
          . URL: https://arxiv.org/abs/
          <year>2012</year>
          .09557. doi:
          <volume>10</volume>
          .48550/ARXIV.
          <year>2012</year>
          .
          <volume>09557</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>M.</given-names>
            <surname>Fellmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Koschmider</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Laue</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Schoknecht</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Vetter</surname>
          </string-name>
          ,
          <article-title>Business process model patterns: state-of-the-art, research classification and taxonomy</article-title>
          ,
          <source>Business Process Management Journal</source>
          <volume>25</volume>
          (
          <year>2019</year>
          )
          <fpage>972</fpage>
          -
          <lpage>994</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>