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.

Time-BPMN

Abstract: We present Time-BPMN which is an extension to the current version of the Business Process Modeling Notation (BPMN). Time-BPMN captures the temporal perspective of business processes. This extension deals with the various temporal constraints and dependencies that may occur while characterizing real world business processes. Time-BPMN allows for the specification and depiction of temporal constraints and dependencies within a BPMN diagram. It not only extends, but also simplifies certain existing temporal BPMN constructs. With our extension, BPMN becomes expressive enough to account for a very large set of real world business processes that are time dependent.

Policy-driven exception-management for composite Web services

Abstract: Process-based composition of Web services has recently gained significant momentum in the implementation of business processes. A critical and time-consuming part of business process development is the detection and handling of exceptions that may occur during process execution. In this paper, we introduce a novel, policy-driven approach to exception management, which substantially simplifies business process development. We advocate that exception management should be implemented in the system infrastructure. Using our exception management framework, developers define exception policies in a declarative manner. Before a business process is executed, the service composition middleware integrates the exception policies with normal business logic to generate an exception-aware process schema. We argue that our policy-driven approach significantly reduces the development time of business processes through its separation of the development of the business logic and the exception handling policies.

Requirements of an Open Data Based Business Ecosystem

Abstract: Emerging opportunities for open data based business have been recognized around the world. Open data can provide new business opportunities for actors that provide data, for actors that consume data, and for actors that develop innovative services and applications around the data. Open data based business requires business models and a collaborative environment-called an ecosystem-to support businesses based on open data, services, and applications. This paper outlines the open data ecosystem (ODE) from the business viewpoint and then defines the requirements of such an ecosystem. The outline and requirements are based on the state-of-the-art knowledge explored from the literature and the state of the practice on data-based business in the industry collected through interviews. The interviews revealed several motives and advantages of the ODE. However, there are also obstacles that should be carefully considered and solved. This paper defines the actors of the ODE and their roles in the ecosystem as well as the business model elements and services that are needed in open data based business. According to the interviews, the interest in open data and open data ecosystems is high at this moment. However, further research work is required to establish and validate the ODE in the near future.

Dimensions of Business Processes Quality (QoBP)

Abstract: Conceptual modeling is an important tool for understanding and revealing weaknesses of business processes. Yet, the current practice in reengineering projects often considers simply the as-is process model as a brain-storming tool. This approach heavily relies on the intuition of the participants and misses a clear description of the quality requirements. Against this background, we identify four generic quality categories of business process quality, and populate them with quality requirements from related research. We refer to the resulting framework as the Quality of Business Process (QoBP) framework. Furthermore, we present the findings from applying the QoBP framework in a case study with a major Australian bank, showing that it helps to systematically fill the white space between as-is and to-be process modeling.

E-market architecture for supporting multiple roles and reconfigurable business porcesses

Abstract: A method for allowing flexible creation and alteration of business processes within a commerce system includes using state machines to describe the actions that can be taken by particular roles at particular points in a process. The state machines are used by a commerce system to enforce validity of user actions, to track the execution of actions within an instance of the business process, to provide the user interface with a list of actions available to a user working on an instance of the business process, to provide coordination between state machines, and to allow different organizations to have varied business processes.