An Artifact-Centric Approach to Dynamic Modification of Workflow Execution

Xü, Wei; Su, Jianwen; Yan, Zhimin; Yang, Jian; Zhang, Liang

doi:10.1007/978-3-642-25109-2_17

Cited by 27 publications

(25 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Their prototype was developed and presented in [15,17]. To support a dynamic runtime modification, Xu et al [11] developed a hybrid model called EZ-Flow based on the ArtiFlow to gain advantages of both declarative and procedural natures. Compared with our approach, we execute an artifact-centric model without converting the model to an activity-centric model.…”

Section: Related Work Discussion and Conclusionmentioning

confidence: 99%

A Workflow Execution Platform for Collaborative Artifact-Centric Business Processes

Yongchareon

Ngamakeur

Liu

et al. 2014

On the Move to Meaningful Internet Systems: OTM 2014 Workshops

View full text Add to dashboard Cite

Abstract.To execute an artifact-centric process model, current workflow execution approaches require it to be converted to some existing executable language (e.g., BPEL) in order to run on a workflow system. We argue that the transformation can incur losses of information and degrade traceability. In this paper, we proposed and developed a workflow execution platform that directly executes a collaborative (i.e., inter-organizational) workflow specification of artifact-centric business processes without performing model conversion.

show abstract

Section: Related Work Discussion and Conclusionmentioning

confidence: 99%

A Workflow Execution Platform for Collaborative Artifact-Centric Business Processes

Yongchareon

Ngamakeur

Liu

et al. 2014

On the Move to Meaningful Internet Systems: OTM 2014 Workshops

View full text Add to dashboard Cite

show abstract

“…With this approach, we are able to easily adapt BPs in response to changes in business environment. This advantage of the artifact model has been proved in many researches (e.g., in [2], [3], [5]). In our platform, an artifact-centric process model is realized using a direct approach, i.e., no model conversion needed.…”

Section: Flexibility and Changes Managementmentioning

confidence: 90%

Notice of Removal An Artifact-Centric Business Process Execution Platform

Ngamakeur

Yongchareon

Liesaputra

et al. 2016

2016 IEEE 20th International Enterprise Distributed Object Computing Workshop (EDOCW)

View full text Add to dashboard Cite

Abstract-Artifact-centric modeling has become an alternative, yet promising approach of business process (BP) modeling and management as it provides higher flexibility than that of traditional activity-centric approaches. However, existing BP execution engines require artifact-centric models be transformed to executable activity-centric BP languages (e.g., BPEL) in order to be executed and managed. We argue that the model conversion incurs losses of information and affects traceability and monitoring ability of BPs, especially where BPs span across inter-organizations. In this paper, we present the design and implementation of an execution platform for artifactcentric BPs. We evaluated our platform using a case study and that can demonstrate several key benefits over the use of existing systems to run artifact-centric BPs.

show abstract

“…Broadly speaking, changes may be applied to either workflow models (e.g., removing an approval step due to a natural disaster) or process instances (e.g., encountering an unexpected situation) [5]. Earlier studies on workflow change focus primarily on process model changes concerning correctness [10], while instance changes were not investigated except the work reported in [22]. However, all earlier studies either consider no data in workflow (e.g., Petri net based models [5] [10]) or data in form of variables (e.g., [3]) or business artifacts [22], none of these studies actually considered persistent data (local stores or enterprise database).…”

Section: Case 3: Execution Engine Failurementioning

confidence: 96%

“…Earlier studies on workflow change focus primarily on process model changes concerning correctness [10], while instance changes were not investigated except the work reported in [22]. However, all earlier studies either consider no data in workflow (e.g., Petri net based models [5] [10]) or data in form of variables (e.g., [3]) or business artifacts [22], none of these studies actually considered persistent data (local stores or enterprise database). As discussed in the first scenario, what a process (instance) sees during an execution is not always what the persistent databases provide.…”

Section: Case 3: Execution Engine Failurementioning

confidence: 97%

Yank Your Data Out of My Engine: A New Approach to Workflow System Design

Yang

2015

2015 IEEE 19th International Enterprise Distributed Object Computing Workshop

Self Cite

View full text Add to dashboard Cite

Business process (or workflow) management is vital in enterprise application systems. Current workflow management systems (WfMSs) do not provide a clear separation between execution management and data management; such a lack of separation causes serious difficulties in managing data consistency and process change. This paper argues for an "execution independence" principle of isolating the two and thus their respective concerns. Following this principle, "universal artifacts" and a new conceptual architecture for WfMSs are developed, which help addressing many challenging issues in application development with the current WfMSs.

show abstract

An Artifact-Centric Approach to Dynamic Modification of Workflow Execution

Cited by 27 publications

References 13 publications

A Workflow Execution Platform for Collaborative Artifact-Centric Business Processes

A Workflow Execution Platform for Collaborative Artifact-Centric Business Processes

Notice of Removal An Artifact-Centric Business Process Execution Platform

Yank Your Data Out of My Engine: A New Approach to Workflow System Design

Contact Info

Product

Resources

About