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
01 Jan 2005
TL;DR: This paper presents a simple, yet instructive example of how a BPMN diagram can be used to generate a BPEL process.
Abstract: The Business Process Modeling Notation (BPMN) has been developed to enable business user to develop readily understandable graphical representations of business processes. BPMN is also supported with appropriate graphical object properties that will enable the generation of executable BPEL. Thus, BPMN creates a standardized bridge for the gap between the business process design and process implementation. This paper presents a simple, yet instructive example of how a BPMN diagram can be used to generate a BPEL process.
212 citations
••
TL;DR: In this article, the authors present the findings of a longitudinal study of a large corporation's transition to a new business model in the face of a major transformation in the ICT industry brought about by Cloud computing.
Abstract: This paper presents the findings of a longitudinal study of a large corporation's transition to a new business model in the face of a major transformation in the ICT industry brought about by Cloud computing. We build theory on the process of business model innovation through a qualitative study that investigates how an established firm organizes for an emerging business model. Contrary to previous findings that presented spatial separation as the optimal structural approach for dealing with two competing business models, our findings indicate a need for recursive iterations between different modes of separated and integrated structures in line with the emergent nature of strategic intent toward the new business models. Our analyses reveal strategy formation to be a collective experimental learning process revolving around a number of alternative strategic intentions ranging from incremental evolution and transformation to complete replacement of the existing business model. Given the fundamental differences in the nature and requirements of those alternative intents, iterations between different structural modes and differing combinations proved to be crucial in enabling the organization to make transition to the new business model.
211 citations
•
15 Jan 1993
TL;DR: In this paper, the authors present a method and system which provides consultants, business process analysts, and application developers with a unified tool with which to conduct business process analysis, design, and documentation.
Abstract: The invention is a method and system which provides consultants, business process analysts, and application developers with a unified tool with which to conduct business process analysis, design, and documentation The invention may be implemented using a software system which has two functional sets One is a set of graphical tools that can be used by a developer or business analyst to map out business processes The second is a set of tools that can be used to document and specify in detail the attributes of each workflow definition, including roles, timing, conditions of satisfaction, forms, and links required to complete a business process definition The invention utilizes fundamental concept of workflow analysis that any business process can be interpreted as a sequence of basic transactions called workflows
210 citations
••
15 Nov 2004TL;DR: This paper proposes a hybrid composition approach that allows for a more modular and flexible web service composition and discusses two alternative technologies for implenting business rules in encapsulated units, using aspects and a rule-based engine.
Abstract: Over the last few years several process-based web service composition languages have erged, such as BPEL4WS and BPML. These languages define the composition on the basis of a process that specifies the control and data flow among the services to be composed. In this approach, the whole business logic underlying the composition including business policies and constraints is coded as a monolithic block. As a result, business rules are hard to change without affecting the core composition logic. In this paper, we propose a hybrid composition approach: The composition logic is broken down into a core part (the process) and several well-modularized business rules that exist and evolve independently. We also discuss two alternative technologies for implenting business rules in encapsulated units, using aspects and a rule-based engine. Our approach allows for a more modular and flexible web service composition.
210 citations
•
01 Feb 1996
TL;DR: The IDEF Process Mapping Methodology as mentioned in this paper is a set of guidelines for process mapping software tool selection and implementation, as well as a collection of data for process Mapping.
Abstract: Do You Need a Roadmap? Reengineer Your Business Processes. Role of Process Mapping in Reengineering. Do You Really Understand Your Processes? Process Mapping Success Stories. IDEF Process Mapping Methodology. Create a Process Mapping Team. Process Mapping Software Tool Selection. How to Collect Data for Process Mapping. Process Map Implementation. Change It! Notes. Suggested Reading. Acronyms. Points of Contact. Glossary. Index.
209 citations