This course of Advanced Topics in HCI includes discussions about a set of representative papers published in the field of HCI, and creation and demonstration of interactive systems. Students lead their own capstone projects where they build interactive systems and present their demonstrations at the last class.
This course is double-listed as “3747-108: Advanced Topics in HCI” in Graduate School of Engineering and “4915100: Human Interfaces” in Interfaculty Initiative in Information Studies, Graduate School of Interdisciplinary Information Studies. Students are allowed to register only to either of these two courses. Everything besides a course name is the same, so no worries about which one you should register. :)
この講義は工学系では「3747-108: ヒューマンコンピュータインタラクション特論」，情報学環・学際情報学府では「4915100: ヒューマンインタフェース」として提供されています．学生はどちらかの講義にしか登録できません．講義の名前以外はすべて同じですので，どちらかで登録していただければ結構です．:)
| Room | 93B on the ninth floor in Eng. Bld. 2 |
|---|---|
| Time | Mondays (not Thursdays), 10:25-12:10 (including a short break) |
| Instructor | Koji Yatani (koji “at-mark” iis-lab.org) |
This course has two major objectives: getting familiarized with classic and recent HCI research that well demonstrates novel interactive systems and applications, and prototyping an interactive system. To achieve them, this course offers a mixture of research discussions on HCI papers and capstone projects.
Except the first and last classes, the rough class structure is as follows:
English is the official language in this course though Japanese may be used if necessary. All teaching is done in English at a class. Students are strongly recommended to deliver their presentations and demonstrations in English. You may use Japanese when you have large difficulties in communication, but you must always try your best to speak English.
We do not have any explicit prerequisite for this course, but students are expected to have:
But, the most important is, of course, your strong passion. :)
We have no tolerance to any type of academic misconducts, such as plagiarism, inappropriate citations, and fabrications. Examples are:
In case serious academic misconducts are found, we give following strong penalties depending on their significance.
Please make sure that your reports and source codes do not cause misunderstandings.
Auditing students are welcome to join us. But I strongly recommend you to do a discussion chair even if you are just auditing. Also participate in discussions at the class. Just don't be a free rider. :)
Your performance in this course will be evaluated in the following criteria.
You must both do a discussion chair at least twice and complete your capstone project to get a final mark. Otherwise, your mark will be zero.
| Class | Date | Contents | |
|---|---|---|---|
| #1 | 8, April | [Introduction] | Course introduction, reading assignment |
| [Research Discussions] | Quick overview of HCI research areas covered in this course | ||
| #2 | 15, April | [Research Discussions] | Brainstorming with vision videos |
| #3 | 22, April | [Research Discussions] | Sensing touch and gestures |
| #4 | 13, May | [Research Discussions] | On-body interaction |
| #5 | 20, May | [Research Discussions] | On-body actuation |
| #6 | 27, May | [Research Discussions] | Sensing your body with smartphones |
| #7 | 3, June | [Capstone Project] | Project peer review |
| #8 | 10, June | [Research Discussions] | Wearable sensing |
| #9 | 17, June | [Research Discussions] | Sensing with smartwatches |
| #10 | 24, June | [Research Discussions] | Infrastructure-based sensing |
| #11 | 1, July | [Research Discussions] | Interacting with your mood |
| #12 | 8, July | [Capstone Project] | Project peer review |
| #13 | 22, July | [Capstone Project] | Project demo presentation |
Please submit your paper preference from the following Google Form page by 11th April.
https://forms.gle/masNXefgqX4nH7Qe6
In research discussions, we discuss some of recently-published HCI work that demonstrates strong novelty and/or progress in this field. After the first class, please name your preferences in this page.
In Class #1 , we discuss some vision videos. If you are interested in checking more videos, use the following links to find your favorites.
A capstone project aims to obtain experience of building an interactive system with hardware and delivering a live demonstration and demonstrating at least one cool application scenario.
You are encouraged to collaborate with your fellow students and team up for capstone projects. However, your team must be up to three people. I recommend to work in a team of two. Marks for the capstone project will be given equally to all team members.
Your system must be interactive and use some kinds of sensing or hardware. You may use anything for your project. Your hardware can be smartphones, cameras, Kinect sensors, and/or what you build by yourselves. As one of the objective of this assignment is to experience hardware hacks, projects with codes only are not acceptable.
You also must demonstrate at least one cool application scenario (excluding games) with your systems. Your application does not have to be large-scale or complex, but you have to demonstrate that your system would be something useful to potential users instead of just being cool.
You will be asked to do a live demonstration at the last class. So make sure that your final system works in real time. Your system will likely to perform some sort of recognition (heuristically or with machine learning). The recognition does not have to be super accurate, but it has to work reasonably well.
We do not care about what programming languages or environment you use. If you need suggestions or support, please consult with the instructor though we do not guarantee providing the stuff you want.
You must deliver the following items at the end of the course.
We evaluate your capstone projects in the following criteria:
Examples of capstone projects are as follows (but not limited to):
After the last class, each team will have another two weeks to refine the system and shoot a demonstration video. The demo video should describe the walkthrough of your system and some details about the implementation. I expect each video to be up to five minutes and under 100MB though these are not a hard limit.
Before creating your demo video, please review those published in CHI, UIST, and/or other major HCI conferences. The videos we have seen during the class would be good to review too. These videos will give you a better idea of what you should have in your submission.
The due date for your video submission is 26th July, 23:59 JST. Please upload your video through Dropbox file requests. The instructor will share the link for the file requests. In addition, please describe the following information in another separate PDF file.
If you have any trouble or question on submitting your video, please contact the instructor well in advance.