Results 1 - 10
of
14
A framework for querying graph-based business process models
- In Proceedings of the 19th International Conference on World Wide Web, WWW ’10
, 2010
"... We present a framework for querying and reusing graph-based busi-ness process models. The framework is based on a new visual query language for business processes called BPMN-Q. The language ad-dresses processes definitions and extends the standard BPMN vi-sual notations for modeling business proces ..."
Abstract
-
Cited by 16 (10 self)
- Add to MetaCart
(Show Context)
We present a framework for querying and reusing graph-based busi-ness process models. The framework is based on a new visual query language for business processes called BPMN-Q. The language ad-dresses processes definitions and extends the standard BPMN vi-sual notations for modeling business processes for its concrete syn-tax. BPMN-Q is used to query process models by matching a pro-cess model graph to a query graph. Moreover, the reusing frame-work is enhanced with a semantic query expander component. This component provides the users with the flexibility to get not only the perfectly matched process models to their queries but also the models with high similarity. The query engine of the framework is built on top of traditional RDBMS. A novel decomposition-based and selectivity-aware relational processing mechanism is employed to achieve an efficient and scalable performance for graph-based BPMN-Q queries.
The Difference Between Graph-Based and Block-Structured Business Process Modelling Languages
- ENTERPRISE MODELLING AND INFORMATION SYSTEMS ARCHITECTURE
, 2009
"... The most prominent business process notations in use today are BPMN, EPC and BPEL. While all those languages show similarities on the conceptual level and share similar constructs, the semantics of these constructs and even the intended use of the language itself are often quite different. As a resu ..."
Abstract
-
Cited by 16 (4 self)
- Add to MetaCart
The most prominent business process notations in use today are BPMN, EPC and BPEL. While all those languages show similarities on the conceptual level and share similar constructs, the semantics of these constructs and even the intended use of the language itself are often quite different. As a result, users are uncertain when to use which language or construct in a particular language, especially when they have used another business process notation before. In this paper, we discuss the core characteristics of graph-based and block-structured modelling languages and compare them with respect to their join and loop semantics.
Towards modeling real-world aware business processes
- In Proceedings of Web of Things
, 2011
"... In this paper we aim at bringing together the Web of Things (WoT) domain with the domain of enterprise business process modeling in order to work towards a Future Internet that includes all layers of networked technology stacks. We suggest introducing new notation concepts to the current business pr ..."
Abstract
-
Cited by 4 (0 self)
- Add to MetaCart
(Show Context)
In this paper we aim at bringing together the Web of Things (WoT) domain with the domain of enterprise business process modeling in order to work towards a Future Internet that includes all layers of networked technology stacks. We suggest introducing new notation concepts to the current business process modeling standards to facilitate modeling WoT aware business processes. We obtain and classify known WoT specific properties of real-world business processes. By means of a sensor based case study we analyze existing business process modeling standards such as
An Extension of BPMN Meta-model for Evaluation of Business Processes
"... Abstract – Business process modeling is used for better understanding and communication of company’s processes. Mostly, business process modeling is discussed from the information system development perspective. Execution of a business process involves various factors (costs and time) which are impo ..."
Abstract
-
Cited by 3 (2 self)
- Add to MetaCart
(Show Context)
Abstract – Business process modeling is used for better understanding and communication of company’s processes. Mostly, business process modeling is discussed from the information system development perspective. Execution of a business process involves various factors (costs and time) which are important and should be represented in business process models. Controlling of business units uses post execution analysis for detection of failures for improvement. The process models conceived for information system development are not sufficient for post execution analysis. This paper focuses on the challenges of business process modeling in the post execution context. We provide a meta model for evaluation of a business process and discuss BPMN in this context. We also extend existing BPMN meta model for performance analysis of business processes. The proposed extensions are presented with the help of an example.
Realising Dead Path Elimination in BPMN
"... guage (BPEL) lacks any standard graphical notation. Various efforts have been undertaken to visualize BPEL using the Business Process Modelling Notation (BPMN). Although this is straightforward for the majority of concepts, it is tricky for the full BPEL standard, partly due to the insufficiently sp ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
(Show Context)
guage (BPEL) lacks any standard graphical notation. Various efforts have been undertaken to visualize BPEL using the Business Process Modelling Notation (BPMN). Although this is straightforward for the majority of concepts, it is tricky for the full BPEL standard, partly due to the insufficiently specified BPMN execution semantics. The upcoming BPMN 2.0 revision will provide this clear semantics. In this paper, we show how the dead path elimination (DPE) capabilities of BPEL can be expressed with this new semantics and discuss the limitations. We provide a generic formal definition of DPE and discuss resulting control flow requirements independent of specific process description languages. Keywords-BPEL, BPMN, dead path elimination, model trans-formation, round-tripping, process model alignment I.
Detection of Process Antipatterns: A BPEL Perspective
"... Abstract—With the increasing significance of the serviceoriented paradigm for implementing business solutions, assessing and analyzing such solutions also becomes an essential task to ensure and improve their quality of design. One way to develop such solutions, a.k.a., Service-Based systems (SBSs) ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract—With the increasing significance of the serviceoriented paradigm for implementing business solutions, assessing and analyzing such solutions also becomes an essential task to ensure and improve their quality of design. One way to develop such solutions, a.k.a., Service-Based systems (SBSs) is to generate BPEL (Business Process Execution Language) processes via orchestrating Web services. Development of large business processes (BPs) involves design decisions. Improper and wrong design decisions in software engineering are commonly known as antipatterns, i.e., poor solutions that might affect the quality of design. The detection of antipatterns is thus important to ensure and improve the quality of business processes. However, although BP antipatterns have been defined in the literature, no effort was given to detect such antipatterns within BPEL processes. With the aim of improving the design and quality of BPEL processes, we propose the first rule-based approach to specify and detect BP antipatterns. We specify 7 BP antipatterns from the literature and perform the detection for 4 of them in an initial experiment with 3 example BPEL processes. Keywords-Business processes; Antipatterns; Service-based systems; Specification; Detection; Design;
Communicated by Athman Bouguettaya.
, 2012
"... Abstract In process-driven, service-oriented architectures (SOAs), process activities can perform service operations, data transformations, or human tasks. Unfortunately, the process activities are usually tightly coupled. Thus, when the number of activities in the process grows, focusing on particu ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract In process-driven, service-oriented architectures (SOAs), process activities can perform service operations, data transformations, or human tasks. Unfortunately, the process activities are usually tightly coupled. Thus, when the number of activities in the process grows, focusing on particular activities of the flow such as the service operations reading or writing persistent data is a time-consuming task. In particular, in order to solve structural problems concerning persistent data access such as deadlocks in data-intensive business processes, stakeholders need to understand the underlying persistent data access details of the activities i.e. physical storage schemes, and database connections. With our view-based model-driven approach, we provide a solution to generate flows of persistent data access activities (which we refer to as persistent data access flows). To the best of our knowledge these persistent data access flows are not used to solve structural problems in process-driven SOAs, yet. Moreover, our persistent data access flows can be flattened by diverse filer criteria e.g. by filtering all activities reading or writing from a specific database or table. Using our approach, we can enhance traceability and documentation of persistent data access in business processes. In a series of motivating scenarios from an industrial case study we present how our persistent data access flow concept can contribute to enhance productivity in service-
PREPRINT Maximal Structuring of Acyclic Process Models
, 2012
"... This article addresses the transformation of a process model with an arbitrary topology into an equivalent structured process model. In particular, this article studies the subclass of process models that have no equivalent well-structured representation but which, nevertheless, can be partially str ..."
Abstract
- Add to MetaCart
This article addresses the transformation of a process model with an arbitrary topology into an equivalent structured process model. In particular, this article studies the subclass of process models that have no equivalent well-structured representation but which, nevertheless, can be partially structured into their maximally-structured representation. The transformations are performed under a behavioral equivalence notion which preserves the observed concurrency of tasks in equivalent process models. The article gives a full characterization of the subclass of acyclic process models that have no equivalent well-structured representation but do have an equivalent maximally-structured one, as well as proposes a complete structuring method. Together with our previous results, this article completes the solution of the process model structuring problem for the class of acyclic process models.
Automatic Transformation from Graphical Process Models to Executable Code
, 2010
"... Model-driven engineering envisions a paradigm shift from block-oriented, textual descriptions of behavior to graph-oriented, visual descriptions similar in significance to the paradigm shift from low-level assembler languages to high-level programming languages. One challenging question in this area ..."
Abstract
- Add to MetaCart
(Show Context)
Model-driven engineering envisions a paradigm shift from block-oriented, textual descriptions of behavior to graph-oriented, visual descriptions similar in significance to the paradigm shift from low-level assembler languages to high-level programming languages. One challenging question in this area is how to transform a behavioral model of a system from a graph-oriented language (e.g., UML Activity Diagrams or BPMN) into a block-oriented language (e.g., BPEL) or vice versa. Part of this problem is the transformation from unstructured (usually visual) process models to structured (executable) program code to which this paper proposes a solution that can handle all sound sequential, parallel and mixed regions. It has been implemented as an extension of the IBM WebSphere Business Modeler and applied to many business processes including dozens from the IBM reference model for insurance companies called Insurance Application Architecture. Key words: Process modeling; control flow; model transformation; UML; BPMN; BPEL 1
