P. Bichler, G. Preuner, and M. Schrefl. Workflow Transparency. In A. Oliv e and J.A. Pastor, editors, Proceedings of the 9th International Conference on Advanced Information Systems Engineering (CAiSE `97), Barcelona, Spain, volume 1250 of Lecture Notes in Computer Science, pages 423--436. Springer, June 1997.  Home/Search   Document Details and Download   Summary   Related Articles   Check

.... or late modeling ( Han96] Hage97] the support of adaptive WFs by allowing dynamic changes of running WF instances; a dynamic change may affect a single WF instance ( JST97] KRW90] Nutt96] Sieb96] Tee96] or all (or part of the) active instances of a specific WF type (WF evolution) [BPS97], Casa96] EKR95] the integration of WfMSs with collaboration and groupware technologies to combine formal and wellstructured processes with informal group processes ( ShKo97] Webe97] the handling of task failures or abnormally terminated WFs ( KaRa96] Hsu95] WoSh97] In the ....

....be executed according to the old schema or to the new one. Casati et al. propose a set of change primitives and evolution policies. Formal criteria are introduced in order to determine which WF instances can be transparently migrated to the new schema. A similar approach is followed by OBD bp wf [BPS97]. Still an open research issue is the question how to integrate dynamic structural changes at the schema level with ad hoc structural changes of single active WF instances. Several proposals have been made to combine formal and well structured processes with informal group processes. ....

Bichler, P.; Preuner, G.; Schrefl, M. Workflow Transparency. Proc. CAiSE 97, Barcelona, 1997

....and evolution of workflow specifications (illustrated in figure 1 in bold face) A. Support for the management of evolving workflow schemata: Different workflow schema versions have to be managed and different propagation strategies of workflow schema changes to their workflow instances (cf. [5, 10, 16, 9]) have to be provided by a WFMS in order to flexibly support the migration from one business process to an improved one, to support alternative workflows for process variants, and to support ad hoc changes of a workflow. For propagating workflow schema changes to their instances we have to ....

....manually by the process designer or automatically by the WFMS according to the instance execution states. migration strategy for selective propagation: Beside the immediate migration, the migration to the new schema has possibly to be delayed until the instance has reached a required state (cf. [5]) Furthermore, different variants for different instance selections as well as local adjustments to some workflow instances have to be supported. local adjustments modifications and upward propagation: A special case of selective propagation is the change of the workflow definition for exactly ....

[Article contains additional citation context not shown here]

Bichler P., Preuner G., Schrefl, M.: Workflow Transparency. In Proc. of 9 th Int. Conf. on Advanced Information Systems Engineering (CAiSE'97), Barcelona, Spain, (1997).

....main requirements for a WFMS to support the evolution of workflow specifications: A. Support for the management of evolving workflow schemata: Different workflow schema versions have to be managed and different propagation strategies of workflow schema changes to their workflow instances (cf. [6, 5, 4]) have to be provided by a WFMS in order to flexibly support the migration from one business process to an improved one, to support alternative workflows for process variants, and to support ad hoc changes of a workflow. We distinguish . lazy propagation, i.e. a workflow schema is changed ....

....of the changed workflow definition. The selection of the workflow instances may be done manually by the process designer or automatically by the WFMS according to the instance execution states. The propagation has possibly to be delayed until the instance has reached the required state (cf. [4]) Furthermore, local adjustments to some workflow instances may additionally take place. local modifications and upward propagation: A special case of selective propagation is the change of the workflow definition for exactly one workflow instance in order to locally customize the workflow ....

[Article contains additional citation context not shown here]

Bichler, P.; Preuner, G.; Schrefl, M.: "Workflow Transparency ", in Proc. of 9 th Int. Conf. on Advanced Information Systems Engineering (CAiSE'97), Barcelona, Spain, 1997.

.... of the workflow (cf. ElNu96, KaRa96, Joe97a] 2) A posteriori flexibility: The evolution of workflow models in order to flexibly modify workflow specifications on the schema and instance level due to process (re)engineering activities and dynamically changing situations of a real process (cf. [CFF93, EKR95, CCPP96b, BPS97, ReDa98, JoHe98]) Workflow evolution management is an important part of our approach, but it is out of the scope of this paper (see [JoHe98] for a detailed overview) Distribution: Distributed workflow enactment (of centralized specified workflow models) is a key requirement for a scalable and fault tolerant ....

Bichler, P.; Preuner, G.; Schrefl, M.: "Workflow Transparency", in Proc. of 9 th Int. Conf. on Advanced Information Systems Engineering (CAiSE'97), Barcelona, Spain, 1997.

....allows to dynamically reorganize a workflow (i.e. replace one workflow by another one) without compromising the correct processing of business cases with respect to the underlying business process. Furthermore, various techniques such as dynamic migration and dynamic classification, introduced in [4], allow for migrating business cases dynamically from an old workflow to a new workflow and to place migrated business cases dynamically at appropriate advanced stages of the new workflow. 7 Webflow transparency denotes the quality of a web based information system to consider the specification ....

....effective. Following an object oriented approach, we use Object Behavior diagrams (OBDs) for the conceptual design of the business process schema. OBDs have been originally introduced for the design of object oriented databases in [11] Since OBDs have been extended also for modeling workflows [4], they are an ideal candidate for further evolving them for the design of web based information systems. It should be noted that any other object oriented design approach, like UML [18] may be used as well for modeling the business process schema. Since OBDs have already been introduced ....

[Article contains additional citation context not shown here]

P. Bichler, G. Preuner, and M. Schrefl. Workflow Transparency. In A. Oliv e and J.A. Pastor, editors, Proceedings of the 9th International Conference on Advanced Information Systems Engineering (CAiSE `97), Barcelona, Spain, volume 1250 of Lecture Notes in Computer Science, pages 423--436. Springer, June 1997.

....concludes this work. 2 Object Behavior Diagrams In this section, we briefly introduce Object Behavior Diagrams (OBD) which have been originally presented as a graphical notation for the object oriented design of databases [14] and have been later extended for the modeling of business processes [2]. We omit the description of object diagrams and concentrate on behavior diagrams with arc labels and their specialization. For more details, the reader is referred to [20, 21] 3 2.1 Labeled behavior diagrams Behavior diagrams are based on Petri nets and consist of activities, states, and ....

P. Bichler, G. Preuner, and M. Schrefl. Workflow Transparency. In A. Oliv'e and J.A. Pastor, editors, Proceedings of the 9th International Conference on Advanced Information Systems Engineering (CAiSE `97), Barcelona, Spain, volume 1250 of Lecture Notes in Computer Science, pages 423--436. Springer, June 1997.

....5 concludes our work. 2 Object Behavior Diagrams In this section, we briefly introduce Object Behavior Diagrams (OBD) which have been originally presented as a graphical notation for the object oriented design of databases [13] and have been later extended for the modeling of business processes [2]. We omit the description of object diagrams and concentrate on behavior diagrams with arc labels. We will present an overview of the basics of behavior diagrams in Section 2.1 and of specialization of behavior diagrams, which will be needed for integration, in Section 2.2. 2.1 Basics of Behavior ....

P. Bichler, G. Preuner, and M. Schrefl. Workflow Transparency. In A. Oliv'e and J.A. Pastor, editors, Proceedings of the 9th International Conference on Advanced Information Systems Engineering (CAiSE `97), Barcelona, Spain, volume 1250 of Lecture Notes in Computer Science, pages 423--436. Springer, June 1997.

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