<!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>From Discovery to Redesign: Leveraging Activity Relationships in Business Process Transformation</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Kerstin Andree</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Technical University of Munich, School of Computation, Information and Technology</institution>
          ,
          <addr-line>Bildungscampus 2, 74076 Heilbronn</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Organizations must regularly adapt their business processes in response to evolving goals, norms, or regulations. Redesign ideas and change operations are typically derived from as-is process models discovered from execution data via automated process discovery. A crucial but often overlooked factor in this context is the choice of modeling language: if it does not match the process's characteristics, particularly its level of structuredness, the resulting model may become unnecessarily complex and harder to interpret, or too abstract, missing relevant control-flow details. Moreover, Business Process Redesign (BPR) lacks automated support in the implementation of change operations. Structural and contextual consequences are not taken into account when modifying process models. To address the challenges of appropriate process representation and automated, preventive BPR support, we conduct a doctoral research project. We plan to develop an IT artifact that supports process classification and representation according to the level of structuredness, and the automated implementation of change operations, including their assessment regarding structural and contextual consequences. This proposal outlines progress so far, the overall research method and approach, first outcomes and remaining steps, as well as its relation to the state-of-the-art literature.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Process Discovery</kwd>
        <kwd>Process Classification</kwd>
        <kwd>Business Process Redesign</kwd>
        <kwd>Activity Relationships</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction and Motivation</title>
      <p>
        Business processes are subject to constant change [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]—whether due to legislative developments,
shifts in business goals toward sustainability objectives, or the pursuit of performance optimizations.
Organizations therefore need to regularly engage in Business Process Redesign (BPR). A prerequisite for any
redesign initiative is a solid understanding of the as-is situation [2, Ch.8]. Traditionally, this understanding
was obtained through interviews and manual modeling, which are costly and often incomplete.
      </p>
      <p>
        Automated Process Discovery addresses this challenge by extracting business process models directly
from event logs [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. These models provide an evidence-based baseline that increases transparency and
that can subsequently be used as input for BPR [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. However, their usefulness depends strongly on the
modeling language in which they are expressed. Imperative modeling languages, such as Business Process
Model and Notation (BPMN), prescribe the control flow of a process while declarative languages, such
as the ConDec language [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] used for Declare [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], allow execution flexibility within defined constraints.
The choice depends on the process’s structuredness: highly structured processes with predictable flows
suit imperative models, while loosely structured or knowledge-intensive processes are better captured
declaratively [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Especially for BPR, where process models form the basis for generating redesign ideas,
selecting a modeling language that reflects the appropriate degree of structuredness is fundamental
to ensuring that redesign initiatives are grounded in process reality.
      </p>
      <p>
        However, for redesign decisions to be efective, process models alone are not enough: contextual
information about activity relationships contributes significantly to the success of BPR tasks as it supports
preventive BPR [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. Risks and consequences can be assessed before actual implementation. Identifying
nonviolable relationships is further considered important in the domain of model repair [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. However,
contextual information for BPR has so far been extracted and annotated manually; automated support is missing.
      </p>
      <p>
        In the past years, several approaches were introduced to support the implementation of BPR tasks,
ranging from manual approaches, such as the change patterns [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] and best practices for BPR [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], to
tools ofering automated support [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] aiming at optimizing performance and eficiency. Nevertheless,
automated support for BPR is still one of the biggest challenges in Business Process Management
(BPM) [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. Transformation from the as-is to the to-be situation is often referred to as the ATAMO
(And Then A Miracle Occurred) principle [2, Ch.8]. An overview of structural consequences is missing.
Moreover, the scattered definition of change operations further hinders automated BPR support. For
example, change operations found in the field of process model repair [
        <xref ref-type="bibr" rid="ref12 ref13">12, 13</xref>
        ] have similar semantics
as in BPR but are named diferently, making efective BPR more challenging.
      </p>
      <p>In summary, we identify three core challenges: (1) appropriate process representation according to
its level of structuredness, (2) integration of contextual information for change operation assessment,
and (3) automated support for change operation implementation explaining structural consequences.
Based on these observations, the proposed PhD research project targets the following research questions:
RQ1: How can we automatically identify the most appropriate process representation for a given
process, based on the characteristics observed in its event log?
RQ2: How can change operations be formalized to modify process behavior at the level of activity
relationships?
RQ3: How can we support the assessment of change operations in terms of their feasibility and impact?</p>
      <p>We propose the development of an IT artifact that integrates structuredness-aware process discovery,
addressing the challenge of finding the most appropriate process representation, with automated support
for business process redesign. Users provide an event log as input, from which a process model is
automatically generated using the most suitable modeling language. Based on this model, users can
derive change operations, which serve as input for the redesign phase. Before applying change operations,
a pre-assessment is conducted to evaluate their violability. Subsequently, the structural consequences
of the selected change operations are made explicit, enabling transparent process transformation.</p>
      <p>
        We follow the design science research approach [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] and use the methodology of algorithm
engineering [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] to formalize the described research problems for algorithm development.
      </p>
      <p>The remainder of this doctoral research proposal is structured as follows. Research methods are
presented in section 2. Section 3 introduces the overall research approach. Section 4 presents first results
and the roadmap of the project. Related work is discussed in section 5, and section 6 concludes.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Methodology</title>
      <p>
        From a methodological point of view, we are following the Design Science Research (DSR) methodology [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]
to develop the proposed IT artifact. We include a snowballing literature review approach [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] to identify
change operations for redesigning process behavior (RQ2). Furthermore, we use the hermeneutic
approach for a literature review [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] to create an understanding of change operation assessment across
diferent research fields in the area of BPM (RQ3). This combined literature review approach allows
for a thorough definition of solution objectives and improved understanding of the research problem.
      </p>
      <p>
        Based on the theoretical background, we then follow the methodology of algorithm engineering [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]
for problem formalization (i.e., formalization of change operations and process structuredness) and
algorithm design. The development of the proposed artifact is conducted in two phases. First, we focus
on RQ1 to find the appropriate representation of a given process. Its output is then used for change
operation implementation being developed in a second step. By following the principles of test-driven
development [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ], we iteratively incorporate increasing levels of complexity.
      </p>
      <p>
        Process classification will be evaluated using both real-world and synthetic event log data, with an
expert survey serving as the ground truth for comparison. Following the principles of technical action
research [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ], we collect change operations from a real-world use case and implement them with the
proposed IT artifact to assess its feasibility.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Approach</title>
      <p>We use the activity relationships matrix [20] as the core artifact to define a relationship for each pair of
activities. It distinguishes between temporal dependency (i.e., the order in which activities occur during process
execution) and existential dependency (i.e., how the occurrence of one activity depends on the occurrence of
another). This intermediate process representation enables us to capture more process details compared to
abstracted process models. Additionally, it provides a comprehensive analytical framework for examining
process behavior and can be translated into various modeling languages such as BPMN or Declare.</p>
      <p>
        Figure 1 shows how the matrix is used in our overall approach. Based on event logs, we discover the
matrix and enrich it with contextual information such as explanatory rationales [
        <xref ref-type="bibr" rid="ref8">8, 21</xref>
        ] to understand
the background and motivation behind each process relation. Additionally, we analyze the ratios of
relationship types to heuristically classify the process regarding its structuredness and suggest an
appropriate modeling language for visualization, since the matrix itself is used for computational analysis
only. It can then be translated into visual process models to make the process accessible to stakeholders.
      </p>
      <p>Based on the process model, stakeholders can generate redesign ideas, which are formalized into
concrete change operations. By implementing these change operations within the matrix, we can
determine structural consequences, i.e., which relationships need to be adjusted so that the process is
sound and consistent in itself.</p>
      <p>Furthermore, using the contextual information stored for each relation, we can perform an initial
assessment of whether a change operation is feasible. By enforcing logical constraints on relations,
we can assess whether a change operation is permissible, thus enabling stakeholders to perform more
efective preventive redesign. Moreover, we are able to assess change operations regarding organizational
risks. If, for example, a change operation afects a relationship that is based on a governmental law,
the consequences might be diferent compared to relationships that exist based on a best practice. Our
approach can diferentiate such cases.</p>
      <p>Contextual Info
Relationship</p>
      <p>Discovery</p>
      <p>- (&lt;,&lt;-) (&lt;,&lt;-&gt;)
(&gt;,&lt;-) - (&lt;,&lt;-)
(&gt;,&lt;-&gt;) (&gt;,&lt;-)</p>
      <sec id="sec-3-1">
        <title>Activity Relationship Matrix</title>
        <p>All relationships between any pair
of activities</p>
        <p>Violability Assessment
Structural Consequences</p>
      </sec>
      <sec id="sec-3-2">
        <title>Process Classification</title>
        <p>Choose appropriate process representation
Translation from Matrix to Process Model
Change
Operation</p>
      </sec>
      <sec id="sec-3-3">
        <title>Process</title>
      </sec>
      <sec id="sec-3-4">
        <title>Stakeholders</title>
      </sec>
      <sec id="sec-3-5">
        <title>Business Process</title>
      </sec>
      <sec id="sec-3-6">
        <title>Model</title>
        <p>Assessment of Change Operation</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Results and Roadmap</title>
      <p>This section summarizes the achieved outcomes so far and outlines the remaining steps to be addressed
in the dissertation project. Table 1 provides an overview of the research questions, the assigned work
packages, and the current status of achievement.</p>
      <p>RQ
RQ1
RQ2
RQ3</p>
      <p>Work Package
WP1 Relationships Discovery: Based on event log data, an activity relationships matrix should
be discovered and stored in an adequate file format.</p>
      <p>WP2 Process Classification: Algorithm development to assign a modeling language to an event
log based on structuredness analysis.</p>
      <p>WP3 Matrix To Process Model: Translate the activity relationships matrix to diferent types of
process models, e.g., Declare and BPMN.</p>
      <p>WP4 Tool Development: Unified modeling environment for multiple modeling languages of
diferent types and UI development for process classification.</p>
      <p>WP5 Change Operation Review: Snowballing change operations from literature.</p>
      <p>WP6 Change Operation Formalization: Change operations are formalized in terms of activity
relationships notation, user input, and output.</p>
      <p>WP7 Change Operation Assessment: Development of a framework to assess change operations
to support preventive BPR.</p>
      <p>WP8 Extracting Contextual Information: Exploration of methods to extract required contextual
information (LLM-based approach, questionnaires, context-aware modeling)
WP9 Change Operation Implementation: Implementation of change operation on a structural
level, including violability check.</p>
      <p>WP10 Final Integration and Testing: Tool development and case study.
✓
✓
◦
✓
✓
✓
✓
◦
✓
◦
[22]
[23]
[22]
[21]
[24]</p>
      <p>We have introduced a discovery algorithm to extract an activity relationships matrix as defined in [ 20]
based on a given event log (WP1) [22]. To improve readability, we chose the YAML format to store the
required information for each activity relationship in the process. Discovered matrices can be used for
automated process classification according to the level of structuredness (WP2) [23] 1.</p>
      <p>The proposed classification algorithm already outputs the most appropriate modeling language and
automatically translates loosely structured processes from activity relationship matrices to Declare2
(WP3). We plan to add the translation to BPMN by the end of October 2025.</p>
      <p>Regarding tool support (WP4), we have implemented a unified, interactive modeling environment for
Declare and BPMN process models that is integrated in a UI that supports users in process classification.</p>
      <p>Moreover, WP5 and WP6 can be considered complete. For the resulting list of change operations we
got from the snowballing literature review, we have formalized each change operation. Moreover, change
operations, including a pre-assessment of locked relationships, are implemented on a matrix level (WP9).
We are currently finalizing the tool integration and plan to complete the evaluation by November 2025.</p>
      <p>Regarding WP7, we have introduced a conceptual model for business process redesign that defines
relevant concepts that need to be taken into account when assessing change operations [21]. It combines
diferent areas of BPM to specify the motivational background of activity relationships, captured by
explanatory rationales, and the connection to diferent types of risks and consequences. For the extraction
of explanatory rationales (WP8), we have compared diferent prompting techniques in combination
with diferent Large Language Models (LLMs) 3 and evaluated the efectiveness of the extraction using
questionnaires. We plan do implement a prototypical context-aware process modeling environment
and compare all three approaches regarding their feasibility and quality of results by spring 2025.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Related Work</title>
      <p>Automated Discovery of Intermediate Process Representations. Intermediate process
representations are used in process discovery to extract general behavior patterns from event logs. The
footprint matrix is used by the  algorithms [25, 26, 27] and captures relationships, such as causality and
direct succession. Directly-follows graphs (DFG) used in the Heuristics Miner [28], Inductive Miner [29],
1The classification algorithm is available on GitHub: https://github.com/INSM-TUM/automated-process-classification
2The translation to Declare is available on GitHub: https://github.com/INSM-TUM/event-log-to-declare-json
3The results will be published and presented at the international conference on Wirtschaftsinformatik 2025 (WI25).
and Split Miner [30] capture only direct temporal dependencies, often with heuristics for noise handling.
LTL formulae representations are used in declarative discovery [31, 32] and verification [ 33]. Komatsu
and Horita [34] introduce a method to discover LTL formulae directly from event logs, however, their
approach is limited by relying on a pre-defined subset of traces as input.</p>
      <p>Intermediate representations usually do not diferentiate between diferent types of existential and
temporal dependencies. The activity relationships matrix, however, captures a richer set of dependency
types, making it useful for further applications beyond process discovery, such as classification based
on structuredness and automated redesign support. Moreover, it allows taking the complete event log
as an input for LTL discovery.</p>
      <p>Process Classification and Appropriate Process Representation. Process classification based
on event log data was first introduced with discovery algorithms for hybrid models [ 35]. These
approaches [36, 37, 38] aim to identify structured and unstructured parts without classifying the entire
event log. Our algorithm classifies structuredness based on relationship types and maps the result to
appropriate modeling languages for adequate representation instead of using hybrid approaches.</p>
      <p>
        For appropriate process representation, most approaches focus on the user and organizational
context [39, 40, 41]. Other criteria include long-term usability and maintainability of process models [42],
tool support [43], or specific business process perspectives [ 44]. However, these approaches largely
ignore event log data. Incorporating process execution data is essential, as the chosen language should
reflect both representational goals and the process’s inherent characteristics, such as structuredness [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
Business Process Redesign. In the context of business process redesign, various change operations
were presented in literature [
        <xref ref-type="bibr" rid="ref1 ref4">1, 45, 46, 4</xref>
        ]. Moreover, the area of business process repair additionally
introduces change operations to modify process behavior [
        <xref ref-type="bibr" rid="ref12 ref13 ref9">12, 9, 13</xref>
        ]. However, there is no unified and
formalized overview of change operations. Authors use diferent terms and concepts, making it dificult
for automated support for change operation implementation.
      </p>
      <p>
        Looking at tools, Fehrer et al. [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] outline a four-step assisted BPR approach for BPMN diagrams.
Simulation experiments are used to assess the impact of the applied change operations in terms of
performance. Structural and contextual consequences, however, are neglected. The change patterns
introduced by Weber et al. [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] also support redesigners in design and run-time, but lack change assessment.
      </p>
    </sec>
    <sec id="sec-6">
      <title>6. Discussion and Conclusion</title>
      <p>
        While the proposed research project addresses the three core problems of appropriate process
representation, automated support for business process redesign, and change operation assessment, it comes with
limitations. First, we focus on changing process behavior, thus excluding the operational view on BPR [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]
to better scope the overall project. Second, the view on relationships is still limited. Even though we
include contextual process information, such as explanatory rationales, risks, and consequences, the
approach lacks a data perspective on the process. Data constraints are currently considered as generic,
non-violable constraints that can be locked before performing BPR. Furthermore, the activity relationships
matrix introduces a limitation with regard to runtime. While the size of the event log afects relationship
discovery, the implementation of change operations slows down as the number of activities increases.
      </p>
      <p>Nevertheless, we believe that our approach contributes towards a more detailed understanding of
activity relationships and their motivational background, supporting automated, preventive business
process redesign.</p>
    </sec>
    <sec id="sec-7">
      <title>Declaration on Generative AI</title>
      <p>During the preparation of this work, the author used the unpaid version of ChatGPT in order to improve
the structure of sentences and shorten paragraphs. After using this tool, the author reviewed and edited
the content as needed and takes full responsibility for the publication’s content.</p>
      <p>Springer, Germany, 2014. doi:10.1007/978-3-662-43839-8.
[20] K. Andree, D. Bano, M. Weske, A closer look at activity relationships to improve business process
redesign, Softw. Syst. Model. 24 (2025) 69–86. doi:10.1007/S10270-024-01234-5.
[21] K. Andree, L. Pufahl, Am I allowed to change an activity relationship? - A metamodel for
behavioral business process redesign, in: M. Kaczmarek-Heß, K. Rosenthal, M. Suchánek, M. M.
da Silva, H. A. Proper, M. Schnellmann (Eds.), Enterprise Design, Operations, and Computing.
EDOC 2024 Workshops - iRESEARCH, MIDas4CS, Doctoral Consortium, Joint CBI-EDOC Forum
and Other Joint CBI-EDOC Events, Vienna, Austria, September 10-13, 2024, Revised Selected
Papers, volume 537 of Lecture Notes in Business Information Processing, Springer, 2024, pp. 18–35.
doi:10.1007/978-3-031-79059-1\_2.
[22] K. Andree, I. Kuzmin, L. Pufahl, Decoupling process abstraction levels: Discovering an activity
relationships matrix (unpublished). ResearchGate-Preprint available.
[23] K. Andree, I. Kuzmin, L. Pufahl, Automated process classification (unpublished).
ResearchGate</p>
      <p>Preprint available.
[24] K. Andree, Z. Touqan, L. Bein, L. Pufahl, Extracting explanatory rationales of activity relationships
using llms – a comparative analysis, in: Proceedings of the International Conference of
Wirtschaftsinformatik (WI25), 2025. Accepted paper.
[25] W. M. P. van der Aalst, T. Weijters, L. Maruster, Workflow mining: Discovering process models
from event logs, IEEE Trans. Knowl. Data Eng. 16 (2004) 1128–1142.
[26] A. K. A. de Medeiros, B. F. van Dongen, W. M. P. van der Aalst, A. J. M. M. Weijters, Process mining
for ubiquitous mobile systems: An overview and a concrete algorithm, in: L. Baresi, S. Dustdar,
H. C. Gall, M. Matera (Eds.), Ubiquitous Mobile Information and Collaboration Systems, Second
CAiSE Workshop, UMICS 2004, Riga, Latvia, June 7-8, 2004, Revised Selected Papers, volume 3272
of LNCS, Springer, 2004, pp. 151–165.
[27] L. Wen, W. M. P. van der Aalst, J. Wang, J. Sun, Mining process models with non-free-choice
constructs, Data Min. Knowl. Discov. 15 (2007) 145–180.
[28] A. Augusto, R. Conforti, M. Dumas, M. L. Rosa, G. Bruno, Automated discovery of structured process
models from event logs: The discover-and-structure approach, Data Knowl. Eng. 117 (2018) 373–392.
[29] S. J. J. Leemans, D. Fahland, W. M. P. van der Aalst, Discovering block-structured process models
from event logs - A constructive approach, in: J. M. Colom, J. Desel (Eds.), Application and Theory
of Petri Nets and Concurrency - 34th International Conference, PETRI NETS 2013, Milan, Italy,
June 24-28, 2013. Proceedings, volume 7927 of LNCS, Springer, 2013, pp. 311–329.
[30] A. Augusto, R. Conforti, M. Dumas, M. L. Rosa, Split miner: Discovering accurate and simple
business process models from event logs, in: V. Raghavan, S. Aluru, G. Karypis, L. Miele, X. Wu
(Eds.), 2017 IEEE International Conference on Data Mining, ICDM 2017, New Orleans, LA, USA,
November 18-21, 2017, IEEE Computer Society, 2017, pp. 1–10.
[31] F. M. Maggi, A. J. Mooij, W. M. P. van der Aalst, User-guided discovery of declarative process
models, in: Proceedings of the IEEE Symposium on Computational Intelligence and Data Mining,
CIDM 2011, part of the IEEE Symposium Series on Computational Intelligence 2011, April 11-15,
2011, Paris, France, IEEE, 2011, pp. 192–199.
[32] F. M. Maggi, R. P. J. C. Bose, W. M. P. van der Aalst, Eficient discovery of understandable declarative
process models from event logs, in: J. Ralyté, X. Franch, S. Brinkkemper, S. Wrycza (Eds.), Advanced
Information Systems Engineering - 24th International Conference, CAiSE 2012, Gdansk, Poland,
June 25-29, 2012. Proceedings, volume 7328 of LNCS, Springer, 2012, pp. 270–285.
[33] W. M. P. van der Aalst, H. T. de Beer, B. F. van Dongen, Process mining and verification of
properties: An approach based on temporal logic, in: R. Meersman, Z. Tari, M. Hacid, J. Mylopoulos,
B. Pernici, Ö. Babaoglu, H. Jacobsen, J. P. Loyall, M. Kifer, S. Spaccapietra (Eds.), OTM Confederated
International Conferences CoopIS, DOA, and ODBASE 2005, Agia Napa, Cyprus, October 31
November 4, 2005, Proceedings, Part I, volume 3760 of LNCS, Springer, 2005, pp. 130–147.
[34] K. Komatsu, H. Horita, Generating ltl formulas for process mining by example of trace, Journal
of Data Science and Intelligent Systems (2024).
[35] T. Slaats, Declarative and hybrid process discovery: Recent advances and open challenges, J. Data</p>
      <p>Semant. 9 (2020) 3–20.
[36] F. M. Maggi, T. Slaats, H. A. Reijers, The automated discovery of hybrid processes, in: BPM - 12th
International Conference, Haifa, Israel, September 7-11, 2014. Proceedings, volume 8659 of LNCS,
Springer, 2014, pp. 392–399.
[37] J. D. Smedt, J. D. Weerdt, J. Vanthienen, Fusion miner: Process discovery for mixed-paradigm
models, Decis. Support Syst. 77 (2015) 123–136.
[38] D. M. M. Schunselaar, T. Slaats, F. M. Maggi, H. A. Reijers, W. M. P. van der Aalst, Mining hybrid
business process models: A quest for better precision, in: Business Information Systems - 21st
International Conference, BIS 2018, Berlin, Germany, July 18-20, 2018, Proceedings, volume 320
of LNBIP, Springer, 2018, pp. 190–205.
[39] S. Farshidi, I. B. Kwantes, S. Jansen, Business process modeling language selection for research
modelers, Softw. Syst. Model. 23 (2024) 137–162.
[40] M. A. Abdel-Fattah, A. E. Khedr, Y. N. Aldeen, An evaluation framework for business process
modeling techniques, International Journal of Computer Science and Information Security (IJCSIS)
15 (2017) 382–392.
[41] L. Aldin, S. De Cesare, A comparative analysis of business process modelling techniques (2009).
[42] G. Reggio, M. Leotta, F. Ricca, E. Astesiano, Business process modelling: Five styles and a method to
choose the most suitable one, in: Proceedings of the Second Edition of the International Workshop
EESSMod, 2012, pp. 1–6.
[43] K. Guizani, S. A. Ghannouchi, An approach for selecting a business process modeling language
that best meets the requirements of a modeler, Procedia Computer Science 181 (2021) 843–851.
[44] H. Mili, G. Tremblay, G. B. Jaoude, É. Lefebvre, L. Elabed, G. E. Boussaidi, Business process modeling
languages: Sorting through the alphabet soup, ACM Computing Surveys (CSUR) 43 (2010) 1–56.
[45] S. Groß, K. Stelzl, T. Grisold, J. Mendling, M. Röglinger, J. vom Brocke, The business process design
space for exploring process redesign alternatives, Bus. Process. Manag. J. 27 (2021) 25–56.
[46] G. Zellner, Towards a framework for identifying business process redesign patterns, Bus. Process.</p>
      <p>Manag. J. 19 (2013) 600–623.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>S. L.</given-names>
            <surname>Mansar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. A.</given-names>
            <surname>Reijers</surname>
          </string-name>
          ,
          <article-title>Best practices in business process redesign: use and impact</article-title>
          , Bus. Process. Manag. J.
          <volume>13</volume>
          (
          <year>2007</year>
          )
          <fpage>193</fpage>
          -
          <lpage>213</lpage>
          . doi:
          <volume>10</volume>
          .1108/14637150710740455.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>M.</given-names>
            <surname>Dumas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. L.</given-names>
            <surname>Rosa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Mendling</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. A.</given-names>
            <surname>Reijers</surname>
          </string-name>
          , Fundamentals of Business Process Management,
          <source>Second Edition</source>
          , Springer,
          <year>2018</year>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>662</fpage>
          -56509-4.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>W. M. P. van der Aalst</surname>
          </string-name>
          ,
          <article-title>Foundations of process discovery</article-title>
          , in: W.
          <string-name>
            <surname>M. P. van der Aalst</surname>
          </string-name>
          , J. Carmona (Eds.),
          <source>Process Mining Handbook</source>
          , volume
          <volume>448</volume>
          <source>of LNBIP</source>
          , Springer,
          <year>2022</year>
          , pp.
          <fpage>37</fpage>
          -
          <lpage>75</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>B.</given-names>
            <surname>Weber</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Reichert</surname>
          </string-name>
          , S. Rinderle-Ma,
          <article-title>Change patterns and change support features - enhancing flexibility in process-aware information systems</article-title>
          ,
          <source>Data Knowl. Eng</source>
          .
          <volume>66</volume>
          (
          <year>2008</year>
          )
          <fpage>438</fpage>
          -
          <lpage>466</lpage>
          . doi:
          <volume>10</volume>
          .1016/J.DATAK.
          <year>2008</year>
          .
          <volume>05</volume>
          .001.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>M.</given-names>
            <surname>Montali</surname>
          </string-name>
          ,
          <article-title>The condec language, Specification and Verification of Declarative Open Interaction Models: A Logic-Based Approach (</article-title>
          <year>2010</year>
          )
          <fpage>47</fpage>
          -
          <lpage>75</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>M.</given-names>
            <surname>Pesic</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Schonenberg</surname>
          </string-name>
          ,
          <string-name>
            <surname>W. M. Van der Aalst</surname>
          </string-name>
          ,
          <article-title>Declare: Full support for loosely-structured processes, in: 11th IEEE international enterprise distributed object computing conference (EDOC 2007)</article-title>
          , IEEE,
          <year>2007</year>
          , pp.
          <fpage>287</fpage>
          -
          <lpage>287</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>C. D.</given-names>
            <surname>Ciccio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Marrella</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Russo</surname>
          </string-name>
          ,
          <article-title>Knowledge-intensive processes: Characteristics, requirements and analysis of contemporary approaches</article-title>
          ,
          <source>J. Data Semant</source>
          .
          <volume>4</volume>
          (
          <year>2015</year>
          )
          <fpage>29</fpage>
          -
          <lpage>57</lpage>
          . doi:
          <volume>10</volume>
          .1007/S13740-014-0038-4.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>G.</given-names>
            <surname>Adamo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. D.</given-names>
            <surname>Francescomarino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Ghidini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. M.</given-names>
            <surname>Maggi</surname>
          </string-name>
          ,
          <article-title>Beyond arrows in process models: A user study on activity dependences and their rationales</article-title>
          ,
          <source>Inf. Syst</source>
          .
          <volume>100</volume>
          (
          <year>2021</year>
          )
          <article-title>101762</article-title>
          . doi:
          <volume>10</volume>
          .1016/J.IS.
          <year>2021</year>
          .
          <volume>101762</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>K.</given-names>
            <surname>Revoredo</surname>
          </string-name>
          ,
          <article-title>On the use of domain knowledge for process model repair</article-title>
          ,
          <source>Software and Systems Modeling</source>
          <volume>22</volume>
          (
          <year>2023</year>
          )
          <fpage>1099</fpage>
          -
          <lpage>1111</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>T.</given-names>
            <surname>Fehrer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. A.</given-names>
            <surname>Fischer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. J. J.</given-names>
            <surname>Leemans</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Röglinger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. T.</given-names>
            <surname>Wynn</surname>
          </string-name>
          ,
          <article-title>An assisted approach to business process redesign</article-title>
          ,
          <source>Decis. Support Syst</source>
          .
          <volume>156</volume>
          (
          <year>2022</year>
          )
          <article-title>113749</article-title>
          . doi:
          <volume>10</volume>
          .1016/J.DSS.
          <year>2022</year>
          .
          <volume>113749</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>I.</given-names>
            <surname>Beerepoot</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. D.</given-names>
            <surname>Ciccio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. A.</given-names>
            <surname>Reijers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Rinderle-Ma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Bandara</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Burattin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Calvanese</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Chen</surname>
          </string-name>
          , I. Cohen,
          <string-name>
            <given-names>B.</given-names>
            <surname>Depaire</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G. D.</given-names>
            <surname>Federico</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Dumas</surname>
          </string-name>
          ,
          <string-name>
            <surname>C. G. J. van Dun</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Fehrer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. A.</given-names>
            <surname>Fischer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Gal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Indulska</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Isahagian</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Klinkmüller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Kratsch</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Leopold</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. V.</given-names>
            <surname>Looy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. A.</given-names>
            <surname>López</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Lukumbuzya</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Mendling</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Meyers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Moder</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Montali</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Muthusamy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Reichert</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Rizk</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Rosemann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Röglinger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Sadiq</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Seiger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Slaats</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Simkus</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I. A.</given-names>
            <surname>Someh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Weber</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Weber</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Weske</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Zerbato</surname>
          </string-name>
          ,
          <article-title>The biggest business process management problems to solve before we die</article-title>
          ,
          <source>Comput. Ind</source>
          .
          <volume>146</volume>
          (
          <year>2023</year>
          )
          <article-title>103837</article-title>
          . doi:
          <volume>10</volume>
          .1016/J.COMPIND.
          <year>2022</year>
          .
          <volume>103837</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>A.</given-names>
            <surname>Armas-Cervantes</surname>
          </string-name>
          ,
          <string-name>
            <surname>N. R. T. P. van Beest</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. L.</given-names>
            <surname>Rosa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Dumas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>García-Bañuelos</surname>
          </string-name>
          ,
          <article-title>Interactive and incremental business process model repair</article-title>
          , in: H.
          <string-name>
            <surname>Panetto</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Debruyne</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          <string-name>
            <surname>Gaaloul</surname>
            ,
            <given-names>M. P.</given-names>
          </string-name>
          <string-name>
            <surname>Papazoglou</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Paschke</surname>
            ,
            <given-names>C. A.</given-names>
          </string-name>
          <string-name>
            <surname>Ardagna</surname>
          </string-name>
          , R. Meersman (Eds.),
          <article-title>On the Move to Meaningful Internet Systems</article-title>
          .
          <source>OTM 2017</source>
          Conferences - Confederated International Conferences: CoopIS,
          <string-name>
            <surname>C</surname>
          </string-name>
          &amp;TC, and
          <article-title>ODBASE 2017, Rhodes</article-title>
          , Greece,
          <source>October 23-27</source>
          ,
          <year>2017</year>
          , Proceedings,
          <string-name>
            <surname>Part</surname>
            <given-names>I</given-names>
          </string-name>
          , volume
          <volume>10573</volume>
          of Lecture Notes in Computer Science, Springer,
          <year>2017</year>
          , pp.
          <fpage>53</fpage>
          -
          <lpage>74</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>319</fpage>
          -69462-7\_5.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>D.</given-names>
            <surname>Fahland</surname>
          </string-name>
          ,
          <string-name>
            <surname>W. M. P. van der Aalst</surname>
          </string-name>
          ,
          <article-title>Model repair - aligning process models to reality, Inf</article-title>
          . Syst.
          <volume>47</volume>
          (
          <year>2015</year>
          )
          <fpage>220</fpage>
          -
          <lpage>243</lpage>
          . doi:
          <volume>10</volume>
          .1016/J.IS.
          <year>2013</year>
          .
          <volume>12</volume>
          .007.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>K.</given-names>
            <surname>Pefers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Tuunanen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. A.</given-names>
            <surname>Rothenberger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Chatterjee</surname>
          </string-name>
          ,
          <article-title>A design science research methodology for information systems research</article-title>
          ,
          <source>Journal of management information systems 24</source>
          (
          <year>2007</year>
          )
          <fpage>45</fpage>
          -
          <lpage>77</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>J.</given-names>
            <surname>Mendling</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Leopold</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Meyerhenke</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Depaire</surname>
          </string-name>
          , Methodology of algorithm engineering,
          <year>2023</year>
          . URL: https://arxiv.org/abs/2310.18979. arXiv:
          <volume>2310</volume>
          .
          <fpage>18979</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>C.</given-names>
            <surname>Wohlin</surname>
          </string-name>
          ,
          <article-title>Guidelines for snowballing in systematic literature studies and a replication in software engineering</article-title>
          ,
          <source>in: Proceedings of the 18th international conference on evaluation and assessment in software engineering</source>
          ,
          <year>2014</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>10</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>S. K.</given-names>
            <surname>Boell</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Cecez-Kecmanovic</surname>
          </string-name>
          ,
          <article-title>A hermeneutic approach for conducting literature reviews and literature searches</article-title>
          ,
          <source>Communications of the Association for information Systems</source>
          <volume>34</volume>
          (
          <year>2014</year>
          )
          <fpage>12</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>K.</given-names>
            <surname>Beck</surname>
          </string-name>
          ,
          <article-title>Test driven development: By example</article-title>
          ,
          <string-name>
            <surname>Addison-Wesley Professional</surname>
          </string-name>
          ,
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>R.</given-names>
            <surname>Wieringa</surname>
          </string-name>
          ,
          <article-title>Design science methodology for information systems</article-title>
          and software engineering,
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>