Topic
Business Process Model and Notation
About: Business Process Model and Notation is a research topic. Over the lifetime, 9038 publications have been published within this topic receiving 190712 citations. The topic is also known as: Business Process Modeling Notation & BPMN.
Papers published on a yearly basis
Papers
More filters
••
TL;DR: The main contributions from this research include the knowledge representation structure and a collaborative tool supporting visual composition of business process models.
54 citations
••
13 Dec 1994
TL;DR: The Leu approach to business process management considers data models, activity models, and organization models as separate, but equally important, facets of business processes.
Abstract: Most of todays approaches to business process engineering (also called business process management) start from an activity-centered perspective. They describe activities to be carried out within a business process and their relationships, but they usually pay little attention to the objects manipulated within processes. In this article we discuss an approach to business process management which is based on modeling data-related, activity-related, and organizational aspects of business processes. In fact, the Leu approach to business process management considers data models (describing types of objects to be manipulated in a business process and their relationships), activity models (describing activities to be carried out in a business process), and organization models (describing organizational entities involved in a business process) as separate, but equally important, facets of business processes.
54 citations
•
01 Jan 2008
TL;DR: This book is for CIOs, executives, SOA project managers, business process analysts, BPM and SOA architects, who are responsible for improving the efficiency of business processes through IT, or for designing SOA
Abstract: Learn how to model business processes in an SOA-compliant approach using BPMN, translate them into BPEL and execute them on the SOA platform. A practical guide with real-world examples illustrating all key concepts. This book is for CIOs, executives, SOA project managers, business process analysts, BPM and SOA architects, who are responsible for improving the efficiency of business processes through IT, or for designing SOA. It provides a high-level coverage of business process modeling, but it also gives practical development examples on how to move from model to execution. We expect the readers to be familiar with the basics of SOA.
54 citations
••
IBM1
TL;DR: This paper presents several extensions to existing notions of compensation for business transactions using a business process modeling language called StAC (Structured Activity Compensation) but are also placed in the context of IBM's BPBeans (Business Process Beans) enterprise technology.
Abstract: The ability to compensate for previous activities, often in the case of failure or exceptional events, is an important feature of long-running business transactions. In this paper, we present several extensions to existing notions of compensation for business transactions. The extensions are described using a business process modeling language called StAC (Structured Activity Compensation) but are also placed in the context of IBM's BPBeans (Business Process Beans) enterprise technology. The meaning of the compensation mechanisms is made precise, as are issues of compensation scoping in multilevel transactions. The compensation extensions result in flexible and powerful mechanisms for modeling and implementing long-running business transactions.
53 citations
••
05 Dec 2011TL;DR: A feature-based approach is proposed that is able to effectively model variability within and across compositions and is supported by a process development methodology that enables the systematic reuse and management of variability.
Abstract: Variability in process-based service compositions needs to be explicitly modeled and managed in order to facilitate service/process customization and increase reuse in service/process development. While related work has been able to capture variability and variability dependencies within a composition, these approaches fail to capture variability dependenciesbetween the composition and partner services. Consequently, these approaches cannot address the situation when a composite service is orchestrated from partner services some of which are customizable. In this paper, we propose a feature-based approach that is able to effectively model variability within and across compositions. The approach is supported by a process development methodology that enables the systematic reuse and management of variability. We develop a prototype system supporting extended BPMN 2.0 to demonstrate the feasibility of our approach.
53 citations