BPMN Core Modeling Concepts: Inheritance-Based Execution Semantics

Börger, Egon; Sörensen, Ove

doi:10.1007/978-3-642-15865-0_9

Cited by 26 publications

(11 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The shortcomings of the BPMN standard are well-known and have been observed (for different versions of the standard) by various authors, see for example [7,9,16,22,36,52,53,58] (the list is by no means exhaustive), so that we can restrict ourselves in this section to listing and briefly commenting upon some of the major points where the standard document fails.…”

Section: Problems Of Bpmn 20mentioning

confidence: 97%

“…In fact, within the boundary of what is called 'standard-conforming' it may happen that: 7 See also the statement by the convenor of the standardization group at http://www.workflowpatterns.com/vendors/bpmn.php: 'The primary goal of BPMN is to provide a notation that is readily understandable by all business users, from the business analysts that create the initial drafts of the processes, to the technical developers responsible for implementing the technology that will perform those processes, and finally, to the business people who will manage and monitor those processes.' 8 A precise refinement concept could have been defined on the basis of a rigorous modeling framework, without need to push it as far as a 'formalization.…”

Section: Problems Of Bpmn 20mentioning

confidence: 98%

“…-The BPMN standard claims to (and indeed should) support the definition of models which serve the three major purposes of business process descriptions, namely model design and analysis (requiring accurate conceptual models in particular for high-level development and management support), model implementation, where the models play the role of the specification of software requirements and are transformed into executable models, and the use of models (user model for process execution, monitoring and management). 7 The standard document fails to provide a seamless systematic mechanism for refinement from conceptual to executable models, which is necessary to guarantee the reliability of the implementation. 8 As a consequence, there remains an unmediated gap between conceptual and executable BPMN models: executable BPMN models (in particular if obtained through compilation to more detailed languages like BPEL or to code) are hard to grasp and analyze for human readers [37,54]; there are no standardized view mechanisms supporting the extraction of abstract (e.g.…”

Section: Problems Of Bpmn 20mentioning

confidence: 99%

See 2 more Smart Citations

Approaches to modeling business processes: a critical analysis of BPMN, workflow patterns and YAWL

Börger

2011

Softw Syst Model

Self Cite

121

View full text Add to dashboard Cite

We investigate three approaches describing models of business processes: the OMG standard BPMN in its recent version 2.0, the workflow patterns of the Workflow Pattern Initiative and their reference implementation YAWL. We show how the three approaches fail to provide practitioners with a suitable means precisely and faithfully to capture business scenarios and to analyze, communicate and manage the resulting models. On the positive side, we distill from the discussion six criteria which can help to recognize practical and reliable tool-supported business process description and modeling systems.

show abstract

Section: Problems Of Bpmn 20mentioning

confidence: 97%

Section: Problems Of Bpmn 20mentioning

confidence: 98%

Section: Problems Of Bpmn 20mentioning

confidence: 99%

See 1 more Smart Citation

Approaches to modeling business processes: a critical analysis of BPMN, workflow patterns and YAWL

Börger

2011

Softw Syst Model

Self Cite

121

View full text Add to dashboard Cite

show abstract

“…It is also unclear how data is modeled. The recent work to be published in [4] gives a precise and well-structured semantics of BPMN using Abstract State Machines. This is, to our knowledge, the largest coverage of BPMN besides ours.…”

Section: Related Workmentioning

confidence: 99%

Formal Analysis of BPMN Models Using Event-B

Bryans

Wei²

2010

Formal Methods for Industrial Critical Systems

View full text Add to dashboard Cite

Abstract. The use of business process models has gone far beyond documentation purposes. In the development of business applications, they can play the role of an artifact on which high level properties can be verified and design errors can be revealed in an effort to reduce overhead at later software development and diagnosis stages. This paper demonstrates how formal verification may add value to the specification, design and development of business process models in an industrial setting. The analysis of these models is achieved via an algorithmic translation from the de-facto standard business process modeling language BPMN to Event-B, a widely used formal language supported by the Rodin platform which offers a range of simulation and verification technologies.

show abstract

“…They have also been used to develop safety‐critical systems, eg, the commuter rail service, the haemodialysis machine, and aeroplane components . Besides the work on formalising BPMN using ASMs, several other approaches towards a formal semantics of business process modelling languages exist, eg, using Petri nets or Z . While the subject of adaptivity and exception handling has been addressed in various contexts, the investigation of a methodology for static and dynamic business process adaptations in a fully integrated and formal model is new.…”

Section: Introductionmentioning

confidence: 99%

Towards functional safety and security for adaptive and flexible business processes

Geist

Natschläger

Illibauer

et al. 2018

J Software Evolu Process

View full text Add to dashboard Cite

Business process management (BPM) provides many benefits for a company including productivity, efficiency, compliance, risk management, consistency, repeatability, and measurability. Many of these aspects also ensure and improve functional safety, privacy, and security in process execution. However, managed business processes lack flexibility; ie, changing a business process requires more effort than ad hoc execution and adaptation. Thus, especially in small companies, the acceptance rate of managed business processes is low. So we claim that in current BPM approaches, the structuredness ensuring functional safety and security concepts contradicts with the objective for flexibility. The main goal of the AdaBPM project is to address this contradiction by providing a formal approach to handle advanced adaptations and exception handling in business processes. The technical objectives of the project include (1) the definition of a basic framework being capable of handling different levels of adaptivity and considering security and safety requirements at the same time, (2) a rigorous process specification language and model refinement methods,(3) static business process adaptations, and (4) dynamic (or ad hoc) adaptations. The result of our research is a general approach for flexible BPM combined with the possibility to nevertheless manage the process and define safety and security restrictions.

show abstract

BPMN Core Modeling Concepts: Inheritance-Based Execution Semantics

Cited by 26 publications

References 6 publications

Approaches to modeling business processes: a critical analysis of BPMN, workflow patterns and YAWL

Approaches to modeling business processes: a critical analysis of BPMN, workflow patterns and YAWL

Formal Analysis of BPMN Models Using Event-B

Towards functional safety and security for adaptive and flexible business processes

Contact Info

Product

Resources

About