This page and its content are solely for students enrolled in the 2025-2026 HCI Masters at Université Paris-Saclay and the IGD Masters at Télécom Paris. It contains instructors' material (slides and audio recordings) that are not to be distributed without the author's written consent, and copyrighted materials (such as articles) that are only made available under the fair use exception to copyright law.
Course Summary
This course presents computer-supported collaborative systems, which allow a group of people, whether they are collocated or not, to work together while sharing computer artifacts. The course covers groupware and mediated interaction, including a state-of-the-art of interactive systems for coordination, communication and collaboration with groups of users across time and space. The course also covers Collaborative Virtual Environments, a research area at the intersection of Virtual Reality, Augmented Reality, teleoperation, high-bandwidth communication, human-computer interaction and collaborative teleworking. Finally it covers recent developments such as social networks and crowdsourcing.
Schedule
Room E105, building 640 (PUIO) Michel Beaudouin-Lafonmbl@lisn.fr
The project must be done in a group of 1, 2 or 3 students, and will be presented orally as well as in a short report.
The project can be a programming project OR a design project.
Programming project: Program a small collaborative tool, or extend an existing one.
You can replicate or extend an existing tool, and you can use existing libraries, but you must create your own code for a significant part of the collaborative features.
For your project proposal (week 3), prepare 3 slides that describe (i) your concept, (ii) the features you plan to implement in order of priority, (iii) the tools you'll use to develop it.
Design project: Design a novel collaborative tool or service, or a new collaborative feature for an existing tool or service. You must follow the design process from Wendy's Design of Interactive Systems class, and create a video prototype of your design.
For your project proposal (week 3), prepare 3 slides that describe (i) your concept, (ii) related papers/systems you have reviewed, (iii) what is novel about your concept.
Process
Enter the names of the project members with a description of the project in this spreadsheet.
Wait until you get a green light in the spreadsheet.
If you get a yellow or red light, revise your project, reset the color and wait for new feedback.
Once you have a green light, develop your project.
Prepare 3 slides do present your project in week 3, as described below.
Write a short report (2-3 pages) before week 7, as described below.
Prepare a short presentation and demo of your project (5-10 minutes) for week 7, as described below.
For your project proposal presentation on week 3 (Nov 19):
Prepare 3 slides and a 3-minute presentation :
For a programming project: describe (i) your concept, (ii) the features you plan to implement in order of priority, (iii) the tools you'll use to develop it.
For a design project: describe (i) your concept, (ii) related papers/systems you have reviewed, (iii) what is novel about your concept.
Add a link to the slides in your group's section in this spreadsheetbefore noon, Tuesday 18 November 2025.
The project report must be turned in by 5pm, Tuesday 16 December 2025.
Add a link to the PDF of the report in the project spreadsheet.
You will have 10 minutes for the oral presentation, all members of the group must speak! Make sure to relate your work to the concepts taught in class.
Programming project:
The 3-5 pages final report must describe the features you implemented, the tools/libraries/language you used, and the problems you ran into.
The final oral presentation must include a live demo of the software.
Design project:
The 2-3 pages report must describe your design process and justify your choices.
The final oral presentation must include the video prototype.
The Information, James Gleick (2012) - this book covers much more than mediated communication, but has fascinating stories about the development of pre-telephone communication systems
Groupware - Some Issues and Experiences. C.A. Ellis, S.J. Gibbs and G.L Rein, Communications of the ACM, 1991. (Describes GROVE towards the end of the paper)
Design and Use of a Group Editor, Ellis, Gibbs and Rein, in Cockton (Ed.), Engineering for Human-Computer Interaction, North-Holland, 1990. (Describes GROVE but not available online)
Social Media for Software Engineering. A. Begel, R. DeLine, and T. Zimmermann, Proceedings of the FSE/SDP workshop on Future of software engineering research (FoSER '10), 2010.
What's wrong with git?: a conceptual design. S. Perez De Rosso and D. Jackson, Onward! Proceedings of the 2013 ACM international symposium on New ideas, new paradigms, and reflections on programming & software, 2013.
