November 2018
·
66 Reads
This page lists works of an author who doesn't have a ResearchGate profile or hasn't added the works to their profile yet. It is automatically generated from public (personal) data to further our legitimate goal of comprehensive and accurate scientific recordkeeping. If you are this author and want this page removed, please let us know.
November 2018
·
66 Reads
November 2000
·
16 Reads
Computer Supported Cooperative Work (CSCW)
The unpredictability of business processes requires that workflowsystems support exception handling with the ability to dynamicallyadapt to the changing environment. Traditional approaches to handlingthis problem have fallen short, providing little support for change,particularly once the process has begun execution. Further,exceptions vary widely in their character and significance,challenging the application of any single approach to handling them.We briefly discuss the classification of exceptions, highlightingdiffering impacts on the workflow model. Based on this discussion, wesuggest principal goals to address in the development of adaptiveworkflow support, including strategies for avoiding exceptions,detecting them when they occur, and handling them at various levels ofimpact. We then identify a number of specific approaches to supportingthese goals within the design of a workflow system infrastructure.Finally, we describe the implementation of many of these approaches inthe Endeavors workflow support system.
November 2000
·
296 Reads
·
196 Citations
Computer Supported Cooperative Work (CSCW)
The unpredictability of business processes requires that workflow systems support exception handling with the ability to dynamically adapt to the changing environment. Traditional approaches to handling this problem have fallen short, providing little support for change, particularly once the process has begun execution. Further, exceptions vary widely in their character and significance, challenging the application of any single approach to handling them. We briefly discuss the classification of exceptions, highlighting differing impacts on the workflow model. Based on this discussion we suggest principal goals to address in the development of adaptive workflow support, including strategies for avoiding exceptions, detecting them when they occur, and handling them at various levels of impact. We then identify a number of specific approaches to supporting these goals within the design of a workflow system infrastructure. Finally, we describe the implementation of many of these approaches in the Endeavors workflow support system.
April 1999
·
82 Reads
·
3 Citations
Frequently process workflows are distributed collections of activities that involve groups of individuals at disparate locations. To coordinate these tasks, a process support system should provide for distributed process execution and integration with tools across networks. We describe the use of the Hypertext Transfer Protocol (HTTP), an increasingly ubiquitous technology, to provide a coordination mechanism for distributed process execution and tool integration. To make the distributed workflow and benefits of HTTP more illustrative, the demonstration will focus on a software pre-requirements process designed for the Applications Development Group of Pacific Bell, a major telecommunications company. This document routing and approval process was developed to support a major requirements engineering activity, where participants interact with applets in a web-browser to submit a document for approval. Keywords open, distributed process technology, architecture INTRODUCTION Process...
October 1998
·
10 Reads
·
13 Citations
Processes that perform and distribute tasks over the Internet are known as "Web-Driven Process Workflow." The UCI Travel Expense Process (TEP) and the Pacific Bell Applications Development Group (ADG) are two webdriven process workflows that exemplify process reuse by leveraging Endeavors, a research workflow process support system at the University of California at Irvine. This paper describes the TEP and ADG projects, and the enabling components and architecture that allow reuse and extension of process components with off-the-shelf tools and webbased resources over the Internet. Keywords Workflow, process, Internet, components, reuse, architecture INTRODUCTION The UCI Travel Expense Process (TEP) and the Pacific Bell Applications Development Group (ADG) [3] are two examples of web-driven process workflows. Both systems involve common workflow activities such as review and approval processes, and both provide distributed process and information across groups and individuals. To b...
October 1998
·
73 Reads
·
13 Citations
Frequently process workflows are distributed collections of activities that involve groups of individuals at disparate locations. To coordinate these tasks, a process support system should provide for distributed process execution and integration with tools across networks. We describe the use of the Hypertext Transfer Protocol (HTTP), an increasingly ubiquitous technology, to provide a coordination mechanism for distributed process execution and tool integration. Building on the Endeavors process support system, we discuss extensions to an HTTP server to provide support for communication and coordination between system components as well as integration with external tools. We also examine several progressively more distributed and flexible approaches to distribution using HTTP and Endeavors. Keywords Software process and process improvement, hypermedia, project management, computer supported cooperative work (CSCW) and software engineering, distributed and parallel systems, environ...
October 1998
·
90 Reads
·
13 Citations
Proceedings - International Conference on Software Engineering
As software projects evolve, possibly differing in size, complexity, scope, and purpose, the development processes that support the project must evolve to reflect these changes. The Endeavors system is an open, distributed process modeling and execution infrastructure that addresses communication, coordination, and control issues. Endeavors' solution architecture applies five key design strategies: (1) maintaining multiple object model layers, (2) implementing the architecture as a set of highly componentized, lightweight, transportable, concurrent elements, (3) providing customization capabilities for each layer of the object model, (4) using a reflexive object model to support dynamic change, and (5) allowing dynamic loading and changing of objects. Keywords open, distributed process technology, architecture INTRODUCTION Effective software evolution demands that all stakeholders are able to participate in a system's evolution. This requires involvement in evolutionary processes, ...
January 1997
·
9 Reads
·
1 Citation
221 Reads
·
21 Citations
Peer computing is the next stage in the evolution of the Internet and promises to be a versatile underpinning for an enormous variety of novel, entertaining, and useful applications. However, peer-to-peer applications pose many difficult challenges for developers. We examine a set of requirements for robust peer computing, propose a small set of architectural principles designed to meet those requirements, and discuss the systematic exploitation of those principles in the context of Magi, a general- purpose, peering infrastructure for both embedded and enterprise applications.
... P2P systems have evolved across time and have wide range of applications and provide a good platform for many data and compute intensive applications [19], [20]. In order to adapt the Mobile Host to the P2P network, many of the current P2P technologies like Gnutella [19], Napster and Magi [21] are studied in detail. Most of these technologies are proprietary and are generally targeting specific applications. ...
... One alternative approach consists in providing run-time flexibility to the process. Supporting run-time modification of the workflow ensures the ability to overcome unexpected situations while maintaining the size of the workflow model (Reichert and Dadam 1998;Kammer et al. 2000). It is necessary to consider that removing any control or constraints wipes out the very reason for which workflow technology was introduced. ...
November 2000
Computer Supported Cooperative Work (CSCW)
... This paper proposes a process model for describing the input/ output of business processes and addresses three types of artifact usage anomalies. The model is based on component-based design technique (Zhuge, 2003; Hitomi and Le, 1998) and is compatible with existing control-oriented workflow design models. It provides an easier way to extract knowledge of artifact usages in a workflow . ...
October 1998
... In particular, a change of a process plan during enactment requires a complete restart of the process in most workflow management tools. However, there are a number of other approaches in the area of process modelling and enactment research, e.g.: Endeavors [4] is a support system for dynamic distributed execution of (workflow) processes; Serendipity [11] is a process modelling and enactment environment that supports collaborative modelling as well as execution of software processes; and CAGIS [22] is a Software Engineering Environment with emphasis on support of cooperative work. In CAGIS, it is possible to have local changes in processes in a decentralised manner. ...
October 1998
Proceedings - International Conference on Software Engineering
... ADEPT [6] focuses on enterprise wide workflows and cross-enterprise workflows, and supports both static and dynamic server assignments. Endeavors [16] and WorldFlow [18] use hypertext transfer protocol (HTTP) to provide a coordination mechanism for distributed process execution and tool integration on the Internet. DartFlow [8] uses transportable agents as the backbone to control the execution of process instances. ...
April 1999
... The goal of the ADAMS project is to provide a full feature environment supporting the software engineer during all the phases of the software lifecycle paying special attention to the coordination problems occurring in cooperative development environments. However, ADAMS is different than traditional Process centered Software Engineering Environments (PSEE)[16][17][18][19][20][21][22][23], as it is not designed around the definition and enactment of software processes. Rather, it is conceived for the definition and cooperative production of software artefacts. ...
October 1998