Validating Component-Based Implementations of Business Processes

2011 ◽  
pp. 124-151
Author(s):  
Jens Lemcke ◽  
Andreas Friesen ◽  
Tirdad Rahmani
Keyword(s):  
Petri Nets ◽  
Business Process ◽  
Business Processes ◽  
Process Models ◽  
Action Refinement ◽  
Deadlock Analysis ◽  
Multiple Process ◽  
Component Based Software Engineering ◽  
Exponential Complexity ◽  
Different Levels

This chapter provides a formal specification of non-atomic, relaxed action refinement suited for component-based business process engineering. Engineering a business process involves multiple process models created by different people on different levels of abstractions. Keeping the models consistent during the engineering procedure—refinement validation—is one objective of this chapter. In component-based software engineering, the lowest abstraction of a business process is mapped on existing components that have a description of their behaviors. Checking the consistency of process and component behavior—grounding validation—is the second objective. Both refinement and grounding validation increase the robustness of business process implementations and the productivity of process engineers. Technically, the specification given in this chapter is in terms of deadlock analysis in safe Petri nets. The evaluation of this straight-forward implementation underlines the exponential complexity of deadlock analysis in safe Petri nets. For use cases with more than 30 activities per process or heavy parallelism, optimized implementations are needed.

Assigning Ontological Meaning to Workflow Nets

2012 ◽  
pp. 209-244
Author(s):  
Pnina Soffer ◽  
Maya Kaner ◽  
Yair Wand
Keyword(s):  
Petri Nets ◽  
Business Process ◽  
Business Processes ◽  
Process Models ◽  
Actual Process ◽  
Workflow Nets ◽  
Business Process Models ◽  
Business Goals ◽  
General Constraints ◽  
Process Behavior

A common way to represent organizational domains is the use of business process models. A Workflow-net (WF-net) is an application of Petri Nets (with additional rules) that model business process behavior. However, the use of WF-nets to model business processes has some shortcomings. In particular, no rules exist beyond the general constraints of WF-nets to guide the mapping of an actual process into a net. Syntactically correct WF-nets may provide meaningful models of how organizations conduct their business processes. Moreover, the processes represented by these nets may not be feasible to execute or reach their business goals when executed. In this paper, the authors propose a set of rules for mapping the domain in which a process operates into a WF-net, which they derived by attaching ontological semantics to WF-nets. The rules guide the construction of WF-nets, which are meaningful in that their nodes and transitions are directly related to the modeled (business) domains. Furthermore, the proposed semantics imposes on the process models constraints that guide the development of valid process models, namely, models that assure that the process can accomplish its goal when executed.

Assigning Ontological Meaning to Workflow Nets

2010 ◽  
Vol 21 (3) ◽  
pp. 1-35 ◽  
Author(s):  
Pnina Soffer ◽  
Maya Kaner ◽  
Yair Wand
Keyword(s):  
Petri Nets ◽  
Business Process ◽  
Business Processes ◽  
Process Models ◽  
Actual Process ◽  
Workflow Nets ◽  
Business Process Models ◽  
Business Goals ◽  
General Constraints ◽  
Process Behavior

A common way to represent organizational domains is the use of business process models. A Workflow-net (WF-net) is an application of Petri Nets (with additional rules) that model business process behavior. However, the use of WF-nets to model business processes has some shortcomings. In particular, no rules exist beyond the general constraints of WF-nets to guide the mapping of an actual process into a net. Syntactically correct WF-nets may provide meaningful models of how organizations conduct their business processes. Moreover, the processes represented by these nets may not be feasible to execute or reach their business goals when executed. In this paper, the authors propose a set of rules for mapping the domain in which a process operates into a WF-net, which they derived by attaching ontological semantics to WF-nets. The rules guide the construction of WF-nets, which are meaningful in that their nodes and transitions are directly related to the modeled (business) domains. Furthermore, the proposed semantics imposes on the process models constraints that guide the development of valid process models, namely, models that assure that the process can accomplish its goal when executed.

scholarly journals Business processes exceptions in relation to operational performance

2019 ◽  
Vol 25 (5) ◽  
pp. 908-922 ◽  
Author(s):  
Remco Dijkman ◽  
Oktay Turetken ◽  
Geoffrey Robert van IJzendoorn ◽  
Meint de Vries
Keyword(s):  
Business Process ◽  
Process Model ◽  
Business Processes ◽  
Process Models ◽  
Operational Performance ◽  
Normal Flow ◽  
Throughput Time ◽  
Content Type ◽  
Business Process Models ◽  
Practical Implications

Purpose Business process models describe the way of working in an organization. Typically, business process models distinguish between the normal flow of work and exceptions to that normal flow. However, they often present an idealized view. This means that unexpected exceptions – exceptions that are not modeled in the business process model – can also occur in practice. This has an effect on the efficiency of the organization, because information systems are not developed to handle unexpected exceptions. The purpose of this paper is to study the relation between the occurrence of exceptions and operational performance. Design/methodology/approach The paper does this by analyzing the execution logs of business processes from five organizations, classifying execution paths as normal or exceptional. Subsequently, it analyzes the differences between normal and exceptional paths. Findings The results show that exceptions are related to worse operational performance in terms of a longer throughput time and that unexpected exceptions relate to a stronger increase in throughput time than expected exceptions. Practical implications These findings lead to practical implications on policies that can be followed with respect to exceptions. Most importantly, unexpected exceptions should be avoided by incorporating them into the process – and thus transforming them into expected exceptions – as much as possible. Also, as not all exceptions lead to longer throughput times, continuous improvement should be employed to continuously monitor the occurrence of exceptions and make decisions on their desirability in the process. Originality/value While work exists on analyzing the occurrence of exceptions in business processes, especially in the context of process conformance analysis, to the best of the authors’ knowledge this is the first work that analyzes the possible consequences of such exceptions.

scholarly journals Pengujian Unit Plugin Pemberian Anotasi Efek Secara Semantik pada Proses Bisnis BPMN

2021 ◽  
Vol 6 (3) ◽  
pp. 170
Author(s):  
Hilman Nuril Hadi
Keyword(s):  
Business Process ◽  
Process Model ◽  
Business Processes ◽  
Process Models ◽  
Unit Testing ◽  
Business Process Model ◽  
Testing Technique ◽  
Modeling Tools ◽  
Path Testing ◽  
Future Business

Business process model was created to make it easier for business process stakeholders to communicate and discuss the structure of the process more effectively and efficiently. Business process models can also be business artifacts and media that can be analyzed further to improve and maintain organizational competitiveness. To analyze business processes in a structured manner, the effect/results of the execution of business processes will be one of the important information. The effect/result of the execution of certain activities or a business process as a whole are useful for managing business processes, including for improvements related to future business processes. This effect annotation approach needs to be supported by business process modeling tools to assist business analysts in managing business processes properly. In previous research, the author has developed a plugin that supports business analysts to describe the effects semantically attached to activities in the Business Process Model and Notation (BPMN) business process model. In this paper, the author describes the unit testing process and its results on the plugin of semantic effect annotation that have been developed. Unit testing was carried out using the basic path testing technique and has obtained three test paths. The results of unit test for plugin are also described in this paper.

scholarly journals Collaborative method to maintain business process models updated

2014 ◽  
Vol 11 (2) ◽  
pp. 461-480 ◽  
Author(s):  
Nuno Castela ◽  
Paulo Dias ◽  
Marielba Zacarias ◽  
José Tribolet
Keyword(s):  
Case Studies ◽  
Business Process ◽  
Process Model ◽  
Business Processes ◽  
Process Models ◽  
Organizational Environment ◽  
Business Process Model ◽  
Business Process Models ◽  
Definition Of ◽  
Over Time

Business process models are often forgotten after their creation and its representation is not usually updated. This appears to be negative as processes evolve over time. This paper discusses the issue of business process models maintenance through the definition of a collaborative method that creates interaction contexts enabling business actors to discuss about business processes, sharing business knowledge. The collaboration method extends the discussion about existing process representations to all stakeholders promoting their update. This collaborative method contributes to improve business process models, allowing updates based in change proposals and discussions, using a groupware tool that was developed. Four case studies were developed in real organizational environment. We came to the conclusion that the defined method and the developed tool can help organizations to maintain a business process model updated based on the inputs and consequent discussions taken by the organizational actors who participate in the processes.

scholarly journals Business Process Improvement of Production Systems Using Coloured Petri Nets

2018 ◽  
Vol 7 (1) ◽  
pp. 102-112 ◽  
Author(s):  
Imam Mukhlash ◽  
Widya Nilam Rumana ◽  
Dieky Adzkiya ◽  
Riyanarto Sarno
Keyword(s):  
Petri Nets ◽  
Business Process ◽  
Business Performance ◽  
Business Processes ◽  
Production Systems ◽  
Coloured Petri Nets ◽  
Manufacturing Companies ◽  
Fundamental Factor ◽  
Bottleneck Analysis

The quality of information systems affects the company's business performance. Therefore, it is necessary to analyze business processes to determine any discrepancies between the planned business processes and the actual ones. Based on the results of this analysis, the business process can be improved. The fundamental factor of manufacturing companies is production process. In reality, there are many discrepancies between the actual business processes with the pre-planned, so that there should be analyzed. The analysis can be performed by modeling the business process using Coloured Petri Nets (CPN). In this study, the objectives are to determine the level of conformance checking of business processes, reachability graph and the bottleneck analysis. The results of the analysis are used to construct a recommended model. Based on the analysis of the case study, e.g. a steel industry in Indonesia, the recommended model has a better value than initial model.

User-Centered Business Process Modeling and Pattern-Based Development for Large Systems

2013 ◽  
pp. 134-155
Author(s):  
O. Takaki ◽  
T. Seino ◽  
N. Izumi ◽  
K. Hasida
Keyword(s):  
Information System ◽  
Business Process ◽  
Large Scale ◽  
Business Processes ◽  
Formal Method ◽  
Modeling Method ◽  
Process Models ◽  
Financial Accounting ◽  
Development Framework ◽  
Agile Software

In agile software development, it is imperative for stakeholders such as the users and developers of an information system to collaborate in designing and developing the information system, by sharing their knowledge. Especially in development of a large-scale information system, such collaboration among stakeholders is important, but difficult to achieve. This chapter introduces a modeling method of business processes for requirements analysis and a development framework based on Web-process architectures. The modeling method makes it easier for stakeholders to agree upon requirements. It also employs a formal method to allow business process models to satisfy both understandability and accuracy. On the other hand, the development framework above enables rapid spiral development of short-term cycles through the collaboration of developers and users. This chapter also introduces an example that compares the workloads of two requirement analyses of large-scale system developments for a government service and a financial accounting service, in order to evaluate the advantages of the proposed modeling method.

User-Centered Business Process Modeling and Pattern-Based Development for Large Systems

2014 ◽  
pp. 1014-1035
Author(s):  
O. Takaki ◽  
T. Seino ◽  
N. Izumi ◽  
K. Hasida
Keyword(s):  
Information System ◽  
Business Process ◽  
Large Scale ◽  
Business Processes ◽  
Formal Method ◽  
Modeling Method ◽  
Process Models ◽  
Financial Accounting ◽  
Development Framework ◽  
Agile Software

In agile software development, it is imperative for stakeholders such as the users and developers of an information system to collaborate in designing and developing the information system, by sharing their knowledge. Especially in development of a large-scale information system, such collaboration among stakeholders is important, but difficult to achieve. This chapter introduces a modeling method of business processes for requirements analysis and a development framework based on Web-process architectures. The modeling method makes it easier for stakeholders to agree upon requirements. It also employs a formal method to allow business process models to satisfy both understandability and accuracy. On the other hand, the development framework above enables rapid spiral development of short-term cycles through the collaboration of developers and users. This chapter also introduces an example that compares the workloads of two requirement analyses of large-scale system developments for a government service and a financial accounting service, in order to evaluate the advantages of the proposed modeling method.

A Method for Eliciting Goals for Business Process Models based on Non-Functional Requirements Catalogues

2013 ◽  
pp. 226-244 ◽  
Author(s):  
Evellin Cardoso ◽  
João Paulo A. Almeida ◽  
Renata S. S. Guizzardi ◽  
Giancarlo Guizzardi
Keyword(s):  
Business Process ◽  
Process Modeling ◽  
Business Processes ◽  
Business Process Modeling ◽  
Process Models ◽  
Functional Requirements ◽  
Business Process Models ◽  
Traditional Approaches ◽  
Goal Models

While traditional approaches in business process modeling tend to focus on “how” the business processes are performed (adopting a behavioral description in which business processes are described in terms of procedural aspects), in goal-oriented business process modeling, the proposals strive to extend traditional business process methodologies by providing a dimension of intentionality to business processes. One of the key difficulties in enabling one to model goal-oriented processes concerns the identification or elicitation of goals. This paper reports on a case study conducted in a Brazilian hospital, which obtained several goal models represented in i*/Tropos, each of which correspond to a business process also modeled in the scope of the study. NFR catalogues were helpful in goal elicitation, uncovering goals that did not come up during previous interviews prior to these catalogues’ use.

Sign in / Sign up

Export Citation Format

Share Document