Agenda Morris LeBlanc: CMC Project update CSCW Ubicomp

Part 3 Presentation next week 15 minutes each (including questions) Load slides onto swiki Motivation Requirements learning from users Design learning from prototyping Evaluation Conclusions Q&A

Computer-Supported Cooperative Work (CSCW) Thinking about groups, collaboration, and communication

CSCW Computer Supported Cooperative Work HCI connotationsCSCW individual use psychology

CSCW Study how people work together as a group and how technology affects this Support the social processes of work, whether co- located or distributed Support the social processes of a group of people communicating or collaborating in any situation

Examples Awareness of people in your family, community, workplace... Mobile communication Online discussions, blogs Sharing photos, stories, experiences Recommender systems Playing games

Groupware Software specifically designed to support group working or playing with cooperative requirements in mind NOT just tools for communication Groupware can be classified by when and where the participants are working the function it performs for cooperative work Specific and difficult problems with groupware implementation

The Time/Space Matrix Classify groupware by: when the participants are working, at the same time or not where the participants are working, at the same place or not Common names for axes: time: synchronous/asynchronous place: co-located/remote different time same time same place different place

Time/Space Matrix Examples Time Place Synchronous Co-located Asynchronous Remote Face-to-face E-meeting room Post-it note Argument. tool Phone call Video window,wall Letter

A More-fleshed Out Taxonomy A typical space/time matrix (after Baecker, Grudin, Buxton, & Greenberg, 1995, p.742)

Styles of Systems Computer-mediated communication Meeting and decision support systems Shared applications and tools

Computer-mediated Communication (CMC) Aids Examples , Chats, virtual worlds Desktop videoconferencing -- Examples: CUSee-Me MS NetMeeting SGI InPerson

Food for thought… Why aren’t videophones more popular? How and when do you use Instant Messaging? How does this differ from ? What communication technology do you still want?

Meeting and Decision Support Systems Examples Corporate decision-support conference room Provides ways of rationalizing decisions, voting, presenting cases, etc. Concurrency control is important Shared computer classroom/cluster Group discussion/design aid tools

Shared Applications and Tools Shared editors, design tools, etc. Want to avoid “locking” and allow multiple people to concurrently work on document Requires some form of contention resolution How do you show what others are doing? Food for thought: What applications do you use concurrently with someone else? Why? Do they work? What applications would you want to use concurrently with someone else? Why?

Social Issues People bring in different perspectives and views to a collaboration environment Goal of CSCW systems is often to establish some common ground and to facilitate understanding and interaction

Turn Taking There are many subtle social conventions about turn taking in an interaction Personal space, closeness Eye contact Gestures Body language Conversation cues How is turn taking handled in IM?

In group dynamics, the physical layout of individuals matters a lot “Power positions” How can you tell power in a videoconference? Geography, Position

Awareness What is happening? Who is there? e.g. IM buddy list What has happened … and why? How do you use awareness in IM? What other systems have awareness?

Groupware implementation Often more complicated feedback and network delays architectures for groupware feedthrough and network traffic robustness and scaling

Groupware Challenges (Grudin) Who does work vs. who gets benefit The system may require extra effort for people not really receiving benefit Critical mass Need enough people before system is successful Groupware and Social Dynamics: Eight Challenges for Developers By Jonathan Grudin (now at Microsoft)

More Grudin challenges Social, political, and motivational factors Outside factors can affect system success No “standard procedures” Many procedures and exceptions when it comes to groups interacting Groupware and Social Dynamics: Eight Challenges for Developers By Jonathan Grudin (now at Microsoft)

More Grudin challenges Infrequent features How often do we actually use groupware anyway? Solution: add groupware features to existing individual software Need to manage deployment and acceptance Groupware and Social Dynamics: Eight Challenges for Developers By Jonathan Grudin (now at Microsoft)

Evaluation Evaluating the usability and utility of CSCW tools is quite challenging Need more participants Logistically difficult Apples - oranges Often use field studies and ethnographic evaluations to assist Groupware and Social Dynamics: Eight Challenges for Developers By Jonathan Grudin (now at Microsoft)

Recommendations Add group features to existing apps Benefit all group members Start with niches were application is highly needed Consider evaluation and adoption early Expect and plan for development and evaluation to take longer

Example: TeamSpace Distributed meeting recording and access system Web interface – groups had workspace, required username to log in Capture interface – distributed, real time system Access interface – individual review

TeamSpace issues Implementation was tough! Responsiveness important, but then how to handle message delivery and conflicts? What to do when network goes down? Debugging was very difficult Whole group had to agree to be recorded One person needed to record, then all could review Infrequently used – easy to forget it was there Required log in – hard to just try out the system Good evaluation required adoption, which required all of the above…

Ubiquitous Computing Computers everywhere

Ubiquitous Computing (Ubicomp) Move beyond desktop machine Computing is embedded everywhere in the environment A new paradigm?? “off the desktop”, “out of the box”, pervasive, invisible, wearable, calm, anytime/anywhere/any place, …

Ubicomp Notions Computing capabilities, any time, any place “Invisible” resources Machines sense users’ presence and act accordingly

Some videos V-g&feature=related V-g&feature=related OXk&feature=related

Marc Weiser: The father of ubicomp Chief Technologist Xerox PARC Began Ubiquitous Computing Project in Scientific American article got the ball rolling

Ubicomp is... Related to: mobile computing wearable computing augmented reality In contrast with: virtual reality

HCI Themes in Ubicomp Some of the themes: Natural interaction Context-aware computing Automated capture and access Everyday computing

How does interaction change? More “natural” and situated dialogue Speech & audio Gesture Pen Tangible UIs Distributed & ambient displays Plus… sensed context …and actuating physical objects

Distributed Displays The Everywhere Display Project at IBM Dynamic Shader Lamps – virtual painting on real objects

Ambient Displays The Information Percolator Ambient Orb

Peripheral Displays Kimura Digital Family Portrait

One take on scales Based on ownership and location body desk room building From the GMD Darmstadt web site on I-Land

What is Context? Any information that can be used to characterize the situation of an entity Who, what, where, when Why is it important? information, usually implicit, that applications do not have access to It’s input that you don’t get in a GUI

Example: Location services Outdoor Global Positioning Satellites (GPS) wireless/cellular networks Indoor active badges, electronic tags vision motion detectors, keyboard activity

How to Use Context To present relevant information to someone Mobile tour guide To perform an action automatically Print to nearest printer To show an action that user can choose Want to phone the number in this ?

Context-aware scenarios Walk into room, lights, audio, etc. adjust to the presence of people Communication between people (intercoms, phones, etc. ring to room with person) Security, emergency calls based on people in the home Monitor health, alert when needed

Automated capture and access Use of computers to preserve records of the live experience for future use (Abowd & Mynatt 2000) Points of consideration: capture needs to be natural user access is important details of an experience are recorded as streams of information

Capture & access applications Compelling applications Design records Evidence based care Everyday communication Family memories Annotations Fusion, indexing, summarization

Example: Personal Audio Loop

Designing for Everyday Activities No clear beginning or end Closure vs. flexibility and simplicity Interruption is expected Design for resumption Concurrent activities Monitoring for opportunity Time is important discriminator Interpret events Associative models needed Reacquire information from multiple pts of view

Technical Challenges Connectivity – almost constant How to gracefully handle changes? Sensing How to gather useful info? (i.e. location?) Integration and analysis of data How to recognize activity and recover when incorrect? How to function at acceptable speeds? Scale – both in information and size of displays

Challenge of Evaluation Bleeding edge technology Novelty Unanticipated uses Quantitative metrics Variety of social implications/issues

Social issues Privacy – who has access to data? How do we make users aware of what technology is present? Differing perspectives and opinions Jane likes that the environment is aware she is present, but John doesn’t…