ABBOTT, K. and SARIN, S., 1994, Experiences with Workflow Management: Issues for the Next Generation, in Proceedings of CSCW 94 (ACM Press, Chapel Hill, North Carolina) ANDERSON, R. J. 1994, Representations and Requirements: The Value of Ethnography in System Design, Human-computer interaction, 9,151-182.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....WWW interface is also provided though it is not described in this paper. These communication software packages are readily available to the public. New agents can be developed with the API of these communication systems. This system architecture is well suited to database based workflow systems [1], which have a centralized server for each workflow process instance. A BPT agent or a compatible entity can be easily embedded for servers of this type. If our agent communication library can be introduced to a workflow client server system, the planning and re planning functions of the BPT agent ....

....workflow client server system, the planning and re planning functions of the BPT agent can be embedded into the workflow management server. On the client side, Pochet may be used as a workflow client, or it may be integrated with existing workflow client. However, there are also some e mail based [1] workflow systems, which do not have a centralized server and are implemented using intelligent e mail. Since wehave developed this kind of workflow system [24] we have designed additional message types to let the BPT agent be available for systems of this type. The result of this design will be ....

Abbott, K. R. and Sarin, S. K. : Experiences with Workflow Management: Issues for the Next Generation, in Proceedings of Conference on Computer SupportedCooperative Work (CSCW) '94, ACM (Nov. 1994), pp. 113--120

....a workflow support system, while the latter executes it when a workflow is started by any authorized user. Despite their growing success, already existing Workflow Management Systems exhibit severe limitations in both their Workflow Model and Workflow Execution Module (see [Ellis Keddara 1993, Abbott Sarin 1994] 1. Exception handling mechanisms are basic features of Workflow Management Systems, but generally either they are too restrictive with respect to the needs of their users or they are too complicated both with respect to the performances of the Workflow Execution Module and the usability of the ....

Abbott, K. R., Sarin, S. K. Experiences with Workflow Management: Issues for The Next Generation. In Proceedings of the 5th Conference on CSCW. ACM, New York NY, 1994, (to appear).

....################################################ 4.6. 6 Related Work and Discussion Workflow systems are a way of routing information objects among users, and to specify automatic actions to be taken in that routing typically according to certain process models [Winograd86] Ellis94] Abbott94] Schael96] Normally, in order to model the workflow in organizations, there are two dominating paradigms: The Customer Supplier (CS) paradigm and the Input Process Output (IPO) paradigm. The CS paradigm focuses on coordination among people. The typical workflow systems in this paradigm are ....

Abbott, K., and Sarin, S. (1994). Experiences with workflow management: Issues for the next generation. In Proceedings of the Conference on CSCW'94, Chapel Hill, USA. ACM, pp. 113-120.

....community of CSCW researchers, the idea of business process simulation has not yet been introduced. To enhance workflow or business process models and their management systems, CSCW research community took some approaches as follow. # Some researches dealt with exception handling and deviations[1, 2, 7, 5]. The WorkWeb System was also one of such research activities of this approach. Simulation is our new tool to evaluate the dynamic attributes of workflow and human behavior. # Zhao and Stohr tried to optimize the process turnaround time[15] Their work is especially focused on claim processing. ....

K. R. Abbott and S. K. Sarin, "Experiences with Workflow Management: Issues for the Next Generation, " Proc. ACM

....in performing a specific task. A second type of usage area for collaboration technology in an IS is in the field of management. Workflow management systems (WfMS) are one particular type of CSCW technology used (often by the management) to coordinate the work activities of groups of employees (Abbott and Sarin 1994). There are also other CSCW systems for supporting decision making and strategic planning in an organization. These are referred to as Decision Support Systems (DSS) and are normally used by top and middle management. Electronic meeting systems are an example of such groupware (Nunamaker, Briggs ....

Abbott, K. R. and Sarin, S. K. (1994). Experiences with Workflow Management: Issues for the Next Generation, in Furuta and Neuwirth (1994), pp. 113--120.

.... workflows might be treated as a performance indicator) but we would argue that this marketbased approach leads to more flexibility and self responsibility of human PE (the lack of which has been identified as a major shortcoming of current approaches to workflow management and software processes [1, 16]) Particularly, through the bidding based task assignment, humans can decide much more freely which tasks they like to perform (in these cases, they should send cheap bids) and which they do not (for those they send no or expensive bids) In our future work, we will extend this work in various ....

K.R. Abbott, S.K. Sarin. Experiences with Workflow Management: Issues for the Next Generation. Proc. ACM 1994 CSCW, Chapel Hill, NC, October 1994.

....the opportunity to interact. A transition may also be performed in several steps or it may be reset. In this aspect, HieraStates is different from all other state diagram based approaches. The two approaches closest to the one presented here are the Regatta system [16] and the InConcert system [1]. In both systems process specifications are intended for guiding the user and for being developed and modified by the user. However, process schemes cannot be used to describe the behavior of arbitrary objects and they cannot be combined and specialized using multiple inheritance. Summarizing, ....

....of objects in the context of procedures, such as documents or tools. Due to its capabilities for exception handling, it supports the integration of non procedural tasks with procedural tasks, which is an important requirement for integrating workflow oriented systems with cooperation based systems [1]. A major design aspect of HieraStates is reuse by inheritance. The mechanism for behavior specification is carefully designed to gain as much as possible from single and multiple inheritance. It uses a fine grained inheritance scheme which allows to modify and add very small parts of behavior ....

Abbott, K. R., Sarin, S. K.: Experiences with Workflow Management: Issues for the Next Generation. In: Furuta, R., Neuwirth, C. (eds.): Proc. of Conference on Computer Supported Cooperative Work CSCW'94, New York: ACM Press, 1994, pp. 113--120

....to successfully support communication and collaboration within an organization. When faced with such a high probability that errors will occur, institutions normally focus on preventing errors by designing information systems that organize workflow into highly structured collaborative processes [1]. Such systems indicate to individuals working within the collaborative group when and what kinds of data to share with whom. This is especially true in situations where many different individuals must collaborate to achieve an overall goal while each performing smaller, individual tasks. Thus, ....

....detailed recording of process information serves as a valuable trace of actual execution steps. The importance of ensuring that workflow systems can handle large numbers of exceptional cases has been noted in prior studies [2, 13, 39] and has inspired work on developing highly flexible systems [1, 12, 16]. Some common exceptions can be predicted and mechanisms included in the workflow to cope with them. Adaptive workflow systems acknowledge that it is not possible to include within the original workflow model pre defined conditional branches for all possible contingencies. Instead, there also ....

Abbott, K.R. and Sarin, S.K. Experiences with workflow management: issues for the next generation. In Proceedings, CSCW'94, (Chapel Hill NC, 1994), ACM Press, 113-120.

....system. The experimental system used email for delivering memoranda to players, the World Wide Web for interactive documents, and email for informal inter player communication. This odd mix of technologies seems to be appropriate. The system failed to support the decision making environment [1] by providing easy access to historic information, and failed to provide a good decision making environment by providing an appropriate level of communication both with and between the players. The system treated all users in the same way and did not permit users to tailor the way in which the ....

Abbott, K.R. and Sarin, K.S. (1994): "Experiences with Workflow Management: Issues for the Next Generation" in Furuta, R., Neuwirth, C. (eds.): proceedings Conference on Computer Supported Cooperative Work, CSCW94, ACM Press, pp. 113-120.

.... data [4] divergence of tasks from the underlying workflow model [2] unexpected contingencies [13] and unmodeled changes in the environment [15] Efforts to evolve, expand, and optimize the workflow process may also be sources of change that must be accommodated by the workflow system [1][11] Traditional approaches have utilized inflexible control policies that make reactive control and graceful exception handling difficult, if not impossible, tasks. Our research in development of the Endeavors dynamic web based workflow system [9] 14] has suggested a number of key requirements ....

Abbott, K. and Sarin, S., "Experiences with Workflow Management: Issues for the Next Generation" Proceedings of the Conference on CSCW, Chapel Hill, NC, pp. 113-120, 1994.

....the Milano system we have been inspired by the claim of John Seely Brown and Paul Duguid (1994) that designers should pay attention to the fact that new systems should help the users to develop new border resources within their practices. 5. Related work and conclusion As it has been observed by Abbott and Sarin (1994) most existing workflow management systems embody inadequate process modeling frameworks, usable only as a means to communicate models and, sometimes, to simulate them. Quite recently some interesting proposals have appeared trying to overcome some of these limitations: Freeflow (Dourish et al. ....

Abbott, Kenneth R., and Sunil K. Sarin (1994): Experiences with Workflow Management: Issues for the Next Generation. In Proceedings of the Conference on the Computer-Supported Cooperative Work. New York, ACM Press, pp. 113-120.

.... systems originated from o#ce automation [6,7] but only after the inclusion of routing and tracking capabilities in image management systems, the importance of a routing capability for the management of such systems as well as for the management of business processes in general was recognised [1,14]. In the following years, some general purpose workflow management systems were developed, and in the late 80 s and early 90 s a large number of workflow management products became commercially available. However, the lack of standards for workflow systems made the interoperability between ....

K.R. Abbott and S.K. Sarin, Experiences with workflow management: issues for the next generation, Proceeding of the ACM 1994 Conference on Computer Supported Cooperative Work (CSCW'94) (1994) 113--120.

....Fig. 1. The time space classification of groupware. chronous groupware because it is technically more challenging, most immediate applications of groupware are the extension of company information systems to support collaborative processes in companies. Such systems are known as workflow systems [1]. They belong to the top right end of figure 1, and use email or more dedicated software technologies to support and enhance expenses handling in research laboratories, loans attribution in banks, or bug reporting and handling in software houses for instance. Workflows can be internal to a ....

K. R. Abbott and S. K. Sarin. Experiences with workflow management: issues for the next generation. In Proceedings of ACM CSCW'94. ACM Press, Oct. 1994.

....and systems. 6.1 Workflow Management Systems Workflow (management) systems provide the infrastructure to design, execute and manage business processes or activities in a network. The emphasis is on the management rather than on the automation of the tasks of which these activities are comprised [Abbott and Sarin, 1994]. Thus, central to these systems should be some form of the language action approach where the conversations between participants initiate and control the flow of activities. Computers can be applied in groupware in three different ways: to automate actions, support users in their intellectual ....

....the variety of behaviours occurring when performing work. A workflow system must therefore be able to adequately manage both procedural and non procedural interactions. Procedural interactions can be modelled using conversation based models, mainly grounded in the language action perspective [Abbott and Sarin, 1994]. Non procedural interactions typically occur in the case of exceptions to structured activities. Many of these exceptions cannot be formalized, but the processes in which they are to be handled, should be. Note that not all procedural conversations have to be modelled to obtain proper system ....

[Article contains additional citation context not shown here]

Abbott, K. and Sarin, S. (1994). Experiences with workflow management: Issues for the next generation. In

....surface representations, or the simple perceptible graphical patterns in application displays. Our approach is similar in that we do not rely on semantics in the application, but different in that we move those semantics closer to the document itself rather than its representation. Abbott and Sarin (1994) suggested that the next generation of workflow tools would be simply another invisible capability that permeates all (or most) applications. By decoupling collaboration functionality from the application, and making it a middleware component, our approach has brought us closer to this model, ....

Abbott, K. and Sarin, S. (1994). Experiences with Workflow Management: Issues for the Next Generation. Proc. ACM Conf. Computer-Supported Cooperative Work CSCW'94 (Chapel Hill, NC). New York: ACM.

....encompass groups of people and machines engaged in collaborative tasks can certainly be relevant. Indeed, the recent CSCW literature contains studies of cooperative, computer supported work that can easily be interpreted in terms of what we may call social or organizational usability. For example, Abbott and Sarin (1994) report a case study of a workflow management system in use where usability issues and challenges are seen to include, e.g. support for interworker coordination and organizational policy management. If usability is seen as social, what are the implications for the practice of achieving more ....

Abbott, K., and Sarin, S. (1994). Experiences with workflow management: Issues for the next generation. In Proc. Conf. Computer Supported Cooperative Work (CSCW'94), pp. 113-120. New York: ACM Press.

....the entire billing and payment process by a barter for some product or service. Many workflow products do in fact support deviations from the process model. For example, InConcert allows a workcase to be modified by allowing tasks or dependencies to be added removed, roles reassigned, etc. [1]. However, we believe that most proposals do not find a middle ground between requiring exceptional cases to be anticipated, and allowing ad hoc actions that are either too specialized (e.g. restricted to forms handling [24] or too powerful (e.g. arbitrary editing of the schema) Furthermore, ....

....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] ....

K.R. Abbott, S.K. Sarin. "Experiences with Workflow Management: Issues for the Next Generation", CSCW'94, Chapel Hill, NC, 1994.

.... Workflow systems, as part of business process reengineering approaches, can empower managers to free themselves from existing constraints (Davenport Stoddard 1994) We should not be surprised that management rarely needs to be convinced [ of the need to adopt workflow technology (Abbott and Sarin 1994) , while those whose work will be managed using this technology are still reluctant. The analytical view of decision making processes alongside with the belief that system designers can predict information needs is serious, inasmuch as it reduces the autonomy and flexibility in situations that are ....

....it builds on an abstract and generic understanding of work, rather than a procedural, specific description of it. Criticism has been raised toward the speech act theory from a linguistic (Jakobson 1967) as well as an application perspective (Dietz Widdershoven 1991; Whitaker 1992; Suchman 1994) Abbott Sarin (1994), on the other hand, describe a system which affords the necessary flexibility to redefine the work processes as they are being enacted: reassigning work, overriding the process of approval, and returning incomplete work. This is, as they admit, only possible to a limited extent within the ....

Abbott, K. R. & Sarin, K. S. (1994). Experiences with Workflow Management: Issues for the Next Generation. In Proceedings of the ACM CSCW'94 Conference on ComputerSupported Cooperative Work , Chapel Hill, North Carolina, USA.

....part of the workflow she is involved in. E 295 2.3 Process Composition E 125 When classifying a NIS according to its purpose, it can be considered an ad hoc E 383 workflow management system. A workflow management system allows for the E 385 design, execution and management of work processes [4]. Ad hoc means that such a E 393 system supports creative knowledge activities. These activities are notoriously E 350 difficult to model; the workflow support provided can therefore at best provide some E 376 sort of control to ensure that tasks, responsibilities, etc. are delivered [5] ....

Abbott, K., Sarin, S. Experiences with Workflow Management: Issues for the Next<E-380> Generation. In Furuta, R., Neuwirth, C., editors, Proceedings of the ACM Conference<E-355> on Computer Supported Cooperative Work, Chapel Hill, October 22-26, 1994. ACM,<E-374> pp.113-120.<E-70>

....the collaborators. It is in this sense more similar to that of Reeves and Shipman (1992) when they aim to gradually populate an information space. It might be of interest to compare the properties of the suggested model to the design principles for future workflow management systems set forward by Abbott and Sarin (1994). As an alternative to the vision of workflow as simply another invisible capability that permeates all applications , we have outlined an architectural model that offers integrated multimedia support for the apparently social activities in the workplace as well as the tasks that are the purpose ....

Abbott, K. R. & Sarin, K. S. (1994). Experiences with Workflow Management: Issues for the Next Generation. In Proceedings of the ACM CSCW'94 Conference on ComputerSupported Cooperative Work, (pp. 113-120).

....the workflow management paradigm, is not always the route to follow. It does not acknowledge that the use of information requires knowledge (meta information) on the effectiveness and efficiency of using that information. We feel that a combined approach is necessary (in line with conclusions from [Abb94] and [She96] Specifically in cases where the processes are less structured, may be even ad hoc, and where the quality of the information is an issue, we argue that an adequate support of the knowledge worker is necessary. They should have the knowledge to assess the combination of procedure and ....

K. Abbott, S. Sarin. Experiences with Workflow Management: Issues for the Next Generation. ACM Conference on ComputerSupported Cooperative Work, 113-120, 1994.

....suggested by the workflow management paradigm, is not always the route to follow. It does not acknowledge that the use of local information requires knowledge on the effectiveness and efficiency of using that information. We feel that a combined approach is necessary (in line with conclusions from Abbott and Sarin (1994) and Seth et al. 1996) combining proven techniques and tools. Specifically in cases where the processes are less structured, may be even ad hoc, and where the quality of the information is an issue, we argue that an adequate support of the local worker is necessary. They should have the ....

Abbott, K., Sarin, S., "Experiences with Workflow Management: Issues for the Next Generation", ACM Conf. on Computer-Supported Cooperative Work, 1994, p. 113-120.

....and Wainer (1995) define an exception to be any departure of a work case from its prescribed flow. Hence, exceptions occur only on the activity instance level. There are also exceptions which can be expected in advance. Then they may be added to the execution scheme as a possible path. However, Abbott and Sarin (1994) note that this tends to make the scheme unwieldy and hard to understand. 4.1 Expected Exceptions HieraStates supports modeling expected exceptions with the help of transitions which may be invoked in several states. In the example the additional transition set manually may be used to handle ....

....groups. However, it prohibits privacy issues for parts of a task. These are important for tasks involving several organizations. In HieraStates a task object may be shared or private, using asynchronous communication for accessing other task objects in the latter case. The system InConcert (Abbott and Sarin 1994) is similar, however, it is more specialized to document processing. Its underlying model (Sarin, Abbott, and McCarthy 1991) focuses mainly on tasks which manipulate linked documents. No specific means for exception handling other than manual subtasks are supported. An important theoretical base ....

Abbott, K. R. and S. K. Sarin (1994). Experiences with Workflow Management: Issues for the Next Generation. In R. Furuta and C. Neuwirth (Eds.), Proc. of the Conf. on Computer Supported Cooperative Work CSCW'94, New York, pp. 113--120. ACM Press.

....task is associated with resources to support the work of the person. Such resources mainly are documents and applications. By integrating teleconferencing systems into the workflow, a teleconferencing system can be used as a special resource for a task scheduled by a workflow management system [4]. The common workflow paradigm being limited to one person one task one application [5] is widened. An activity can incorporate as well more than one person as multiple applications. An integrated telecooperation framework for both approaches has been developed [6] This framework closely ....

Abbott K.R.; Sarin, S.K.: Experiences with Workflow Management: Issues for the Next Generation, Conference on Computer-supported Cooperative Work (CSCW), ACM Press, 1994.

....means. The Network Information System Because of our process focus, we are especially interested in one particular kind of groupware, namely workflow management systems. These are systems that allow for the design, execution and management of business processes and activities in a network (Abbott and Sarin, 1994). The kind of system that is most appropriate in the research network context is that of the ad hoc workflow system. Most workflow systems are transactionfocused, which means that they create structures to implement and enforce frequently recurring processes. Ad hoc applications, on the other ....

Abbott, K., Sarin, S. (1994) Experiences with Workflow Management: Issues for the Next Generation. In: Furuta, R. and Neuwirth, C., eds., Proceedings of the 1994 Conference on Computer Supported Cooperative Work, Chapel Hill, October 22-26, ACM, 113-120.

....DESIGN GOALS We begin by describing the primary and secondary design goals that pertain to the discussion in this paper. Primary Design Goals Support for a Range of Specifications. It is generally accepted that it is impossible to specify, in advance, the full details of how a task will proceed [20, 17, 1]. Sometimes participants have a lot of knowledge about what steps are necessary to complete a task, how the steps are related, and what must be accomplished in each step. Other times, very little is known about how to proceed and the flow is essentially designed as the task progresses. Therefore, ....

....a surrogate s rule can be set to this one , and the current template is essentially copied into the obligation. The template is only changed if the rule is changed. This type of continual binding also accomplishes delayed binding where the template to use is selected as late as possible [1, 22]. A surrogate s rule is first derefer 4 The section on Surrogation describes cases where obligations do not upgrade automatically. DESIGN ENGINEER: Modify Design C PROJECT MANAGER: Schedule and Assign Tasks C QA ENGINEER: Modify Test Plans C ALL: Review Design C Stage Sub Obligation QA ....

[Article contains additional citation context not shown here]

Kenneth R. Abbott and Sunil K. Sarin. Experiences with workflow management: Issues for the next generation. In Proceedings ACM Conference on Computer-Supported Cooperative Work (CSCW '94), pages 113--120, Chapel Hill, North Carolina, Oct. 22 -- 26, 1994.

....Management System, then a task oriented approach seems to be more suitable for the Re engineering Process. Nevertheless, it seems that business policy oriented approaches are becoming more and more important and it is believed that they will have an impact to future Workflow Management Systems (Abbott Sarin, 1994). Our future work focusses on the combination of task oriented and business policy oriented approaches. More specifically we are thinking of applying the business policy oriented approach during Information Acquisition and generate afterwards a task oriented model. We think that the use of a ....

Abbott, K. R., & Sarin, S. K. (1994). Experiences with Workflow Management: Issues for the Next Generation. Proceedings of the Conference of Computer Supported Cooperative Work (CSCW'94). ACM Press, 113-120.

....to global goals (in addition to the structured directives included in the process definition) 6 Integrated model We suggest to use the group communication processes as an intermediate level between the level of the global control processes and the level of local data management. We agree with Abbott and Sarin (1994) that the conversation based models are appropriate for the less formal details of communication, but overkill for the more structured processes: it is therefore necessary for users to be able to switch back and forth gracefully between these two modes of interaction . Therefore, the integrated ....

Experiences with Workflow Management: Issues for the Next Generation, Abbott and Sarin, Proc. ACM Conf. on Computer-Supported Cooperative Work, 1994, pages 113-120.

....be embedded into the workflow management domain. In recent years there has been considerable work and publication related to workflow systems, models and studies. Also the growing interest in business process reengineering [ Davenport, 1993 ] led to the development of commercial workflow systems [ Abbott and Sarin, 1994 ] in order to support and improve business processes. McCarthy and Bluestein [ McCarthy and Bluestein, 1991 ] define workflow management as a proactive system which manages the flow of work among participants according to a defined procedure consisting of a number of tasks. It coordinates user ....

K. R. Abbott and S. K. Sarin. Experiences with workflow management: Issues for the next generation. In R. Furuta and C. Neuwirth, editors, Proc. 5th Int. Conf. on Computer-Supported Cooperative Work, pp. 113--120, Chapel Hill, NC, October 1994. New York: SIGCHI/SIGOIS ACM.

....these plans in actual work. Introduction The issue of workflow systems has been addressed by several authors as ways of routing information objects among users, and to specify automatic actions to be taken in that routing typically according to certain process models (Medina Mora et al. 1992; Abbott and Sarin, 1994; Sch l, 1996) A process model is typically understood as a computerised (i.e. formal) representation of work procedures that controls the order in which a sequence of tasks are to be performed. These workflow systems for the coordination of activities in organisations have drawn much attention, ....

....made and embedded in workflow systems in the first place. Often e.g. in the area of Business Process Reengineering workflow systems are viewed as the enabling technologies for turning the modern firm into a process organisation with greater opportunities for efficiency and cost reduction (see e.g. Abbott and Sarin, 1994). Thus, workflow systems are conceived as organisational infrastructure used and designed for meeting organisational goals (e.g. customer satisfaction) Sch l, 1996) When viewed from this overall organisational perspective, workflow systems are often used to keep track of the work according to ....

Abbott, K., and Sarin, S. (1994): "Experiences with workflow management: Issues for the next generation", In Proceedings of the Conference on CSCW, Chapel Hill, USA. ACM, p. 113-120.

....a general activity support system (Schlichter and Teege, 1994) In this section I describe how to achieve this integration in OOActSM. If a workflow is mapped into OOActSM, it becomes an activity with additional predetermined information about its structure and execution. Sarin et al. 1991) and Abbott and Sarin (1994) list several requirements for workflow support systems. I will explain how these requirements are satisfied in the framework of object oriented activity support. The requirements of using an explicit representation of the collaborative process, of providing a task context, and of working in a ....

Abbott, K. R. and Sarin, S. K.: 1994, Experiences with Workflow Management: Issues for the Next Generation, in R. Furuta and C. Neuwirth (eds), Proc. of the Conf. on Computer Supported Cooperative Work CSCW'94, ACM Press, New York, pp. 113--120.

....Systems must offer ways of assigning people authority levels and of enforcing that no one may access unauthorized items. The seeming simplicity of authorization might offer some traps, for instance when there is an inconsistency between authority levels for task execution and for document access [AS94] The agent may have authority enough to execute the task, but not to access the necessary documents. A difference between the responsible actor and the executor surfaces here [Joo94] Tool integration Activities work is best conducted with the aid of tools. These tools may be unstructured, like ....

....the main line. This goal can be reached by better integration of exception handling. We would like to state clearly that our intention is not of creating a model that tries to predict every possible exception beforehand. Such a goal would be destined to failure, as some authors forewarn ( EW94, AS94] for instance) Our objective is to enhance the model so that the handling of routine exceptions could be incorporated at specification level, and supported at enactment level. We discuss next how we intend to reach the fore mentioned goals, through better exception handling and component ....

[Article contains additional citation context not shown here]

Abbot,K.R., Sarin, S.K. "Experiences with Workflow management: Issues for the Next Generation, " in CSCW'94, ACM, 1994.

....steps is swapped) According to the survey in [21] many workflow products on the market do in fact support deviations from the process model during an enactment. For example, InConcert allows a workcase to be modified by allowing tasks or dependencies to be added removed, roles reassigned, etc. [1]. However, we believe that in most cases the mechanisms considered so far suffer from a number of failings, including being either too specific ad hoc (e.g. restricted to forms handling [24] or too powerful (e.g. allowing arbitrary editing of the schema) and giving insufficient consideration ....

K.R. Abbott, S.K. Sarin, "Experiences with Workflow Management: Issues for the Next Generation", in the Proceedings of ACM Conference on Computer Supported Collaborative Work (CSCW94), Chapel Hill, NC, 1994.

....management paradigm, is not always the route to follow. It does not acknowledge that the use of local information requires knowledge (metainformation) on the effectiveness and efficiency of using that information. 6 We feel that a combined approach is necessary (in line with conclusions from [AS] and [Sea] combining proven techniques and tools. Specifically in cases where the processes are less structured, may be even ad hoc, and where the quality of the information is an issue, we argue that an adequate support of the local worker is necessary. They should have the knowledge to assess ....

Kenneth Abbott, Sunil Sarin, "Experiences with Workflow Management: Issues for the Next Generation", ACM Conf. on Computer-Supported Cooperative Work, 1994, p. 113-120.

.... can be classified into production, collaborative, administrative, and ad hoc workflow [23] Production workflow applications are characterized by transactional features and are targeted by high end workflow management systems like FileNet Workflo [6] IBM FlowMark [10] Staffware, XSoft InConcert [22, 1] and many others. Collaborative, administrative and ad hoc workflow applications instead require flexible workflow management environments and depend on built in database and communication infrastructure. This type of integrated workflow management functionality is best provided by groupware ....

K. Abbott and S. Sarin. Experiences with workflow management: Issues for the next generation. In Proc. of the Conf. on Computer-SupportedCooperative Work, CSCW, pages 113-- 119. ACM Press, 1994.

No context found.

ABBOTT, K. and SARIN, S., 1994, Experiences with Workflow Management: Issues for the Next Generation, in Proceedings of CSCW 94 (ACM Press, Chapel Hill, North Carolina) ANDERSON, R. J. 1994, Representations and Requirements: The Value of Ethnography in System Design, Human-computer interaction, 9,151-182.

No context found.

Abbott KR, Sarin SK (1994) Experiences with workflow management: issues for the next generation. In: Proceedings of the 1994 ACM conference on computer supported cooperative work, Chapel Hill, NC. ACM Press, New York, pp 113--120

No context found.

Abbott, K. R. and Sarin, S. K. Experiences with workflow management: Issues for the next generation. In CSCW'94, ACM, Chapel Hill, NC, 1994.

No context found.

K.R. Abbott, S.K. Sarin, "Experiences with Workflow Management: Issues for the Next Generation", in the Proceedings of ACM Conference on Computer Supported Collaborative Work (CSCW94), Chapel Hill, NC, 1994.

No context found.

Abbott KR, Sarin SK. Experiences with workflow management: issues for the next generation. In: Furuta R, Neuwirth C (eds). Proceedings of the conference on computer supported cooperative work, Chapel Hill, NC, 22--26 October 1994. ACM Press, New York, 1994, pp 113--120

No context found.

Abbott, K. R., and S. K. Sarin: "Experiences with workflow management: issues for the next generation," in T. Malone (ed.) CSCW '94. The Conf. on ComputerSupported Cooperative Work, Chapel Hill, North Carolina, October 24-26, 1994, ACM Press, New York, 1994, pp. 113-120.

No context found.

K. R. Abbott and S. K. Sarin, "Experiences with workflow management: issues for the next generation," presented at Conference on Computer Supported Cooperative Work, Chapel Hill United States, 1994.

No context found.

Abbott, K. R. & Sarin, K. S. (1994). Experiences with Workflow Management: Issues for the Next Generation. In Proceedings of the ACM CSCW'94 Conference on ComputerSupported Cooperative Work, (pp. 113-120).

No context found.

Abbott, K. and Sarin, S. (1994): "Experiences with Workflow Management: Issues for the Next Generation" Proceedings of the Conference on CSCW, Chapel Hill, NC, pp. 113-120, 1994.

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