SPRING 2006
CS294: Integrating Physical and Digital Interactions
Thursday, 11:00AM - 1:30PM, Gates 100

Scott Klemmer, 384 Gates
Office Hours: Tuesdays 1:15-2:15PM

TA: Björn Hartmann, 376 Gates
Office Hours: by email appointment (bjoern at cs.stanford.edu)


 

Final Projects

The final projects of CS294h were presented on 6/12 at the CS Software Faire. You can find papers and images on the project page.

Overview

Today, physical and electronic media coexist unaware of each other. Contemporary design studios, offices, and labs are filled with both physical and electronic artifacts, but the two exist separately, and the infrastructure for moving between media representations—scanning and printing—is heavyweight and cumbersome, at odds with the freewheeling, organic nature of creative work.

Students in this CS294 will work in groups on a quarter-long, mentored research project. Mentors will be PhD students in the Stanford HCI Group and Reuters Digital Vision Fellows. Students will produce a piece of publication-quality research.

Students in this course are encouraged to attend CS547, the HCI seminar, on Fridays from 12:30 - 2:00.
 

Requirements & Grading

The course is organized around a quarter-long mini-research project. The final paper should be two pages long in the CHI format, and is due Friday, June 9th at 9:00am. The final presentations will be on Wednesday June 7th from noon to 1:30pm. Students are encouraged to submit their projects as posters, demos, or videos to Ubicomp 2006. The course grade comprises the following:

   15% Paper critiques: Students will work with their mentors and the teaching staff to select three papers to read each week for the first six weeks. Students should submit short critiques of each reading to cs294H(at)cs.stanford.edu. PDFs of readings are available in the password-protected directory cs249h/readings/. Critiques are due by 6:00am the day of class; late critiques will not be accepted. Each student may opt to pass on one week of critiques for any reason (personal or family matters, conflicting deadlines, etc.); there are no exemptions beyond this.
   15%
Concept: How interesting and engaging is the problem? How appropriate is the scope?
   20% Implementation: How complete and functional is the implementation
   20% Evolution and Iteration: How much did you iterate and refine your ideas? How well did you incorporate the results of user testing?
   10% Presentation: Did you clearly explain your idea at the final project presentations?
   10% Final Report: Quality of your user test and subsequent reflection; explanation of your ideas, motivation, and alternatives
   10% Class participation

 

06 Apr Course Introduction
Björn Hartmann, Brian Lee, Ron Yeh, Reuters Fellows
13 Apr Users & Design Insight
Due: two-page proposal about target users & design insight, including schedule for the quarter
Due: reading summaries
20 Apr Scenarios & Storyboards
Due: Scenario skit and storyboard
Sue: reading summaries
27 Apr Rapid Prototype, Part I
Due: reading summaries
04 May Rapid Prototype, Part II
Due: reading summaries
11 May Full Prototype, Part I
Due: reading summaries
18 May Full Prototype, Part II
Due: reading summaries
25 May Full Prototype, Part III
01 Jun Full Prototype, Part IV
12 June
12:15-3:15pm
Class Project Presentations
Wallenberg Hall
14 June
2:00pm
Project Papers Due