90 likes | 207 Views
CS 575 Spring 2012. Lecture 7 2012-05-19 Bapa Rao. Agenda for Today. Review of previous meeting Heuristic Testing Student Presentations Assignment for the coming week Presentation: Direct Manipulation [time permitting] Sutherland’s Sketchpad video [time permitting] Alan Kaye video.
E N D
CS 575Spring 2012 Lecture 7 2012-05-19 Bapa Rao
Agenda for Today • Review of previous meeting • Heuristic Testing Student Presentations • Assignment for the coming week • Presentation: Direct Manipulation • [time permitting] Sutherland’s Sketchpad video • [time permitting] Alan Kaye video
Review of previous meeting • Paper prototypes • Heuristic Evaluation Presentation • Nielsen’s methodology for heuristic evaluation • Usability heuristics • Severity ratings • Assignment
Assignment from the previous week • Self-evaluation of your work from the previous week (storyboard / paper prototype) • Start a journal on your personal page documenting the work you have personally done, and your personal thoughts & ideas • Back-fill with work you have already done • Include self-evaluation • For every activity done by your team, you should post documentation of your personal contribution and self-evaluation • Not everyone has to do every task, but everyone has to do significant tasks in the team activity • This will, in part, determine your personal final grade • I can’t grade you if I don’t know what you have done • I will provide evaluation templates as appropriate
Assignment from the previous week (contd) • Read the papers on Heuristic Evaluation posted on the wiki. • Complete heuristic evaluation of your paper prototype and post your evaluation report on the team wiki page. • Be sure to include your personal (course-related) activity and contribution on your personal wiki page • Do a debriefing and make needed design changes • Post a self-evaluation of your heuristic evaluation. • Put an implementation proposal and plan together • See the sample on wiki • You have 2 weeks to build the prototype so limit your scope accordingly starting May 18th • + 1 week for testing • Identify platform • Decide what backend functions you will “fake” and how • Should be demo-able in class on June 9th 2012 • No coding till you finish heuristic evaluation step
Assignment for the coming week: 1 • Bring yourself and your team up to date on the assignments so far • You cannot do any coding till you are up to date and I give the OK • Email me if you have any questions
Assignment for the coming week: 2 • New Assignment: Use Nielsen’s heuristic evaluation method and criteria to do an evaluation of the www.csula.edu website. • Due 2012-05-26 • Refer to the Resources for examples and guidelines. • For each team, upload the following: • each team member does an independent evaluation • Construct a template and fill it out • Scores, Verbal descriptions • Consolidate the evaluations of all team members • Average scores, consolidated verbal descriptions • Debriefing results: • Specific ideas for improving the design of the site. • Submit and Present in class in 2012-05-26 meeting • Consolidated verbal critique of site, average scores, debriefing results
(From Klemmer’s HCI Course at Stanford) Direct manipulation