An Architecture for Bridging OO and Business Process Modeling
TOOLS '00 Proceedings of the Technology of Object-Oriented Languages and Systems (TOOLS 33)
Data flow and validation in workflow modelling
ADC '04 Proceedings of the 15th Australasian database conference - Volume 27
Formulating the Data-Flow Perspective for Business Process Management
Information Systems Research
Oryx --- An Open Modeling Platform for the BPM Community
BPM '08 Proceedings of the 6th International Conference on Business Process Management
Specification, Verification and Explanation of Violation for Data Aware Compliance Rules
ICSOC-ServiceWave '09 Proceedings of the 7th International Joint Conference on Service-Oriented Computing
Consistency of business process models and object life cycles
MoDELS'06 Proceedings of the 2006 international conference on Models in software engineering
A framework for querying graph-based business process models
Proceedings of the 19th international conference on World wide web
Generation of business process models for object life cycle compliance
BPM'07 Proceedings of the 5th international conference on Business process management
| Hi-index | 0.00 |
Most commonly used business process (BP) notations, such as BPMN, focus on defining the control flow of the activities of a BP, i.e., they are activity-centered. In these notations, data play a secondary role, just as inputs or outputs of the activities. However, there is an increasing interest in analysing the life cycle of the data objects that are handled in a BP because it helps understand how data is modified during the execution of the process, detect data anomalies such as checking whether an activity requires a data object in a state that is unreachable, and check data compliance rules such as checking whether only a certain role can change the state of a data object. To carry out such an analysis, it is very appealing to provide a mechanism to transform from the usual activity-centered model of a BP to the set of life cycles of all the data objects involved in the process (i.e., a data-centered model). Unfortunately, although some proposals describe such transformation, they do not deal with data anomalies in the original BP model nor include information about the activities of the BP that are executed in the state transitions of the data object, which limits the analysis capabilities of the life cycle models. In this paper, we describe a model-driven procedure to automatically transform from an activity-centered model to a data-centered model of a BP that solves the aforementioned limitations of other proposals.