ARIADNE and HOPLa: Flexible Coordination of Collaborative Processes

The Ariadne system and its modeling language HOPLa aim to provide generic support for hybrid collaborative processes, i.e. complex information processing tasks involving coordinated contributions from multiple people and tools. Ariadne should be usable for a wide variety of such processes and actively support people working in them and defining and managing them. The basic concept in Ariadne is that of a process. It combines a shared workspace with mechanisms to control the growth and evolution of this workspace. The workspace holds tree-shaped data and is selfdescriptive, in the sense that it holds the actual data but also the constraints (i.e. type definitions) that govern its structure. Nodes in the workspace can be marked as tasks to be performed and coordination operators and constraints, e.g. on the deadline or performer of a task, can be attached. Ariadne manages active processes and provides the interaction with the outside world. When tasks are enabled, actors are notified and results of their actions are stored in the workspace. A key issue for Ariadne is flexibility. It should be easy for users to model and create new kinds of processes even if this happens during the work in the process itself. This is addressed in two ways. First, process workspaces can be adapted arbitrarily within the limits of typedefinitions stored within them. Second, both process descriptions and running processes are HOPLa programs. This means that a running process can be stopped, arbitrarily modified (through editing of the program text) and continued whenever exceptions make this necessary and without the loss of any data that had already been produced.

[1]  Clarence A. Ellis,et al.  Groupware: some issues and experiences , 1991, CACM.

[2]  Christopher Fry,et al.  Experiments with Oval: a radically tailorable tool for cooperative work , 1992, CSCW '92.

[3]  L. Suchman Plans and situated actions , 1987 .

[4]  Sergio Bandinelli,et al.  Computational reflection in software process modeling: The SLANG approach , 1993, Proceedings of 1993 15th International Conference on Software Engineering.

[5]  Ian M. Holland,et al.  Contracts: specifying behavioral compositions in object-oriented systems , 1990, OOPSLA/ECOOP '90.

[6]  Nicholas Carriero,et al.  Coordination languages and their significance , 1992, CACM.

[7]  Kevin Crowston,et al.  What is coordination theory and how can it help design cooperative work systems? , 1990, CSCW '90.

[8]  Farhad Arbab,et al.  An overview of manifold and its implementation , 1993, Concurr. Pract. Exp..

[9]  Jon Atle Gulla,et al.  Modeling Cooperative Work for Workflow Management , 1994, CAiSE.

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

[11]  Michael L. Begeman,et al.  gIBIS: a hypertext tool for exploratory policy discussion , 1988, CSCW '88.

[12]  Hassan Aït-Kaci Type Subsumption as a Model of Computation , 1984, Expert Database Workshop.

[13]  Gail E. Kaiser,et al.  A bi-level language for software process modeling , 1993, Proceedings of 1993 15th International Conference on Software Engineering.

[14]  Don Libes Kibitz—connecting multiple interactive programs together , 1993, Softw. Pract. Exp..

[15]  Brad Hartfield,et al.  Computer systems and the design of organizational interaction , 1988, TOIS.

[16]  Alexander Schill,et al.  Language and distributed system support for complex organizational services , 1991, COCS '91.

[17]  Simon M. Kaplan,et al.  Flexible, active support for collaborative work with ConversationBuilder , 1992, CSCW '92.

[18]  Daniel Le Métayer,et al.  The GAMMA Model and Its Discipline of Programming , 1990, Sci. Comput. Program..

[19]  Jari Alasuvanto,et al.  Distributed form management , 1990, TOIS.

[20]  Danny Greefhorst A Simulation Environment For Ariadne , 1995 .

[21]  F. vov Martial A conversation model for resolving conflicts among distributed office activities , 1990, COCS '90.

[22]  Pattie Maes,et al.  Computational reflection , 1987, The Knowledge Engineering Review.

[23]  Steven Pemberton,et al.  The MUSA design methodology , 1992 .

[24]  Jacques Wainer,et al.  A conceptual model of groupware , 1994, CSCW '94.