McCarthy, D. & Sarin, S. (1993) Workflow and transactions in InConcert. Bulletin of the Technical Committee on Data Engineering. IEEE Computer Society. 16(2).  Home/Search   Document Not in Database   Summary   Related Articles   Check

....methodologies model the tasks involved in a process and their dependencies. The majority of the business process modelling methods described in the previous section may well fall within this category. It should be noted that the activity based approach is consistent with object orientation (e.g. McCarthy Sarin, 1993; and the objectoriented workflow system Oz in Ben Shaul Kaiser 1995) Similarly to the work carried out by the Object Management Group and the BOMSIG mentioned in the previous paragraphs, one should mention the work of the Workflow Management Coalition (Hollinsworth, 1995) towards the ....

McCarthy, D. & Sarin, S. (1993) Workflow and transactions in InConcert. Bulletin of the Technical Committee on Data Engineering. IEEE Computer Society. 16(2).

....is a goal, then there may be multiple procedures which can be invoked to attain the goal. The extended ICN model presented in [Ellis 94] recognizes that an organization comprises resources and goals. The model incorporates the notion of unstructured activity. In the INCONCERT workflow model [McCarthy 93] a job represents a collaborative activity. A job consists of tasks, each of which is a unit of work that can be performed by one person. Tasks can be decomposed into subtasks, to obtain a hierarchical breakdown structure. Tasks at the same level may have ordering dependencies defined among ....

: McCarthy D.R, Sarin S.K., "Workflow and transactions in InConcert", Bulletin of Technical Committe on Data Engineering, 1993, Vol. 16, N° 2, IEEE, june, Special Issue on Workflow and Extended Transactions Systems. p. 53-56.

....in the representation and the building of a complex procedure by successive refinements. Alternative, parallelism and loop structures are used to describe procedures. The extended ICN model presented in [6] incorporates the notions of goal and unstructured activity. In the Inconcert workflow model [13] a job represents a collaborative activity. A job consists of tasks, each of which is a unit of work that can be performed by one person. Tasks can be decomposed into sub tasks, to obtain a hierarchical breakdown structure. Tasks at the same level may have ordering dependencies defined among ....

....may be associated with a group of actors. Also, one actor may play many roles within an organisation. An actor is a person, program, or an entity that can fulfil roles to execute, to be responsible for, or to be associated in some way with activities and procedures. In the Inconcert workflow model [13], a role is a logical placeholder for the user (person or program) that will perform a task. In VPL [25] a role is a container for list of names of people or groups. A role is not a quality of individual, but rather a relationship between a person (group) and a particular shared collaboration ....

[Article contains additional citation context not shown here]

McCARTHY, D.R., SARIN, S.K., Workflow and transactions in InConcert, in: Bulletin of Technical Committee on Data Eng., 16(2) IEEE, Special Issue on Workflow and Extended Transactions Systems (1993).

....role. time Task Data Tools Roles Actors and or Role 1 Role 2 Role 3 g Figure 2 Procedure representation We have considered seven models dealing with task workflow agent role representations, respectively OSSAD (Dumas, 1990) Dumas et al. 1990) ICN (Ellis, 1979) Ellis, 1994) InConcert (McCarthy, 1993), VPL (Swenson, 1993) I (Yu, 1994) Enterprise Modelling (Bubenko 1994) Loucopoulos 1995) and ITHACA (Ang, 1993) This study showed a convergence on a set of concepts such as goal, procedure, task, role, actor, resource, decomposition of tasks, etc. However, an appropriate model for a large ....

McCarthy D.R, Sarin S.K. (1993): "Workflow and transactions in InConcert", Bulletin of Technical Committe on Data Engineering, Vol. 16, N° 2, IEEE, june, Special Issue on Workflow and Extended Transactions Systems. p. 53-56.

....by the direct encoding into the program. However, in a complicated business application which may contain thousands of tasks, the portability and maintainability considerations render the direct encoding approach unattractive. This necessitates separate specification of these dependencies [1,3,17]. The early workflow models assumed that all the structural components could be specified in advance. While such a static view still applies to some (usually small) workflows which are static in nature, it is no longer appropriate for the others. In these applications, either the tasks may not be ....

D. McCarthy and S. Sarin, "Workflow and transactions in InConcert", Bulletin of the Technical Committee on Data Engineering, IEEE Computer Soci

.... [1] The connection to the TriGS f low engine is based on the GemBuilder for Java interface [12] 5 Related Work For the last six years, a couple of systems has proposed the use of ECA rules as a mechanism for the realization of different coordination aspects of WFMS [2] 4] 5] 8] 13] [24], 25] The first system dates back to the early 90ies, when research on AOODBS has been intensified. All these Implementation Environment Roles Application Areas for ECA Rules Activity Ordering Agent Selection Worklist Management Long Running Activities RDBS HiPAC 3 ActMan RDBS 3 ....

....data preparation, initiation of the activity, and post analysis routines of the activity. Concerning batch activities , i.e. activities executed by software agents, similar to TriGS f low , their start is automatically enforced as soon as the activity is inserted into the worklist. InConcert [24] allows to attach EA rules to significant events that are recorded within an audit log. Examples for such events are state changes of activities such as ready or overdue , document check out check in, as well as user defined events. These events may trigger the start of a new workflow, ....

[Article contains additional citation context not shown here]

D.R. McCarthy, S.K. Sarin, "Workflow and Transactions in InConcert", in IEEE Bulletin of the Technical Committee on Data Engineering, vol. 16(2), June 1993.

.... 6 Related Work We first discuss work in the literature related to workflow activity models [10] These include active database and rule based approaches [7, 8] multidatabase and relaxed extended transaction model based approaches [14, 1, 15] and office and process automation based approaches [17, 23, 24]. Somewhat less relevant are the many proposals for multi level and nested transaction models [30] A perspective on combining workflow and transaction management was given in [4] Unlike many of these models, we do not view the entire application or the activities in transactional terms, since ....

D. McCarthy and S. Sarin. Workflow and Transaction in InConcert. In [10].

.... in the literature dealing with workflows activities [15] can be described as those based on multidatabase and relaxed extended transactions ( 19] 1] 37] 18] active database and rule based approaches ( 12] 13] combinations of the above two [20] and office and process automation ( 24] [30], 31] The ACTA model [10] and the DOM model [20] provide frameworks for system specification that capture several of the above approaches. For instance, these models support the specification of complex intra and inter transaction state dependencies, and correctness dependencies such as ....

D. McCarthy and S. Sarin. Workflow and Transaction in InConcert. In [15].

....activities [Waechter and Reuter, 1992] Most of these 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 ....

McCarthy, D. and Sarin, S. (1993). Workflow and Transactions in InConcert. Bulletin of the Technical Committee on Data Engineering, 16(2). IEEE Computer Society.

.... Approaches in the literature dealing with workflows activities [14] can be described as those based on multidatabase and relaxed extended transactions [18, 17, 1, 35] active database and rule based approaches [11, 12] combinations of the above two [19] and office and process automation [22, 28, 29]. The ACTA model [9] and the model discussed in [26] provide formal frameworks for system specification that capture several of the above approaches. For instance, these models support the specification of complex intra and inter transaction state dependencies, and correctness dependencies such ....

D. McCarthy and S. Sarin. Workflow and Transaction in InConcert. In [14].

....sequencing have explanations similar to that of the New Service Provisioning workflow. A number of organizations have produced workflow management systems (WFMSs) that provide the ability to specify, execute, report on, and dynamically control workflows involving multiple humans and HAD systems [31]. The capabilities commercial WFMSs currently offer are discussed in Section 4 and Appendix A. 2.2. Characterizing workflows As yet, there is no commonly agreed way to characterize or categorize workflows or WFMSs. Furthermore, most workflow characterizations neglect highly automated workflows ....

....and that tasks may nest arbitrarily deeply. Unlike communicationbased methodologies, activity based methodologies do not capture process objectives such as customer satisfaction. Many commercial WFMS provide activity based workflow models. For example, in the workflow model supported by InConcert [31], workflows (referred to as jobs) consist of tasks. Each task may be comprised from subtasks. Each task has dependencies on other tasks at the same level and has an assigned role which is the proxy for a human or a program that performs the task. GTE s RAPID methodology [11] is also ....

[Article contains additional citation context not shown here]

D. McCarthy and S. Sarin, "Workflow and Transactions in InConcert," Bulletin of the Technical Committee on Data Engineering, IEEE Computer Society, Vol. 16, No.2, June, 1993.

No context found.

McCarthy, D.R. et Sarin, S.K. "Workflow and Transaction in InConcert", Bulletin of the Technical Committee on Data Engineering, Vol. 16 N2 - IEEE, June. Special Issue on Workflow Extended Transaction Systems, 1993.

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