Synchronous Collaboration and Awareness SystemsSlide 2Why CSCW Research is ImportantGrudin’s Time/Space ModelDegrees of InterdependenceCollaboration TransparencyWhat You See Is What I SeeMaintaining Awareness: What You See Is What I Think You SeeConventional Collaboration Transparency ArchitectureConcurrency ControlLimitations of Collaboration-Transparency SystemsCollaboration-Aware ApplicationsSlide 14Workspace AwarenessReplicated ArchitectureCan We Achieve Spontaneous Collaboration?Flexible JAMM: Replication + Object ReplacementSingle- to Multi-user Object ReplacementReplacement ProcessConcurrent Editing using Operational TransformationWhat About System Resources?Flexible JAMM’s Proxied System ResourcesDoes it Work? Could it Introduce Problems?Performance TimeUser Perceptions - Text EntryUser Perceptions - Copy EditEvaluation - other resultsSun SharedShellSharedShell VideoAwareness through the agesAwarenex“Presence” = can be reachedBuddy list is nearly useless when someone is not PresentRhythms in Group CoordinationSlide 37Key Factors Affecting RhythmsPredictability varies between individualsHuman-observable patterns in Presence HistoryModeling ApproachesGoal: Descriptive model of temporal patterns to augment user’s mental model of rhythmsStep 1: Estimate Transition PeriodsStep 2: Cluster observed inactivity periods by distance from estimated periodsExample Rhythm ModelExample with Location TransitionEnd-user Visualizations – Which are Easier to Interpret?Integrating Rhythms and IMProbability that Inactivity is a TransitionSlide 51OutlinePresence ≠ AvailabilityTwo philosophies on infering availabilitySalient Factors in Detecting Unavailability in an OfficeLilsysClient InterfaceUsage ObservationsDid it work?What’s next?Impression ManagementWhen is Dagwood Available?Rhythm and Unavailability InferencingSlide 64ReferencesSynchronous Collaboration and Synchronous Collaboration and Awareness SystemsAwareness SystemsBo BegoleUbiquitous Computing Area ManagerComputer Science LabUC Berkeley, Sep 25, 2006Synchronous Collaboration and Synchronous Collaboration and Awareness SystemsAwareness SystemsDegrees of InterdependenceReplicated Application Sharing: Flexible JAMMMulti-user UNIX terminal: SharedShellAwareness:–ConNexus–AwarenexPresence and Availability Forecasting:–Rhythm Awareness–LilsysWhy CSCW Research is ImportantWhy CSCW Research is ImportantInter-Personal ComputingMost of what we do with computers is communicated to others–Documents–Information Analysis–Even calculating Ballistic Missile trajectories are a form of communication (“I hate you”)CSCW combines systems and social researchGrudin’s Time/Space ModelCoLocated RemoteSynchronous Meeting RoomsVideo conferencingAsynchronousArgumentation ToolsEmailDegrees of InterdependenceDegrees of InterdependenceModeratelyInterdependent workAsynchHighly interactive InterdependentworkWeaklyInterdependent workSemi,Peri,Psuedo-synch SynchronousProductivityToolsCommunicationToolsProposalModule-level programmingReviewsSystem design & prgrmngNegotiationSystem integration & debuggingTwoExamplesResearch Funding:Technology Development:IMSMSPush-to-talkaudioFull-duplexaudioFace-to-facemeetingemailBlogsUsenetWebpagesPaperMemos Text chatShared AppsWikisShared FileSystemsEditorsMeetingSupportSystemsMultiplayerGamesDecisionSupportSystemsDistributedPresentationBrowsers &other ViewersTimeSpentTaskCriticalityCollaboration Transparency•Sharing single-user legacy applications•Application source code is not modified•Runtime environment is modified•sharing mechanism is “transparent” to application.•Synchronous “Application sharing” for•Pair programming•Debugging/integration•Collaborative document editing•Examples: •NetMeeting, WebEx, GoToMyPC, SharedX, SharedApp, XTV, SunForum, Timbuktu, etc.What You See Is What I See•Collaboration is grounded in shared view, but•prevents independent work •Collaboration is grounded in shared view•Are there downsides to WYSIWIS?Maintaining Awareness: What You See Is What I Think You SeeConventional Collaboration Transparency ArchitectureNetworkTrafficDisplayDisplayUserInputUserInputDisplayBroadcasterConferenceAgentMergedInputApplicationConference Agent HostUser A Host User B Host•Centralized architecture •One copy of application•Remote inputs merged•Graphics output sent to each remote participant•Used by all collaboration-transparent systemsDoes this model human collaboration?•Input events can interleave and conflict•Solution: take turns using “floor control”•How well does turn-taking model human collaboration?Concurrency Control(a) intended result of two users drawing curves simultaneously(b) unintended result due to conflicting mouse movement eventsLimitations of Collaboration-Transparency Systems•Strict What You See Is What I See•Slower application responsiveness•No concurrent work•Limited group awareness information•Higher network bandwidth requirement than collaboration-aware applicationsCollaboration-Aware Applications•Applications designed for collaborative use•Examples: •Editors – SASSE, Calliope, SubEthaEdit, Writely •Whiteboards – innumerable •Chat – ICQ, AIM•Visualization – CAPI, Shastra, Sieve•Work flow – TeamRooms, Groove•Learning – LiNC, CoVis•Games – Diablo, Doom, WorldOfWarcraft, There•Toolkits – Habanero, Tango, GroupKitCollaboration-Aware ApplicationsShared editorsShared whiteboardsSubEthaEditWorkspace Awareness•Information about participants:•identity•location•activity•accessTelepointers to represent remote mouse cursors“radar” views to indicate remote scroll positions•Copy on each host•Remote inputs merged•Inputs distributed•Enables:•Lower network bandwidth•Independent views•Concurrent workReplicated ArchitectureNetworkTrafficDisplayDisplayUser B HostUser A HostUserInputUserInputEventBroadcasterMergedInputConferenceAgentConference Agent HostAppli-cationAppli-cationCan We Achieve Spontaneous Collaboration?•Co-workers “encounter” each other•Accessing shared content, docs, code, etc.•Within shared events, web sites, meetings, etc.•Applications morph into collaborative versions on-the-fly•Research prototypes•Flexible JAMM [Begole et al. 99]•Zipper [IBM]•Co-Word/Co-PowerPoint [Griffith U.]Flexible JAMM: Replication + Object ReplacementSingle- to Multi-user Object Replacement(a) Original