MODELAGEM DO PROCESSO DE ENSAIO DE RADIOCOMUNICAÇÃO RESTRITA UTILIZANDO NOTAÇÃO BPMN

A company must maintain the stability of its business processes. To ensure smooth business operations, one approach is to enhance competitive quality for consumers. Maintaining consumer trust can be achieved by ensuring the stability of quality products and fast service. This study was conducted at PT. Dwi Putra Manunggal, located in Malang Regency, East Java. The company faces inefficiencies in its distribution process, causing delays in getting products to consumers. To improve business processes, an analysis using the Business Process Improvement (BPI) method can be performed. BPI is used to find solutions to ongoing business process issues. To evaluate and implement improvements, modeling notation written in Business Process Model and Notation (BPMN) can be used, providing stakeholders with an overview of the business process improvements made. By using BPMN notation, the actual (as-is) and recommended (to-be) business process simulations and models can be identified. As a result, PT. Dwi Putra Manunggal's business processes need improvement through BPI, with several parts of the business process requiring simplification. The simplification, simulated and modeled using BPMN, results in a minimum time of 7 hours, a maximum time of 13 hours, and an average time of 13 hours and 10 minutes.A company must maintain the stability of its business processes. To ensure smooth business operations, one approach is to enhance competitive quality for consumers. Maintaining consumer trust can be achieved by ensuring the stability of quality products and fast service. This study was conducted at PT. Dwi Putra Manunggal, located in Malang Regency, East Java. The company faces inefficiencies in its distribution process, causing delays in getting products to consumers. To improve business processes, an analysis using the Business Process Improvement (BPI) method can be performed. BPI is used to find solutions to ongoing business process issues. To evaluate and implement improvements, modeling notation written in Business Process Model and Notation (BPMN) can be used, providing stakeholders with an overview of the business process improvements made. By using BPMN notation, the actual (as-is) and recommended (to-be) business process simulations and models can be identified. As a result, PT. Dwi Putra Manunggal's business processes need improvement through BPI, with several parts of the business process requiring simplification. The simplification, simulated and modeled using BPMN, results in a minimum time of 7 hours, a maximum time of 13 hours, and an average time of 13 hours and 10 minutes.Keywords: BPI, BPMN, Modeling and Simulation, Distribution

In the software maintenance, business process models help practitioners understanding of the software, because it represents the organisational process in which software is embedded. BPMN (Business Process Modelling and Notation) is the standard notation for business process modelling. However, it is common for the BPMN diagrams to be outdated, which, among other possibilities, may be caused due to the lack of adequate knowledge of some practitioners about the notation. It is important to provide means to stimulate the evolution of these models and, consequently, to aid in the learning of BPMN notation. With this focus, the authors proposed and evaluated the e-VOL BPMN, a technique that supports the evolution and the learning of BPMN diagrams. In this evaluation, they compared e-VOL BPMN with the BPMN 2.0 Poster, an artefact used commonly to support BPMN notation in companies. Participants who used the e-VOL BPMN in a scenario of diagrams evolution presented more correct BPMN diagrams and had a higher learning perception of the notation. In addition, in a written exam on BPMN notation, participants who used e-VOL BPMN scored higher. From these results, they notice that e-VOL BPMN support both evolution and learning of BPMN diagrams.

Business Process Model and Notation (BPMN) is applied to manage business processes. Currently, business processes are becoming more complex with increasing conditions. As a result, it is highly difficult to manage activities and decision-making in business processes. However, BPMN still cannot handle the decision-making in business processes. Object management group (OMG) created Decision Model and Notation (DMN) to complement BPMN and to manage the decision-making of business processes. In software development process, creating a business process model can occur earlier during requirement gathering. However, a tester can generate test cases to verify accuracy of information in the business process. Previously, many researchers have focused on BPMN test cases generation. None of their studies has been conducted on the creation of BPMN test cases with DMN. Consequently, this paper proposes an approach to generate test cases from BPMN with DMN. BPMN along with DMN, paths traverse from the entry to the exit of the BPMN, and existing test cases are inputs of our approach. BPMN, DMN, and existing test cases are analyzed to check whether they cover all rules in the DMN. In case that all rules are not covered, new test cases will be generated. This paper proposes an approach to generate test cases cover all rules in the DMN to effective monitoring BPMN with DMN. This approach is used to check the rules within the DMN decision table without affecting BPMN process. It ensures the business processes are implemented correctly.

Business process modeling is one of the main tools of the BPM (Business Process Management) concept. With the help of business process modeling, business scenarios can be presented in the form of graphical models that can be easily understood by both information technology (IT) professionals and non-IT professionals – business analysts, software customers, department heads, top managers, and other stakeholders interested in business process improvement. Business process improvement is usually done through the automation of activities, which were identified as “bottlenecks” after analysis. However, it is possible to analyze a business process model only if it is clear and correct in terms of compliance with both the notation used and the real business process it depicts. This paper considers the analysis of BPMN (Business Process Model and Notation) business process model structural measures. It is assumed that business process models, which by their structural features violate rules of business process modeling, are neither understandable nor suitable for further work with them, which also can lead to various errors occurring at the stage of business process analysis, as well as at the stage of its improvement and implementation of proposed changes, i.e., during development, testing and maintenance of distinct software components, information system modules or BPM-system scenarios that ensure business process execution. Therefore, in this paper, we propose to identify the main elements of BPMN business process models and their structural measures that affect models’ understandability and maintainability and could be sources of errors. Considering selected measures, it is proposed to calculate respective values for a large collection of BPMN business process models, and then study compliance with theoretical business process modeling guidelines on practice when real business process models are designed. In order to provide efficient storage and processing of a large collection of BPMN business process models data, there were developed a database, and a software component. Results of analysis of BPMN business process model structural measures obtained using developed database and software component are demonstrated and discussed. The conclusion is made, as well as future research directions in this field are formulated.

The Business Process Model and Notation (BPMN) has emerged as one of the dominant graphical modelling languages for processes in recent years. Its usage is both for conceptual workflow modelling and for specification of executable workflow schemata. Nevertheless BPMN seems to be less suitable for modelling of business processes. Business process models describe production and delivery as well as control of goods and services according to the goals of an enterprise (task level). These characteristics are not covered explicitly by BPMN. In contrast, workflow schemata specify solution procedures for the execution of business tasks (actor level). In this paper a two-stage modelling approach is proposed in order to overcome the semantic gap between business process models and workflow schemata: In a first step a business process model according to the Semantic Object Model (SOM) is created and stepwise refined. In a second step a BPMN workflow schema is derived from an adequately refined business process model according to a metamodel-based schema transformation. The modelling approach is illustrated using the case study of an online auction house.

Business process modelling is one of the major aspects in the modern information system development. Recently business process model and notation (BPMN) has become a standard technique to support this activity. Typically the BPMN notations are used to understand enterprise's business processes. However, limited work exists regarding how security concerns are addressed during the management of the business processes. This is a problem, since both business processes and security should be understood in parallel to support a development of the secure information systems. In the previous work we have analysed BPMN with respect to the domain model of the IS security risk management (ISSRM) and showed how the language constructs could be aligned to the concepts of the ISSRM domain model. In this paper the authors propose the BPMN extensions for security risk management based on the BPMN alignment to the ISSRM concepts. We illustrate how the extended BPMN could express assets, risks and risk treatment on few running examples related to the Internet store regarding the asset confidentiality, integrity and availability. Our proposal would allow system analysts to understand how to develop security requirements to secure important assets defined through business processes. The paper opens the possibility for business and security model interoperability and the model transformation between several modelling approaches (if these both are aligned to the ISSRM domain model).

Business Process Model and Notation (BPMN) is a standard graphical notation for modeling complex business processes. Given the importance of business processes, the modeling analysis and validation stage for BPMN is essential. In recent years, BPMN notation has become a widespread practice in business process modeling because of these intuitive diagrams. BPMN diagrams are built from basic elements. The major challenge of BPMN diagrams is the lack of formal semantics, which leads to several interpretations of the concerned diagrams. Hence, this work aims to propose an approach for checking BPMN collaboration diagrams to guarantee some properties of smooth functioning of systems modeled by BPMN notation. The verification approach used in this work is based on model checking techniques. The approach proposes as a first step a formal semantics of the collaboration diagrams in terms of the formal language DD-LOTOS, i.e., a phase of the transformation of collaboration diagrams into DD-LOTOS. This transformation is guided by applying the inference rules of the formal semantics of the DD-LOTOS formal language, and we then use the UPPAAL model checker to check the absence of deadlock, safety properties, and liveness properties.

Service-oriented systems are increasingly implemented in a process-based fashion. Multiple languages for building process-based systems are available today, but the Business Process Model and Notation (BPMN) is becoming ubiquitous. With BPMN 2.0 released in 2011, execution semantics were introduced, supporting the definition of executable processes. Nowadays, more and more process engines directly support the execution of BPMN processes. However, the BPMN specification is lengthy and complex. As there are no official tests and no certification authority, it is very likely that engines a) implement only a subset of the language features and b) implement language features differently. In other words, we suspect that engines do not conform to the standard, despite the fact that they claim support for it. This prohibits the porting of processes between different BPMN vendors, which is an acclaimed goal of the language. In this paper, we investigate the standard conformance of open source BPMN engines to provide a clear picture of the current state of the implementation of BPMN. We develop a testing approach that allows us to build fully BPMN-compliant tests and automatically execute these tests on different engines. The results demonstrate that state of-the-art BPMN engines only support a subset of the language. Moreover, they indicate that porting BPMN processes is only feasible when using basic language constructs.

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.

BACKGROUND Healthcare systems are increasingly confronted with the challenge of managing complex clinical processes. One proposed solution is a patient-centered management intervention called a care pathway that needs process mapping to support process improvement. Although the adoption and use of Business Process Model and Notation (BPMN) for modeling patient healthcare trajectories has increased, evidence of the benefits of implementing it in healthcare organization management systems are still unclear. OBJECTIVE This review sought to examine effectiveness by mapping evidence of implementation factors linking intended purpose to expected or demonstrated outcomes. METHODS A systematic review of the use of BPMN for modeling patient care trajectories was conducted across Medline (Ovid), Embase (Embase.com), Academic Search Premier, ABI/Inform (ProQuest), Web of Science, and Google Scholar. We followed the Cochrane Methods Group and the PRISMA guidelines. Quality appraisal was performed using the Mixed Methods Appraisal Tool (MMAT). Data were charted using a customized form and were analyzed thematically with both qualitative and semi-quantitative syntheses. RESULTS After screening, 53 studies were included. Our findings suggest that BPMN offers significant benefits in healthcare. Its use allows healthcare professionals to gain a comprehensive understanding of patient care pathways, making it easier to identify inefficiencies and areas for improvement. The definition of processes ensures that workflows remain consistent across different settings, thereby reducing variation and improving the quality of care. Several studies have demonstrated BPMN’s effectiveness in process optimization, highlighting its ability to streamline workflows, reduce redundancies, and enhance operational efficiency. Moreover, when integrated with decision-support tools, BPMN enhances clinical decision-making by enabling better adherence to guidelines and best practices. Another important advantage is BPMN’s interoperability with existing healthcare IT standards, such as HL7, which facilitates seamless integration with EHRs and other digital health systems. However, in a managerial perspective, users must also carefully weigh the trade-offs between BPMN’s benefits and its limitations, particularly in highly complex healthcare settings. Despite advantages, several challenges persist, including issues related to scalability, integration with advanced decision-making frameworks and the complexity of modeling dynamic healthcare environments. While BPMN is a widely adopted modeling approach, alternative methodologies offer complementary or competing advantages, such as Petri Nets, UML or Business Process Execution Language. Therefore, there are several opportunities for enhancing BPMN’s applicability in healthcare, such as the creation of domain-specific BPMN extensions or the integration of artificial intelligence and machine learning into BPMN models. CONCLUSIONS This review highlights BPMN’s potential as a valuable tool for modeling patient healthcare trajectories. Its ability to standardize and optimize processes makes it a promising framework for improving clinical and operational efficiency. However, trade-offs between benefits and limits of BPMN characterized its implementation in patient care trajectories, giving rise to opportunities for the development and integration of new tools. INTERNATIONAL REGISTERED REPORT RR2-10.1136/bmjopen-2021-060357

Business Process Model and Notation (BPMN) is a graphical representation and notation for modeling complex business processes in diagrams. A simple BPMN diagram is easier to understand by all of the business stakeholders than a complex one. It is also easier for the developers to implement the corresponding systems. Complexity metrics can measure the complexity of a diagram. Only a few BPMN complexity metrics are found in the literature as BPMN is a recent development. To propose a new BPMN complexity metric, it is important to find suitable software complexity metrics which can be further adapted to develop a complexity metric for BPMN. This research surveys the existing software complexity metrics and the existing BPMN complexity metrics (i.e. McCabe Cyclomatic Complexity, Control-flow Complexity, and Halstead-based Process Complexity Metrics) to compare their performance and suitability in measuring the complexity of BPMN diagrams. The BPMN diagrams of the business processes of two Enterprise Resource Planning (ERP) open-source systems (i.e. Compiere and Openbravo ERP systems) are used in this research. The metrics values obtained are compared with empirical application and code measurement values (i.e. number of form-fields, number of files of code, and number of classes) of the two open-source systems. This research finds that the Halstead-based Process Complexity that has been proposed in the literature is useful in measuring the data complexity of BPMN diagrams. This means that the Halstead-based Process Complexity can be further elaborated to produce a BPMN complexity measure.

Business process modelling is one of the major aspects in the modern system development. Recently business process model and notation (BPMN) has become a standard technique to support this activity. Although BPMN is a good approach to understand business processes, there is a limited work to understand how it could deal with business security and security risk management. This is a problem, since both business processes and security concerns should be understood in parallel to support a development of the secure systems. In this paper we analyse BPMN with respect to the domain model of the IS security risk management (ISSRM). We apply a structured approach to understand key aspects of BPMN and how modeller could express secure assets, risks and risk treatment using BPMN. We align the main BPMN constructs with the key concepts of the ISSRM domain model. We show applicability of our approach on a running example related to the Internet store. Our proposal would allow system analysts to understand how to develop security requirements to secure important assets defined through business processes. In addition we open a possibility for the business and security model interoperability and the model transformation between several modelling approaches (if these both are aligned to the ISSRM domain model).KeywordsBusiness process model and notation (BPMN)Security risk managementAlignment of modelling languagesInformation systems

Business Process Model and Notation (BPMN), now at version 2.0.2, provides a standard graphical representation for specifying business processes. In this paper we report on the first stage of a semantic investigation of BPMN, using methods in the tradition of programming languages semantics. We consider a control-flow subset of BPMN and an execution architecture based on an intermediate language that we name ℒ BPMN . The execution architecture comprises two main components: a translator which takes as input a BPMN model and generates ℒ BPMN code, and an interpreter for ℒ BPMN . ℒ BPMN is a process oriented imperative language providing a combination of concepts, including maximal parallelism and durational activities. We employ the mathematical methodology of metric semantics in designing and relating an operational semantics O and a denotational semantics D for ℒ BPMN . We establish the formal relation between O and D by using an abstraction operator and a fixed point argument. In this way we prove the correctness of the denotational semantics with respect to the operational semantics. We focus on the semantic investigation of BPMN. We also explain how the operational semantics can serve as a blueprint for an implementation on a client-server architecture.

Business process modelling is one of the major aspects in the modern information system development. Recently business process model and notation (BPMN) has become a standard technique to support this activity. Typically the BPMN notations are used to understand enterprise's business processes. However, limited work exists regarding how security concerns are addressed during the management of the business processes. This is a problem, since both business processes and security should be understood in parallel to support a development of the secure information systems. In the previous work we have analysed BPMN with respect to the domain model of the IS security risk management (ISSRM) and showed how the language constructs could be aligned to the concepts of the ISSRM domain model. In this paper the authors propose the BPMN extensions for security risk management based on the BPMN alignment to the ISSRM concepts. We illustrate how the extended BPMN could express assets, risks and risk treatment on few running examples related to the Internet store regarding the asset confidentiality, integrity and availability. Our proposal would allow system analysts to understand how to develop security requirements to secure important assets defined through business processes. The paper opens the possibility for business and security model interoperability and the model transformation between several modelling approaches (if these both are aligned to the ISSRM domain model).

uBPMN: A BPMN extension for modeling ubiquitous business processes