Flexible architectures for CSCW system support

  • Authors:
  • Richard Bentley

  • Affiliations:
  • GMD-FIT

  • Venue:
  • ACM SIGOIS Bulletin - Special issue: workshop write-ups and positions papers from CSCW'94
  • Year:
  • 1995

Quantified Score

Hi-index 0.00

Visualization

Abstract

Despite the widespread attention CSCW has received from researchers and product developers there have been very few examples of successful cooperative applications. This lack of success can be attributed in part to the lack of principles we have for CSCW system development. Identification of such principles requires a better understanding of the core functionality required to support group work. My own belief is that tools which allow developers to experiment with different strategies to support cooperation, such as alternative approaches to information sharing and presentation, update propagation, synchronisation and so on, would contribute significantly to this understanding. As such I advocate an approach to the development of cooperative systems based on prototyping, and I see this as complementary to other work focusing on discovering and articulating social interaction in order to better inform cooperative system development.Cooperative applications place novel requirements on supporting architectures, over and above those of more traditional multi-user systems. One such requirement is the need for a high degree of flexibility, necessary to support different end-users, engaged in different tasks and often adopting different methods of working. This requirement for flexibility is emphasised if we consider toolkits and environments intended to support experimentation with different strategies for managing and promoting cooperative interaction.In this brief exposition I will attempt to support my position which is based on the need for experimental prototyping of cooperative systems, and justify the claim that this prototyping requires more flexible software architectures. My thinking in this area to date has been shaped largely by experiences gained in developing the MEAD multi-user interface prototyping environment at Lancaster University. Although the MEAD system proved useful for prototyping user interfaces to support the cooperative work of air traffic controllers, it is limited in the range of cooperative interaction which can be supported. In this respect I believe MEAD is similar to most other platforms supporting development of cooperative systems.