Markus Kradolfer, Andreas Geppert "Dynamic Workflow Schema Evolution based on Workflow Type Versioning and Workflow Migration", Technical Report 98.02, Department of Computer Science, University of Zurich, April 1998 Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
A Management System for Evolving Development Processes - Heller, Schleicher.. (2003) (Correct)
....process evolution. To realize this approach, we have to work both bottom up and top down: we learn from actual performance (bottom up) and propagate changes to process definitions top down. In contrast, most other approaches are confined to top down evolution. For example, in [10] 12] 15] [17], the process definition has to be created beforehand, while we allow for executing partially known process definitions. Modifications to process definitions may be performed in place, as in [30] 5] However, it seems more appropriate to create a new version of the definition in order to ....
....Modifications to process definitions may be performed in place, as in [30] 5] However, it seems more appropriate to create a new version of the definition in order to provide for traceability. Version control is applied at different levels of granularity such as class versioning [15] [17] and schema versioning [4] Our approach is similar to class versioning (interface and realization packages for individual task types are submitted to version control) Different migration strategies may be applied in order to propagate changes at the definition level to the instance level. A ....
[Article contains additional citation context not shown here]
M. Kradolfer and A. Geppert. Dynamic workflow schema evolution based on workflow type versioning and workflow migration. In Proceedings of the International Conference on Cooperative Information Systems (CoopIS`99), pages 104--114, Edinburgh, Sept. 1999. IEEE Computer Society Press.
Schema Evolution in Heterogeneous Database Architectures, .. - McBrien, Poulovassilis (2002) (9 citations) (Correct)
....schema transformations. As we will see below, an advantage of our approach over query oriented approaches is that it allows systematic repair of global schemas as source schemas evolve. Much of the previous work on schema evolution has presented approaches in terms of just one data model e.g. [1, 4, 5, 11]. In contrast, we represent higher level data modelling languages in terms of an underlying hypergraph based data model [17] Thus, the techniques for handling source schema evolutions that we propose in this paper can be applied to any of the common data modelling languages. In [12] it was ....
M. Kradolfer and A. Geppert. Dynamic workflow schema evolution based on workflow type versioning and workflow migration. In Proceedings of CoopIS 1999, pages 104-114, 1999.
On Building Workflow Models for Flexible Processes - Mangan, Sadiq (2002) (1 citation) (Correct)
....business process evolves in response to competitive and regulatory influence, still exists. The biggest problem is the handling of the active instances that were initiated in the old model. Defining a migration strategy is a complex problem and has been the target of extensive research [CCP 96] [KG99], LOL98] Sad00a] Furthermore the need to handle exceptions to cater for instances that cannot be anticipated at design must also be supported. As the support for this level of change is required in the traditional workflow implementations considerable work has been devoted to it also [RD97] ....
MARKUS KRADOLFER, ANDREAS GEPPERT. (1999) Dynamic Workflow Schema Evolution based on Workflow Type Versioning and Workflow Migration. Proccedings of the Fourth IFCIS International Conference on Cooperative Information Systems (CoopIS99). Edinburgh, Scotland. Sep 2-4, 1999.
Schema Evolution in Heterogeneous Database Architectures, .. - McBrien, Poulovassilis (2002) (9 citations) (Correct)
....schema transformations. As we will see below, an advantage of our approach over query oriented approaches is that it allows systematic repair of global schemas as source schemas evolve. Much of the previous work on schema evolution has presented approaches in terms of just one data model e.g. [1, 4, 5, 11]. In contrast, we represent higherlevel data modelling languages in terms of an underlying hypergraph based data model [17] Thus, the techniques for handling source schema evolutions that we propose in this paper can be applied to any of the common data modelling languages. In [12] it was argued ....
M. Kradolfer and A. Geppert. Dynamic workflow schema evolution based on workflow type versioning and workflow migration. In Proceedings of CoopIS
Schema Evolution in Heterogeneous Database Architectures, .. - McBrien, Poulovassilis (2002) (9 citations) (Correct)
....of source schemas; and, as we will see below, iv) enabling the systematic repair of global schemas and global query translation in the face of evolving source schemas. Much of the work on schema evolution has presented approaches in terms of just one data model e.g. ER [1] OO [4, 5] or workflow [10]. In contrast, our approach of representing higherlevel data modelling languages in terms of an underlying hypergraph based data model allows us to propose in this paper a method which can be applied to any of the common data modelling languages. In [11] it was argued that a uniform approach to ....
M. Kradolfer and A. Geppert. Dynamic workflow schema evolution based on workflow type versioning and workflow migration. In Proceedings of CoopIS 1999, pages 104--114, 1999.
Tolerating Exceptions in Workflows: a Unified Framework for.. - Borgida, Murata (1999) (7 citations) (Correct)
....respective step attributes) for the workflow. The advantage of our approach is that even this (meta )constraint may be violated with suitable excusing privileges. 6 RELATED WORK AND CONCLUSIONS To begin with, there have been many papers on the evolution of workflow and process models, including [1, 2, 4, 11, 18, 19, 26, 32, 34]. We believe there is a distinction to be made between deviations during workflow enactment (the topic of this paper) and workflow evolution. The difference is analogous to the one between allowing exceptional individuals in a database (e.g. 7] and schema evolution in a database (e.g. 5] ....
M. Kradolfer, A. Geppert "Dynamic Workflow Schema Evolution based on Workflow Type Versioning and Workflow Migration", TR 98.02, Dept. of Computer Science, University of Zurich, April 1998
Managing Evolving Workflow Specifications With Schema.. - Joeris, Herzog (1999) (8 citations) (Correct)
....depend on the general purpose schema evolution primitives of the OODBMS ADOME. Specific problems of workflow schema versioning as mentioned in section 4. 1 as well as different propagation strategies are not discussed by Chiou et al. To the best of our knowledge, the work of Kradolfer and Geppert [36] is the only one which also discusses workflow schema versioning. But the proposed versioning approach does not distinguish between the versioning of a whole workflow type and the versioning of the body. Therefore, workflow changes cannot be encapsulated, but require the definition of a new ....
Kradolfer M., Geppert A.: Dynamic Workflow Schema Evolution based on Workflow Type Versioning and Workflow Migration. Technical Report 98.02, Department of Computer Science, University of Zurich (1998).
Enabling Technologies For Electronic Commerce - Kappel, Retschitzegger, Schröder (1998) (Correct)
....rapid changes in the business environment, there is a need to dynamically reengineer and optimize the workflow type itself while possibly several workflow instances of this type are active. For this purpose, appropriate migration strategies as well as versioning mechanisms have to be developed [Krad98]. A promising technique to cope with these adaptability requirements are active mechanisms in terms of Event Condition Action rules since they allow for an event driven realization of context and timedependent behaviour, which may be manipulated at runtime [Kapp98] 2.2. Interoperability of ....
KRADOLFER, M., GEPPERT, A., Dynamic Workflow Schema Evolution based on Workflow Type Versioning and Workflow Migration, Technical Report, The Database Technology Research Group, Department of Computer Science, University of Zurich, 1998.
Issues on Workflow Specification and Execution - Geppert, Kradolfer, Tombros (1998) Self-citation (Kradolfer Geppert) (Correct)
....be reached. The TRAMs workflow specification approach provides additional concepts, such as iteration blocks to support the iterative execution of workflows, parallel blocks to support the parallel execution of a variable number of workflows, organizational modeling, and dynamic schema evolution [13]. As an example, consider a complex workflow type HIC (see Fig. 1a) defined in a health insurance company which specifies the process of determining whether a health insurance claim (HIC) is to be accepted or not. As the first step to be carried out, the workflow type defines a subworkflow ....
M. Kradolfer and A. Geppert. Dynamic Workflow Schema Evolution based on Workflow Type Versioning and Workflow Migration. Technical Report 98.02, Department of Computer Science, University of Zurich, 1998.
Workflows as Persistent Objects with Persistent Exceptions - Framework For Flexibility (Correct)
No context found.
Markus Kradolfer, Andreas Geppert "Dynamic Workflow Schema Evolution based on Workflow Type Versioning and Workflow Migration", Technical Report 98.02, Department of Computer Science, University of Zurich, April 1998
Approaches for Guideline Versioning Using GLIF - Peleg, Kantor (2003) (Correct)
No context found.
Kradolfer M, Geppert A. Dynamic Workflow Schema Evolution Based on Workflow Type Versioning and Workflow Management. In: Proceedings. 3rd IFCIS International Conference on Cooperative Information Systems; 1999. p. 104-114.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC