A Formal Framework for Diagnostic Analysis for Errors of Business Processes

BackgroundBusiness process modelling is increasingly used not only by the companies’ management but also by scientists dealing with process models. Process modeling is seldom done without decision-making nodes, which is why operational research methods are increasingly included in the process analyses.ObjectiveThis systematic literature review aimed to provide a detailed and comprehensive description of the relevant aspects of used operational research techniques in Business Process Model and Notation (BPMN) model.MethodsThe Web Of Science of Clarivate Analytics was searched for 128 studies of that used operation research techniques and business process model and notation, published in English between 1 January 2004 and 18 May 2020. The inclusion criteria were as follows: Use of Operational Research methods in conjunction with the BPMN, and is available in full-text format. Articles were not excluded based on methodological quality. The background information of the included studies, as well as specific information on the used approaches, were extracted.ResultsIn this research, thirty-six studies were included and considered. A total of 11 specific methods falling into the field of Operations Research have been identified, and their use in connection with the process model was described.ConclusionOperational research methods are a useful complement to BPMN process analysis. It serves not only to analyze the probability of the process, its economic and personnel demands but also for process reengineering.

Business process modeling and management approaches are increasingly used and disclosed between organizations as a means of optimizing and streamlining the business activities. Among the various existing modeling languages, we stress the Business Process Model and Notation (BPMN), currently in version 2.0. BPMN is a widespread OMG standard that is actually used either in academia and in organizations. BPMN enables business process modeling, but does not facilitate the modeling of the information infrastructure involved in the process. However, interest in the data and its preservation has increased in BPMN's most recent version. The aim of this paper is to study BPMN 2.0, particularly on the usage and persistence of data, and present an approach for obtaining an early data model from the business process modeling, which may then be used as a starting data model in the software development process.

Large Language Models (LLMs) are emerging as powerful tools for automating business process modeling, promising to streamline the translation of textual process descriptions into Business Process Model and Notation (BPMN) diagrams. However, the extent to which these Al systems can produce high-quality BPMN models has not yet been rigorously evaluated. This paper presents an early evaluation of five LLM-powered BPMN generation tools that automatically convert textual process descriptions into BPMN models. To assess the external quality of these Al-generated models, we introduce a novel structured evaluation framework that scores each BPMN diagram across three key process model quality dimensions: clarity, correctness, and completeness, covering both accuracy and diagram understandability. Using this framework, we conducted experiments where each tool was tasked with modeling the same set of textual process scenarios, and the resulting diagrams were systematically scored based on the criteria. This approach provides a consistent and repeatable evaluation procedure and offers a new lens for comparing LLM-based modeling capabilities. Given the focused scope of the study, the results should be interpreted as an exploratory benchmark that surfaces initial observations about tool performance rather than definitive conclusions. Our findings reveal that while current LLM-based tools can produce BPMN diagrams that capture the main elements of a process description, they often exhibit errors such as missing steps, inconsistent logic, or modeling rule violations, highlighting limitations in achieving fully correct and complete models. The clarity and readability of the generated diagrams also vary, indicating that these Al models are still maturing in generating easily interpretable process flows. We conclude that although LLMs show promise in automating BPMN modeling, significant improvements are needed for them to consistently generate both syntactically and semantically valid process models.

During software maintenance, software models play a fundamental role, as they assist in understanding the software that will be corrected or evolved. Business process models, generally produced using Business Process Modeling and Notation (BPMN), help understanding the business processes supported by software. Therefore, these models are instrumental in maintaining corporate software. However, it is common that during software maintenance, models related to the software are not updated. Thus, the models are inconsistent with the version in use of the software, becoming increasingly obsolete over time. Given that, we developed the e-VOL BPMN technique to support BPMN models' evolution during software maintenance. The objective of e-VOL BPMN is to assist software engineers and developers, with little experience in BPMN notation, to carry out the necessary evolutions in the processes supported by the software. We evaluated the e-VOL BPMN in two experiments, and the results showed evidence that e-VOL BPMN helps the evolution of BPMN models in an appropriate manner. With this technique, such professionals can keep BPMN models up to date. This makes it easier to understand the processes supported by the software, which reduces the time and cost of future maintenance. Furthermore, understanding these processes correctly can reduce undue modifications to the software, contributing to the quality of the maintained software.

Currently, the number of patients with neurological diseases is increasing, especially those older than 65 suffering from Alzheimer’s disease. This development increases the emphasis on understanding and mapping treatment and care processes, not only for the elderly. Service providers (of both treatment and care) are under general pressure to decrease charges and maintain or improve existing levels of care. This situation is significantly influenced by a comprehensive knowledge of the whole process and its values. This publication therefore aims to describe the fundamental procedural aspects of caring for patients with Alzheimer’s disease, using Business Process Model and Notation (BPMN). It also aims to show the possibilities of using BPMN in the description of treatment and care. Modeling of the business process is more frequently being applied not only by businesses but also by scientists involved in process models. It is used to model medical topics, with approximately 10% of its publications only, and most of these publications deal only with clinical pathways, not with overall treatment and care processes. However, the BPMN model allows the whole process of medical and nonmedical care for patients with Alzheimer’s disease to be described, including the decomposition of partial activities into individual threads and sub-processes or atomic tasks. This paper presents the BPMN modeling and mapping of the specific care path for neurodegenerative patients. The text provides a new perspective on the BPMN modeling of Alzheimer’s disease. The presented model offers the option of expanding treatment cost calculation to simulate the process using graphical tools and languages. The overall view of this system creates a much more complex concept of the system and its surroundings.

Reliability of BPMN Business Processes

The Business Process Model and Notation (BPMN) is a widely used standard for business process modelling and maintained by the Object Management Group (OMG). However, the BPMN 2.0 specification is quite comprehensive and spans more than 500 pages. The definition of an element is distributed across different sections and sometimes conflicting. In addition, the structure of the elements and their relationships are described within the metamodel, however, further syntactical rules are defined within the natural text. Therefore, this paper defines an ontology that formally represents the BPMN specification. This ontology is called the BPMN 2.0 Ontology and can be used as a knowledge base. The description of an element is combined within the corresponding class and further explanations are provided in annotations. This allows a much faster understanding of BPMN. In addition, the ontology is used as a syntax checker to validate concrete BPMN models.

The Business Process Model and Notation (BPMN) has become the de facto standard for process modeling. Currently, BPMN models can be (a) analyzed or simulated using specialized tools, (b) executed using business process management systems (BPMSs), or (c) used for requirements elicitation. Although there are many studies comparing BPMN to other modeling techniques for analyzing and executing processes, there are few showing the suitability of BPMN models as a source for requirements comprehension in projects where process-aware software is built without using BPMSs. This chapter presents a study aimed at comparing the comprehension of software requirements regarding a business process using either BPMN or traditional techniques, such as use cases. In our study, we analyzed responses of 120 undergraduate and graduate students regarding the requirements comprehension achieved when using only BPMN models, only use cases, or both. The results do not show significant impact of the artifacts on the comprehension level. However, when the understanding of the requirement involves sequence of activities, using the BPMN shows better results on the comprehension time.

In 2014, the Object Management Group (OMG) published the Case Management Modeling and Notation (CMMN) version 1.0 specification, which is a new process modeling specification to complement its Business Process Modeling and Notation (BPMN) specification. The declarative nature of CMMN is intended to supplement the procedural perspective of BPMN. CMMN takes a data-centric view to process modeling based on business artifacts to provide flexibility for knowledge workers, while retaining the advantages of business process management (BPM) systems.

The rise of vehicle connectivity and autonomy is predicted to amplify the impact of emerging cybersecurity risks during the entire product life cycle in the automotive sector. To address all aspects of vehicle safety, including functional safety, safety of intended functionality (SOTIF), and cybersecurity, efforts must be made to collaborate across these areas during the maintenance period for incidents handling as well. Currently, much emphasis is being placed on the Incident Monitoring Process, which focuses on cybersecurity concerns. To round out the picture, safety incidents should be also considered. As a result, the research intends to examine SOTIF -related incidents in addition to cybersecurity issues. Following that, the paper gives a full model of the CyberSafety Incident Monitoring Process, which includes all industry requirements for cybersecurity monitoring as well as SOTIF-related concerns. The paper presents the proposal of using Business Process Model and Notation (BPMN) to create a complete process model. The probable practical implementation of the CyberSafety Incident Monitoring Process Model is evaluated in the last part of the study based on the phantom attack scenario to test the idea with a real-world example. As a consequence, the strategy is accurate and fits the industry goal of merging safety and cybersecurity during the maintenance phase, which reduces the time and effort necessary for faster response to various vehicle risks when time is crucial. In future research, more emphasis should be made on combining numerous incident fields, which may have an impact on vehicle safety.

A metamodel to integrate business processes time perspective in BPMN 2.0

Business Process Model and Notation—BPMN

PurposeBusiness process modelling integrates and visualizes relevant information essential for managing day-to-day business operations. It plays a critical role in the design and execution of business transformations. Recognizing the role of process modelling, a large number of modelling languages, methods and techniques have been developed, each offering diverse advantages and having inherent limitations. Traditional and popular process modelling approaches focus on the exact specification of the control flow of business processes, whereas more recent approaches like Subject-oriented Business Process Management (S-BPM) are focused on the communication between process participants. This study aims to provide comparative insights about these two approaches through their experimental application. This study does so by comparing Business Process Model and Notation (BPMN); a control flow approach, with S-BPM; a communication approach, with a specific focus on their suitability for novice modellers.Design/methodology/approachThis paper reports on an exploratory experiment that compares BPMN to S-BPM. Applying cognitive load theory, this study compares the experiences and outcomes of novice process modellers, assessing perceived ease of use, model quality (syntactic and semantic) and modelling efficiency (time to model) across the two approaches.FindingsStudy results show that S-BPM (a communication approach) led to significantly better user performances for process modelling than BPMN (a control flow approach). This study points to how a different modelling approach such as S-BPM could be either considered as an alternative or to complement the more popular control flow approach BPMN. This observation was especially relevant for modelling contexts where domain experts are novice process modellers.Originality/valueThis study provides the first empirical evidence that communication approaches like S-BPM could outperform modelling approaches which are control-flow based (i.e. BPMN), especially when being used by novice process modellers who hold the domain and process knowledge. This study uses this as a springboard to present important considerations for practice and guide future process modelling research.

Industry 4.0 is one of the most prominent initiatives towards the vision of smart manufacturing to foster efficiency and synergy among suppliers, producers, and customers. It will transform the production systems into a smart, fully integrated, and optimized cyber-physical production systems (CPPS) based on technology enablers such as Internet of Things (IoT). Moreover, the availability of a wide range of data and information in the context of CPPS provides a huge possibility to create novel business opportunities. However, for these business opportunities to materialize successfully there is an evident need to have an efficient communication and clear visualization of the new strategies and the underlying operational process among all the stakeholders involved in the manufacturing value chain. In this paper, we propose a model-based approach for creating and communicating business strategies (mission, goals, and tactics) and bridging the gap between the business strategies and corresponding operational processes using Business Motivation Model (BMM) and Business Process Modeling and Notation (BPMN) respectively. Concretely, we do the following, (i) create BMM models to communicate business ideas and connect corresponding business tactics to the processes models in BPMN, (ii) simulate processes to check achievable KPIs corresponding to different strategies (modeled in BMM), and (iii) define organizational units in BMM that perform tasks modeled in BPMN. We illustrate our approach through an exemplar case study about production of plastic cups by modeling high-level strategies and their underlying processes. To prove the feasibility of our work, we used and developed the BMM and BPMN plugins based on Eclipse Papyrus framework.

Process analysis and process modeling are a current topic that extends to many areas. This trend of using optimization and modeling techniques in various specific areas has led to the question of how widespread these approaches are overall in medical specializations. We compiled a list of 272 medical disciplines that we used as a search string with the Business Process Model and Notation (BPMN) for a Web of Science database search. Thus, we found a total of 485 documents that we subjected to the exclusion criteria. We analyzed the remaining 108 articles using bibliometric and content analyses to find answers to three research questions. This systematic review was carried out using the procedure proposed by Kitchenham and following the Preferred Items of the Systematic Review and Meta-Analysis Report (PRISMA). Due to the broad scope of the medical field, it was no surprise that for almost 85% of the sought-after medical specializations, we could not identify any publications in the given database when applying the BPMN. We analyzed the impact of upgrades to the BPMN on publishing. The keyword analysis showed a diametrical difference between the authors’ keywords and the so-called “Keywords Plus”, and we categorized the publications according to the purpose of applying the BPMN. However, the growing interest in combining BPMN with other approaches brings new challenges in practice.