CS295J/Class 1

• class title [1]
• intro self [2]
• motivation for class [10]
  • a research project -- but loosely defined
  • brains work differently than user interfaces
  • specific things we know about brains should influence user interfaces
    • e.g., | seven plus or minus two
  • how?
  • what other things do we know like that?
  • can software that helps with all this, or just create ``best practices?
  • cognitive modeling, human-computer interaction, scientific visualization
• class goals [15]
  • learn how to take an abstract research concept and take it to a much more concrete research plan
  • learn about the field of HCI
  • learn about the field of cognitive modeling
  • learn about the field of scientific visualization
  • learn about learning new areas targeted at a research agenda
  • learn to work as a group
  • learn to tersely summarize research papers
  • be intellectually stimulated and excited
  • have fun!
• class activities
  • build a research proposal
• an aside: structure of an NIH proposal [15]
  • specific aims
  • background and significance
  • preliminary results
  • research plan
• class activities
  • find papers/books/chapters
  • read papers/books/chapters
  • write summaries of pieces related to research goals
  • identify important topics and structure within disciplines
  • organize readings into topics
  • codify design rules motivated by cognition (or from HCI or other literature)
  • codify performance predictions
  • critique interfaces based on those rules
  • analyze the critiques
  • design some preliminary results
    • experiments?
    • software systems?
• theory of visualization presentation
• vrl wiki tutorial
• media wiki tutorial
• augment a reading list
  • find an expert (yourself, a professor, a student)
  • surf some course syllabi (try "HCI syllabus")
• assignment 1
  • spend 10 hours adding to any part of the wiki you think isrelevant
  • by Monday noon add any potential readings. If you've got a tentative summary evaluation, go ahead and add it. It's ok to edit folks summary evaluations, but try to make the result more accurate or precise without losing information.
  • by Wednesday noon finish with any summary evaluatio and also identify at least one as-relevant-as-possible reading as yours. Put your name on that entry in the reading list as the ``owner so that there are no duplicates.
  • by Wednesday 5pm -- select 2 additional relevant readings that are owned and that you will read by Friday and be prepared to discuss. Put your name as a ``discussant in the reading list; there should be a max of two discussants per reading.
  • by Friday class -- author a summary description, less than 250 words, in the wiki of how the reading you own relates to our project. Be prepared to describe, in two minutes, how your reading relates to the project. Also be prepared for everyone in class to discuss after your description. You may bring notes for yourself, but no slides. The wiki page for your reading will be displayed while you talk.
  • by Friday class -- read and be prepared to discuss the other two readings you choose.
  • by Friday class -- make one more wiki page titled "<Last-Name> week 1" with a list of the keys for the citations you added, the readings you summarized, the reading you presented, the two readings you were a discussant on, and any other readings you did in detail.
  • Let me know if you have any kind of problems. You should be spending right around 10 hours -- if that's a problem, let's talk.
  • The How Tos page has some tips. Edit or add as you find others.