Fourth And Fifth Weeks

HCILectures.FourthAndFifthWeeks History

Hide minor edits - Show changes to markup

July 10, 2007, at 01:19 PM by 136.159.7.242 -
Changed lines 27-29 from:
  • what made write-ups excellent
  • what made write-ups weak
  • where marks were typically lost
to:
  • what made write-ups excellent
  • what made write-ups weak
  • where marks were typically lost
Changed lines 40-42 from:
  • report should be oriented toward manager
  • must be readable
  • must show deep thought
to:
  • report should be oriented toward manager
  • must be readable
  • must show deep thought
Changed lines 58-59 from:
  • not to ambitious/large
  • better to have excellent interface to small system implementable
to:
  • not to ambitious/large
  • better to have excellent interface to small system implementable
July 10, 2007, at 01:18 PM by 136.159.7.242 -
Changed line 22 from:
to:

\\

Changed line 33 from:
to:

\\

Changed line 44 from:
to:

\\

Changed line 52 from:
to:

\\

July 10, 2007, at 01:17 PM by 136.159.7.242 -
Deleted line 0:
Changed lines 11-12 from:
to:


\\

July 10, 2007, at 01:17 PM by 136.159.7.242 -
Changed lines 1-5 from:
  CPSC  481

Foundations of HCI Saul Greenberg, Instructor Contents Back to lab materials for teaching assistants Notes for Teaching Assistants — Labs 4 & 5

to:

Notes for Teaching Assistants — Labs 4 & 5

July 10, 2007, at 01:16 PM by 136.159.7.242 -
Changed lines 5-6 from:

Your fourth lab session

to:

Your fourth lab session

Changed lines 10-15 from:
    * Grade the assignments and get them back to me by the end of the week so I can check them
    * Be available for students who are doing Assignment 2.
    * Collect general comments on Assignment 1 (strengths/weaknesses) that you will tell students to follow/avoid for Assignment 2.

Your fifth lab session

to:
  • Grade the assignments and get them back to me by the end of the week so I can check them
  • Be available for students who are doing Assignment 2.
  • Collect general comments on Assignment 1 (strengths/weaknesses) that you will tell students to follow/avoid for Assignment 2.

Your fifth lab session

Changed lines 18-23 from:
    * Questions on Assignment 1 marking (briefly!)
    * Assignment 2 expectations and grading
    * Lead a discussion on the system evaluated in Ass2
    * Introduce the project
    * At end of formal lab, go over individual reports
to:
  • Questions on Assignment 1 marking (briefly!)
  • Assignment 2 expectations and grading
  • Lead a discussion on the system evaluated in Ass2
  • Introduce the project
  • At end of formal lab, go over individual reports
Changed lines 26-35 from:
    * students will likely have questions for you
    * tell students overall things you noticed when marking assignments
    *
          o what made write-ups excellent
          o what made write-ups weak
          o where marks were typically lost
    * while you should answer high-level questions about marking, defer picky questions (e.g. actual grade) until the end of the formal lab
    * I strongly suggest you ask students with complaints over their grading to give in their assignment with a note on it that says exactly where they feel the grading was wrong, and exactly why they should be regraded.
    * encourage groups to discuss their assignment 1 reports with you. This is the best way to give feedback!
to:
  • students will likely have questions for you
  • tell students overall things you noticed when marking assignments:
    • what made write-ups excellent
    • what made write-ups weak
    • where marks were typically lost
  • while you should answer high-level questions about marking, defer picky questions (e.g. actual grade) until the end of the formal lab
  • I strongly suggest you ask students with complaints over their grading to give in their assignment with a note on it that says exactly where they feel the grading was wrong, and exactly why they should be regraded.
  • encourage groups to discuss their assignment 1 reports with you. This is the best way to give feedback!
Changed lines 37-45 from:
    * give out grading sheet
    * go over main differences (organization and final section)
    * length should be long enough to tell the story! But probably no shorter than 8 pages, no longer than 20.
    * Stress:
      report should be oriented toward manager
      must be readable
      must show deep thought
    * Refer to lab 3ís notes for details of writeup
to:
  • give out grading sheet
  • go over main differences (organization and final section)
  • length should be long enough to tell the story! But probably no shorter than 8 pages, no longer than 20.
  • Stress:
    • report should be oriented toward manager
    • must be readable
    • must show deep thought
  • Refer to lab 3ís notes for details of writeup
Changed lines 48-53 from:
    * have people present their sample tasks, and why they thought they were good (or bad) ones. In particular, did they explore a common thing that users did in the system, or an arcane part of the system? Did the task really matter that much?
    * have people discuss their general observations and anecdotal evidence of what happened
    * try to elicit some problems of the system, at both the low level (particular examples) and the high level (ie how they generalize)
    * try to elicit design changes of the system that use the same technology
    * If you have time, have them design a new interface to the system.
to:
  • have people present their sample tasks, and why they thought they were good (or bad) ones. In particular, did they explore a common thing that users did in the system, or an arcane part of the system? Did the task really matter that much?
  • have people discuss their general observations and anecdotal evidence of what happened
  • try to elicit some problems of the system, at both the low level (particular examples) and the high level (ie how they generalize)
  • try to elicit design changes of the system that use the same technology
  • If you have time, have them design a new interface to the system.
Changed lines 56-65 from:
    * briefly introduce the project(see handout)
    * get them ready for first milestone, as below:
    * choose project area
      not to ambitious/large
      better to have excellent interface to small system
      implementable
    * start exploring many interface ideas with paper/pencil
    * present best ones to class as sketches/storyboard/pictive display
    * explain other aspects of first milestone
to:
  • briefly introduce the project(see handout)
  • get them ready for first milestone, as below:
  • choose project area:
    • not to ambitious/large
    • better to have excellent interface to small system implementable
  • start exploring many interface ideas with paper/pencil
  • present best ones to class as sketches/storyboard/pictive display
  • explain other aspects of first milestone
April 20, 2007, at 03:46 PM by 136.159.7.242 -
Added lines 1-67:
  CPSC  481

Foundations of HCI Saul Greenberg, Instructor Contents Back to lab materials for teaching assistants Notes for Teaching Assistants — Labs 4 & 5 Your fourth lab session

Labs will not be held this week. Instead,

    * Grade the assignments and get them back to me by the end of the week so I can check them
    * Be available for students who are doing Assignment 2.
    * Collect general comments on Assignment 1 (strengths/weaknesses) that you will tell students to follow/avoid for Assignment 2.

Your fifth lab session

Topics covered are:

    * Questions on Assignment 1 marking (briefly!)
    * Assignment 2 expectations and grading
    * Lead a discussion on the system evaluated in Ass2
    * Introduce the project
    * At end of formal lab, go over individual reports

Assignment 1 marking

    * students will likely have questions for you
    * tell students overall things you noticed when marking assignments
    *
          o what made write-ups excellent
          o what made write-ups weak
          o where marks were typically lost
    * while you should answer high-level questions about marking, defer picky questions (e.g. actual grade) until the end of the formal lab
    * I strongly suggest you ask students with complaints over their grading to give in their assignment with a note on it that says exactly where they feel the grading was wrong, and exactly why they should be regraded.
    * encourage groups to discuss their assignment 1 reports with you. This is the best way to give feedback!

Assignment 2 expectations/grading

    * give out grading sheet
    * go over main differences (organization and final section)
    * length should be long enough to tell the story! But probably no shorter than 8 pages, no longer than 20.
    * Stress:
      report should be oriented toward manager
      must be readable
      must show deep thought
    * Refer to lab 3ís notes for details of writeup

System discussion

    * have people present their sample tasks, and why they thought they were good (or bad) ones. In particular, did they explore a common thing that users did in the system, or an arcane part of the system? Did the task really matter that much?
    * have people discuss their general observations and anecdotal evidence of what happened
    * try to elicit some problems of the system, at both the low level (particular examples) and the high level (ie how they generalize)
    * try to elicit design changes of the system that use the same technology
    * If you have time, have them design a new interface to the system.

Assignment 3 project

    * briefly introduce the project(see handout)
    * get them ready for first milestone, as below:
    * choose project area
      not to ambitious/large
      better to have excellent interface to small system
      implementable
    * start exploring many interface ideas with paper/pencil
    * present best ones to class as sketches/storyboard/pictive display
    * explain other aspects of first milestone

Last updated April 1997, by Saul Greenberg