Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

6.
BEYOND BEING THERE A seminal paper by Hollan and Stornetta [Holland and Stornetta 91] Question: “(…) those at a distance will be at no real disadvantage to those colocated?” Not about the quality, but about the imitation of the ‘being there’ felling Analogy: crutches (broken leg) x shoes (enhance performance) Other characteristics: anonymity, semisynchronous discussions, feedback, archiving, and others

11.
AWARENESS – EARLY STUDIES [Heath & Luff 92] studied the coordination of activities of London Control Rooms (trains) Two actors: Line controller’s and DIA Seat side by side without direct communication Awareness by indirect interation: listen to conversations, gaze direction, monitoring displays, and indirect cues Implicit actions to coordinate the tasks: unobtrusive awareness Many implications for the design of CSCW applications Social focus on communication and coordination

16.
ARCHITECTURES “The architecture of a collaborative application is characterized by the modules, layers, replicas, threads, and processes into which the application is decomposed; the awareness in these components of collaboration functions; and the interaction among these components.” [Dewan 99] Decomposition of the system into components Synchronous, Assynchronous, Multi-synchronous and Quasi-synchronous WYSIWIS x relaxed WYSIWIS x WYSIWYG Many architectural models

18.
ARCHITECTURES – DISTRIBUTION Distributed system aspects in the architecture for synchronous groupware [Phillips 99]: Centralized: “(…)application on a single server and only the display services are found at the users’ sites.” Replicated: “(…) all data and computation is replicated at all sites” Semi-replicated: “(…) some aspects of computation and state are replicated while others are centralized.” Flexible: “(…) adjust the run time distribution architecture to suit application needs.” Many variations of these basic distribution architectures

21.
CONCLUSIONS Collaboration models help the design from the theoretical point of view Designers must provide more than the immitation of face to face meetings Design of synchronous applications have many challenges (and opportunities) Awareness is a central focus for communication, coordination and cooperation Different approches for developer synchronous CSCW applications Architectures help organize and distribute the components