CS 6750 Human Computer Interaction

1
CS 6750Human Computer Interaction
Spring 2003

• Jeff Pierce
• jpierce_at_cc.gatech.edu

2
Agenda

• Introductions
• Course Information
• A little about HCI
• Project Information

3
Introductions Jeff Pierce

• Carnegie Mellon 01, CoC GVU 02
• Human-Computer Interaction (with a CS flavor)
• Cool projects
• 3D Interaction
• DisneyQuest
• Alice
• Sensing Techniques
• for Mobile Devices

4
Introductions Bob Amar

• Your illustrious TA
• CS PhD Student
• Office Hours
• TR 330-430
• CCB Commons
• bob_at_cc

5
Introductions - You

• Name, Degree, Research Focus, your N
• What youd like to get out of the class
• Previous HCI experience
• An interesting fact about yourself
• Pictures! (later)

6
Course Information

• Books
• Human-Computer Interaction (2nd ed.), by Alan
  Dix, Janet Finlay, Gregory Abowd, and Russell
  Beale. Prentice Hall, 1998.
• The Design of Everyday Things, by Donald Norman.
  Currency/Doubleday, 1990.
• Web
• http//www.cc.gatech.edu/classes/AY2003/cs6750_spr
  ing/
• Syllabus
• Assignments
• Co-web (swiki)
• HCI resources

7
Course Information

• Grading
• Mid-term final exams (32)
• Group project, 4 parts (40)
• More to come...
• Homeworks (21)
• One week to do, 3 of them
• Short Homeworks (4)
• One day to do, 4 of them
• Participation (3)
• Class involvement

8
Course Information

• Resources
• Previous courses, courses elsewhere
• Content, lectures, projects,
• Books
• Web sites
• Go further
• Move beyond lectures book
• Further courses
• Step into research

9
Course Overview

• Human abilities
• Evaluation (without users)
• Evaluation (with users)
• Design
• Dialog interaction
• Special topics
• CSCW, InfoVis, Ubicomp, 3D Interaction, Adaptive
  Interfaces

10
Course Aims

• 1. Consciousness raising
• Make you aware of the issues
• 2. Design critic
• Question bad design
• 3. Improve design evaluation skills
• Go forth and do good work!

11
And were off!

• HCI what is it?
• Can you define / describe it?

12
HCI

• What happens when a human and a computer get
  together to perform a task
• task - write document, calculate budget, solve
  equation, learn about Bosnia, drive home,...
• Yes, thats a little simplistic.
• Key points are that user has to
• Express task (execution)
• Interpret results (evaluation)
• Note not just desktop computers!

13
Why should we care?

• Computers (in one way or another) now affect
  every person in society
• Increasing utilize computers at work and home
• Want to increase satisfaction, utility, and
  safety
• Product success may depend on ease of use, not
  necessarily power
• Macintosh vs. Windows

14
Goals of HCI

• Allow users to carry out tasks
• Safely
• Effectively
• Efficiently
• Enjoyably

15
Usability

• Important issue
• Combination of
• Ease of learning
• High speed of user task performance
• Low user error rate
• Subjective user satisfaction
• User retention over time

16
How do we improve interfaces?

• Educate software professionals
• Draw upon accumulating body of knowledge
  regarding H-C interface design
• Integrate UI design methods techniques into
  standard software development methodologies now
  in place

17
UI Design / Develop Process

• User-Centered Design
• Analyze users goals tasks
• Create design alternatives
• Evaluate options
• Implement prototype
• Test
• Refine
• IMPLEMENT

18
Know Thy Users!

• Physical cognitive abilities ( special needs)
• Personality culture
• Knowledge skills
• Motivation
• Two Fatal Mistakes
• Assume all users are alike
• Assume all users are like the designer

You Are Here
19
Design Evaluation

• Both subjective and objective metrics
• Some things we can measure
• Time to learn
• Speed of performance
• Rate of errors by user
• Retention over time
• Subjective satisfaction

20

• And now more about that project thing.

21
Project Structure

• Design and evaluate an interface
• 0 - Team formation topic choice
• 1 - Understand the problem
• 2 - Design alternatives
• 3 - Prototype evaluation plan
• 4 - Evaluation
• Main 4 parts worth 10 each

22
Project Details

• Part 0 - Topic definition 1/16
• Identify team topic, create web notebook
• Part 1 - Understanding the problem 2/6
• Describe tasks, users, environment, social
  context
• What are implications for design?

23
Project Details

• Part 2 - Design alternatives 2/27
• Storyboards, mock-ups for multiple different
  designs
• Explain decisions
• Part 3 - System prototype eval plan - 3/27
• Semi-working interface functionality
• Plan for conducting evaluation

24
Project Details

• Part 4 Evaluation 4/24
• Conduct evaluation with example users
• Characterize whats working and whats not

25
Project Groups

• 4 people
• You decide
• Diverse is best!
• Consider schedules
• Cool name
• Some time available Thursday for recruiting
  members

26
Project Presentations

• Informal poster session
• Feedback on ideas, both class periods
• Feb. 25
• Other students and expert gallery
• Formal project presentation
• Final week of classes
• 10-15 minute summary

27
Project Topics

• Set of possibilities
• Max of 2 teams per topic
• First-come, first-served
• By next Thursday
• Set up web notebook
• Real client

28
Previous Project Topics

• Mobile/handheld (cars, tour guides, etc.)
• Wedding planner
• GIS
• Calendar agent (speech)
• Audio / Web sites
• Domain that you know well
• More on Class Co-Web
• http//swiki.cc.gatech.edu8080/cs6750

29
What Makes a Good Project

• Access to domain experts users
• Real clients
• Interesting human issues
• Rich domain for design

30
Whats Next

• History of HCI
• Start reading (4.1 4.2)