<!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>Business Process Architecture Design Based on Domain Models (Extended Abstract)</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Fernanda Gonzalez-Lopez</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Ponti cia Universidad Catolica de Valpara so</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>This thesis proposes a novel Business Process Architecture (BPA) design method for overcoming limitations of currently available alternatives. The proposal { named domain-based BPA (dBPA) method { uses domain models as a starting point for building BPA models. The evaluation of the dBPA method revealed that it was perceived as useful and likely to be used in practice.</p>
      </abstract>
      <kwd-group>
        <kwd>Business Process Architecture Domain Model Method</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>The thesis focuses on Business Process Architecture (BPA) design. A BPA
consists of an organized overview of business processes and their relations. An
analysis of the literature of the BPA research eld revealed problems regarding BPA
design methods (see Sect.3) that ultimately challenge the most relevant
quality metrics { and predictors of use { of BPA methods, namely, ease of use and
usefulness.</p>
      <p>
        The aforementioned issues led to identifying the need for a new BPA design
method: the domain-based BPA (dBPA) method. The research, which followed
the Design Science Research (DSR) paradigm [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ], focused on the following
research goals:
      </p>
    </sec>
    <sec id="sec-2">
      <title>Models 2</title>
      <p>
        Data models represent information handled
by organizations. A domain model represents
the structure of a domain by showing its main
concepts and how they relate to one another
as classes and associations, respectively (see
Fig. 1). An object lifecycle (OLC), can be
built for a class to represent the dynamic
aspects of data, namely states and transitions.
Unlike traditional activity-centric approaches
to process modeling (e.g. [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]), the dBPA
method considers data as a rst-class citizen,
in line with the entity-centric paradigm [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ].
Accordingly, it is based on structure and
dynamic models of business entities (BEs), i.e.
real-world concepts handled by the
organization.
3
      </p>
      <sec id="sec-2-1">
        <title>Related</title>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Work 3</title>
      <p>
        The selection of a suitable architecture description language for the dBPA method
was based on requirements regarding abstract syntax and cognitive e ectiveness
of Business Process Model and Notation (BPMN) [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] and ArchiMate [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. The
assessment revealed that only ArchiMate complied with abstract syntax
requirements. However, to improve cognitive e ectiveness, its viewpoint mechanism was
used for de ning the BPA viewpoint, exempli ed in the BPA model in Fig. 2.
2 Materials reported in this chapter are partially published in [
        <xref ref-type="bibr" rid="ref3 ref7">7, 3</xref>
        ].
3 Materials reported in this chapter are partially published in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
    </sec>
    <sec id="sec-4">
      <title>Foundations 4</title>
      <p>The dBPA method is based on a number of
foundations. First, regarding the identi
cation of business entities and relationships:
{ Each domain model class de nes, at</p>
      <p>most, one business entity.
{ Each domain model association de nes
one or more relationships between the
OLCs of the partaking classes.</p>
      <p>Second, integration of structure and
dynamic data models involves specializing the
domain model classes with dynamic
hierarchies such that:
{ A dynamic hierarchy is built by
specializing the original class with sub-classes
that hold a bi-univocal relationship with
the OLC states.
{ The properties of the hierarchy are
de</p>
      <p>ned in a way that they are consistent
with the organization of OLC states.</p>
      <p>Third, formal de nitions used for the method include the concepts of:
association a, BPA model , business entity b, business process ', class c, data
dictionary dd, domain model w, and object lifecycle l.
6</p>
    </sec>
    <sec id="sec-5">
      <title>Method 5</title>
      <p>
        The dBPA method has six steps that are { generally speaking { sequential:
1. Prepare domain model. Some transformations are applied to the original
domain model to produce a semantically-equivalent domain model w where
all associations are directed and power types are replaced by hierarchies.
2. Identify business entities. The set of business entities B corresponds to
the set of all classes c 2 w that are not sub-classes.
3. Identify states of domain model classes. The set of states for each
business entity b 2 B is identi ed by using two sources of information: the
domain model w and its complementary information (e.g. its data dictionary
dd ), and domain expert knowledge.
4 Materials reported in this chapter are partially published in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
5 Materials reported in this chapter are partially published in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
4. Build OLC for each business entity. The OLC l for each business entity
b 2 B is built by using domain expert knowledge. In every OLC l, a
transition corresponds to one business process ' which changes the state of the
respective business entity. Also, each association a between domain model
classes is mapped into relations between the corresponding OLCs.
5. Build BPA model. The BPA model is built by mapping information in
each OLC l and in the domain model w.
6. Improve domain model expressiveness. The domain model w is
transformed to a semantically equivalent one by mapping OLC states to
subclasses of dynamic hierarchies.
7
      </p>
    </sec>
    <sec id="sec-6">
      <title>Evaluation 6</title>
      <p>
        The conceptual evaluation of the proposed method was done using a novel
framework based on the works by [
        <xref ref-type="bibr" rid="ref15 ref9">9, 15</xref>
        ]. This highlighted some di erentiating aspects
of the proposal. A user study was conducted for the empirical evaluation of the
dBPA method based on the Method Evaluation Model (MEM) [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. The study
assessed the use of the dBPA method and another BPA design method (i.e.
BPTrends Associates [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]) in terms of ease of use, usability, and intention to use
with promising results in favor of the proposal.
8
      </p>
      <sec id="sec-6-1">
        <title>Conclusions</title>
        <p>
          G1 (Artifact design): The dBPA method was designed for overcoming
issues of currently available BPA design methods. The reuse of structured
business knowledge was implemented as using domain models as an input for the
method. The method also considers four types of process relations that, though
mentioned in the literature, are rarely considered together in BPA design
methods. Including them allows building more complete BPA models. The use of an
industry-standard language was done by proposing an ArchiMate viewpoint that
would improve cognitive e ectiveness of the resulting BPA models. The proposed
method has some limitations that could be addressed in future research: (i) it
works with a simpli ed version of the domain model; (ii) it assumes that the
granularity of all OLC transitions is such that it can constitute one business
process; and (iii) it is domain model dependent. Future works include: partial
automation of the method, and development of tools for BPA analysis.
G2 (Instrument design): Two instruments were tailored for evaluation of the
proposed method. The framework for qualitative analysis was found useful for
the description, evaluation, and comparison of (other) BPA design methods at
a conceptual level. Future lines of work might include validating this framework
with a panel of experts. An instantiation of the MEM was successfully used
for quantitative analysis. Future research could include improving some issues
6 Materials reported in this chapter are partially published in [
          <xref ref-type="bibr" rid="ref6 ref8">6, 8</xref>
          ].
inherited from the MEM, as well as some issues of the instantiation. Also, the
use of the MEM could be further developed and tested.
        </p>
        <p>G3 (Knowledge): The evaluation provided signi cant evidence that the
proposal was perceived as useful and not easy to use. The user study also provided
preliminary evidence that the proposed method is an improvement regarding
ease of use, usefulness, and intention to use. These results are consistent with
the main design decisions of the proposed method. In the end, however, further
research is needed to gather signi cant evidence.</p>
        <p>G4 (Prediction): In terms of adoption in practice, the study provided
preliminary evidence in favor of the proposal. Again, future research is needed in
this regard. Also, the study provided signi cant evidence stating that usefulness
seems to be the main predictor of adoption in practice followed by ease of use.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Gonzalez-Lopez</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Research proposal for business process architecture from domain models</article-title>
          .
          <source>In: Doctoral Consortium</source>
          ,
          <string-name>
            <surname>BPM</surname>
          </string-name>
          <year>2016</year>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Gonzalez-Lopez</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bustos</surname>
          </string-name>
          , G.:
          <article-title>Integration of entity-centric models for business processes</article-title>
          .
          <source>In: 2nd Workshop STI</source>
          , Chillan (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Gonzalez-Lopez</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bustos</surname>
          </string-name>
          , G.:
          <article-title>Business process architecture in the context of enterprise architecture: a survey</article-title>
          .
          <source>In: 8th ICPR { Americas</source>
          <year>2016</year>
          ,
          <article-title>Valpara so (</article-title>
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Gonzalez-Lopez</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bustos</surname>
          </string-name>
          , G.:
          <article-title>Business process architecture baselines from domain models</article-title>
          .
          <source>In: BPM</source>
          <year>2016</year>
          ,
          <article-title>LNBIP 281</article-title>
          . pp.
          <volume>118</volume>
          {{130. Springer (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Gonzalez-Lopez</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bustos</surname>
          </string-name>
          , G.:
          <article-title>Business process architecture design methodologies { a literature review</article-title>
          .
          <source>Bus. Process Manag. J</source>
          .
          <volume>25</volume>
          (
          <issue>6</issue>
          ),
          <volume>1317</volume>
          {
          <fpage>1334</fpage>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Gonzalez-Lopez</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bustos</surname>
          </string-name>
          , G.:
          <article-title>Evaluating methodologies for business process architecture design { a pilot study</article-title>
          .
          <source>In: ZEUS</source>
          <year>2019</year>
          , CEUR
          <volume>2339</volume>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Gonzalez-Lopez</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bustos</surname>
          </string-name>
          , G.:
          <article-title>Integration of business process architectures within enterprise architecture approaches: A literature review</article-title>
          .
          <source>Eng. Manag. J</source>
          .
          <volume>31</volume>
          (
          <issue>2</issue>
          ),
          <volume>127</volume>
          {
          <fpage>140</fpage>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Gonzalez-Lopez</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pufahl</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>A landscape for case models</article-title>
          .
          <source>In: BPMDS</source>
          <year>2019</year>
          ,
          <article-title>LNBIP 352</article-title>
          . pp.
          <volume>87</volume>
          {
          <fpage>102</fpage>
          . Springer (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Green</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ould</surname>
            ,
            <given-names>M.A.</given-names>
          </string-name>
          :
          <article-title>A framework for classifying and evaluating process architecture methods</article-title>
          .
          <source>Softw. Process Improv. Pract</source>
          .
          <volume>10</volume>
          (
          <issue>4</issue>
          ),
          <volume>415</volume>
          {
          <fpage>425</fpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Harmon</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Business process change: a business process management guide for managers and process professionals</article-title>
          .
          <source>Elsevier</source>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Kitchenham</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Charters</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Guidelines for performing systematic literature reviews in software engineering Version 2</article-title>
          .3 (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12. Moody, D.L.:
          <article-title>The method evaluation model: A theoretical model for validating information systems design methods</article-title>
          .
          <source>In: 11th ECIS</source>
          . pp.
          <volume>1327</volume>
          {
          <issue>1336</issue>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Nigam</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Caswell</surname>
            ,
            <given-names>N.S.:</given-names>
          </string-name>
          <article-title>Business artifacts: An approach to operational speci - cation</article-title>
          .
          <source>IBM Syst. J</source>
          .
          <volume>42</volume>
          (
          <issue>3</issue>
          ),
          <volume>428</volume>
          {
          <fpage>445</fpage>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14. OMG:
          <article-title>Business Process Model and Notation (BPMN): Version 2</article-title>
          .
          <fpage>0</fpage>
          . (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Pesantes</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mitre</surname>
            ,
            <given-names>H.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lemus</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Evaluation of process architecture design methods</article-title>
          .
          <source>In: 13th ICCSA, Ho Chi Minh City</source>
          . pp.
          <volume>144</volume>
          {
          <issue>159</issue>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16. The Open Group:
          <article-title>ArchiMate R 3.0.1 speci cation (</article-title>
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Wieringa</surname>
          </string-name>
          , R.:
          <article-title>Design science methodology for information systems</article-title>
          and software engineering. Springer (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>