Coordination Science: Challenges and Directions

Several distinct kinds of “coordination technology” have evolved to support effective coordination in cooperative work. This paper reviews some of the major weaknesses with current coordination technology and suggests several technical directions for addressing these weaknesses. These directions include developing semi-structured process representations that explicitly capture cooperative work inter-dependencies, exploiting advanced product and software design technologies for process design, and integrating coordination technologies to synergistically combine their strengths and avoid their individual weaknesses.

[1]  William J. Clancey,et al.  Classification Problem Solving , 1984, AAAI.

[2]  Ira P. Goldstein.  Bargaining Between Goals , 1975, IJCAI.

[3]  Surya B. Yadav,et al.  Requirement definition architecture—an overview , 1985 .

[4]  Terry Winograd,et al.  A language/action perspective on the design of cooperative work , 1986, CSCW '86.

[5]  Carl Hewitt,et al.  Offices are open systems , 1986, TOIS.

[6]  David C. Brown,et al.  Failure handling in a design expert system , 1985 .

[7]  François Vernadat,et al.  Open system architecture for CIM: edited by ESPRIT Consortium AMICE. Published by Springer-Verlag, Berlin, Germany. 1989. 212pp. £14.00 , 1992 .

[8]  Stephen F. Smith,et al.  ISIS—a knowledge‐based system for factory scheduling , 1984 .

[9]  Raymond McCall,et al.  Making argumentation serve design , 1991 .

[10]  Reid G. Smith,et al.  The Contract Net Protocol: High-Level Communication and Control in a Distributed Problem Solver , 1980, IEEE Transactions on Computers.

[11]  Jean-Claude Latombe,et al.  Making Compromises Among Antagonist Constraints in a Planner , 1985, Artif. Intell..

[12]  Robert P. Smith,et al.  A model-based method for organizing tasks in product development , 1994 .

[13]  Mark Klein.  Conflict management as part of an integrated exception handling approach , 1995, Artif. Intell. Eng. Des. Anal. Manuf..

[14]  K. C. Burgess Yakemovic,et al.  Report on a development project use of an issue-based information system , 1990, CSCW '90.

[15]  Mark Stefik,et al.  Planning with Constraints (MOLGEN: Part 1) , 1981, Artif. Intell..

[16]  Lucy A. Suchman,et al.  Office procedure as practical action: models of work and system design , 1983, TOIS.

[17]  Terry Winograd,et al.  The action workflow approach to workflow management technology , 1992, CSCW '92.

[18]  Richard M. Young,et al.  Options and Criteria: Elements of design space analysis , 1991 .

[19]  Mark Klein,et al.  Supporting conflict resolution in cooperative design systems , 1991, IEEE Trans. Syst. Man Cybern..

[20]  Mark Klein.  iDCSS: Integrating Workflow, Conflict and Rationale-Based Concurrent Engineering Coordination Technologies , 1995 .

[21]  John McDermott,et al.  VT: an expert elevator designer , 1987 .

[22]  Bernard Widrow,et al.  Neural networks: applications in industry, business and science , 1994, CACM.

[23]  Jon Dukes-Schlossberg,et al.  Cosmos: A System for Supporting Engineering Negotiation , 1994 .

[24]  B. Karbe,et al.  Influence of exception handling on the support of cooperative office work , 1990, SIGO.

[25]  Douglas R. Vogel,et al.  Technological Support for Group Process Modeling , 1994, J. Manag. Inf. Syst..

[26]  Jonathan Grudin,et al.  Groupware and social dynamics: eight challenges for developers , 1994, CACM.

[27]  K. Kosanke.  CIMOSA: Offene System-Architektur , 1993 .

[28]  Gerald Jay Sussman,et al.  CONSTRAINTS - A Language for Expressing Almost-Hierarchical Descriptions , 1980, Artif. Intell..

[29]  Jintae Lee,et al.  What's in design rationale? , 1991 .

[30]  Tadao Murata,et al.  Petri nets: Properties, analysis and applications , 1989, Proc. IEEE.