A.P. Sheth, On Multi-system Applications and Transactional Workflows, collection of papers from Bellcore, 1994.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....the paper contains a high level overview of our research in six specific areas that are not product specific. The list of these areas is not, by any means, exhaustive. There are still many issues that remain open. For reasons of space, the paper does not discuss workflow related concepts [11, 26, 12, 24, 27] or the particular details of the architecture and functioning of FlowMark [19, 18, 14, 15] The interested reader can find more information in the references. 2 Large Scale Workflow Systems Before discussing workflow management, it is necessary to put in perspective the applications addressed ....

A.P. Sheth, On Multi-system Applications and Transactional Workflows, collection of papers from Bellcore, 1994.

....In this model, each execution of a process is associated with an Information Carrier, which is an object that contains all the necessary information for the execution as well as propagation of the object among the relevant processing nodes. Transaction based applications [TAC 93] MS93] She94] like the model based on extended nested sagas [GMGK 90] for coordinating multi transaction activities, or the ConTract model, which provides reliable control flow between transactional activities [WR92] In [DHL90] and [DHL91] a specification language and a transactional model for ....

A.P. Sheth. On Multi-system Applications and Transactional Workflows, Bellcore's projects PROMP and METEOR, 1994. Collection of papers and reports from Bellcore.

....and determining when a process has terminated. Though these concepts have been around for a number of years, the technology required to implement suitable systems has however been available only recently. Currently, there is a considerable amount of attention devoted to this area [GHS95, Hsu95, She94] A workflow model is a description of a business process. For this purpose, the Workflow Management Coalition has proposed the following reference model [WfMC94] A business process is represented by a schema that includes the process name, version number, start and termination conditions and ....

A.P. Sheth. On Multi-system Applications and Transactional Workflows, 1994. Collection of papers from Bellcore.

....management. In this model, each execution of a process is associated with an Information Carrier, which is an object that contains all the necessary information for the execution as well as propagation of the object among the relevant processing nodes. Transaction based applications [25] 18] [24], like the model based on extended nested sagas [8] for coordinating multi transaction activities, or the ConTract model, which provides reliable control flow between transactional activities [27] In [6] and [7] a specification language and a transactional model for organizing long running ....

A. Sheth. On Multi-system Applications and Transactional Workflows, Bellcore's projects PROMP and METEOR, 1994. Collection of papers and reports from Bellcore.

....is not allowed, and the program execution client must be able to deal with all the information about activities, containers and navigation, effectively performing the same task as the server and the database. 4 Related Work There is a considerable amount of reserach in the area of workflow [She94, Hsu93, GHM 93, TAC 93, WR92, DHL91] however, both in research and in commercial systems, the issue of disconnected client support has not been fully addressed. Workflow systems like FlowMark, InConcert [MS93] or WorkFlo [FG87] assume users to be permanently connected to a more or less ....

A. Sheth. On Multi-system Applications and Transactional Workflows, 1994. Collection of papers from Bellcore.

....early efforts were limited in their scope and did not address business processes in their full generality. More recently, several high level designs have been proposed for modeling and managing business processes [Tomlison et al. 1993] McCarthy and Sarin, 1993] Medina Mora et al. 1993] [Sheth, 1994], but most of them are centralized and fail to address issues such as high availability, failure resilience or scalability. Moreover, they tend to be transactional in nature and too centered around databases, which contrast with the reference model created by software vendors [Hollinsworth, 1994] ....

Sheth, A. (1994). On Multi-system Applications and Transactional Workflows, Bellcore's projects PROMP and METEOR. Collection of papers and reports from Bellcore.

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