CS%203724:%20Introduction%20to%20Human%20Computer%20Interaction

1
CS 3724 Introduction to Human Computer
Interaction
Chris NorthJason LeeSzu-Chia Lu
2
WELCOME TO THE NEXT LEVEL
3
Toto, I dont think were in 2604 anymore.

• Class discussion, participation
• HWs/Projects open-ended
• Group project
• Student presentations

4
Course Overview

• Lectures and activities
• Individual homework assignments
• Readings
• Tests
• Hall of Fame / Hall of Shame
• Design project

5
Textbook

• Mary Beth Rosson and John M. Carroll, Usability
  Engineering Scenario-Based Development of
  HCI(required)
• Visual C .NET,Step-by-Step by SharpJaggeror
  Core Ref by Williams(optional)

6
The Project

• Team-based
• Choose topic
• Information vizualization
• Problem seeking / problem solving
• Find users problem, prototype, interim review
  presentation, evaluate, revise, final
  presentation
• C language?

7
Grading Breakdown

• Presentation (hall of fame/shame) 5
• homework (4 x 5) 20
• Mid term 10
• Design project 50
• Team formation 0
• Requirements 10
• Formative analysis design 20
• Interim presentation 5
• Prototype implementation 10
• Summative Evaluation 20
• Final presentation 5
• Final implementation 30
• Final 15

8
Policies

• Homework due in class Thurs. Late 0
• No early exams, make up by advance arrangement
• Signed request with rationale
• Reminder of VT Honor Code
• Specifically, tests and homeworks are individual
• Students with special needs see me ASAP

9
Adminstrivia

• Force-adds and prerequisite forms
• CRN is 91680 / 91681
• Prerequisite is CS 2604, REQUIRED
• Everyone must complete the forms TODAY
• Must attend today
• Add decisions by next meeting
• Web page (courses.cs.vt.edu/cs3724) contains
  syllabus, lecture outlines, assignments, and
  related materials

10
HCI ???

1. What is it?
2. Who cares?
3. Why is it hard?
4. How does it work?
5. What will I learn?

11
1. What is HCI?
12
1. What is HCI?

• Human-Computer Interaction

13
1. What is HCI?

• Human-Computer Interaction

• Requirements analysis
• Design
• Development
• Evaluation
• of user interfaces for computer systems

14
Huh?

• An example
• HomeFinder

15
Apartments.com
16
HitList
17
HomeFinder
18
The Goal of HCI

• Usability
• People are trying to accomplish their tasks in
  life. (system independent)
• Introduce a system,User Interface should
  maximize their ability.

task
person
system
19
2. Who Cares?

• Everyone, because
• Everything is a User Interface

20
Doors
21
More Doors
22
Communication Channels

• System to human
• Human to system

system, world
23
2. Who Cares?

• Everyone, because
• Everything is a User Interface
• The User Interface is Everything

24
Florida Cares!

• Human error Whos fault is it?

25
3. Why is it so hard?
26
Usability is hard

• People (users) are all different
• People are unpredictable
• Design skill isnt enough
• Evaluation with users is required
• Designers pride
• New ways to think, break out of the box

27
Usability is hard

• People (users) are all different
• People are unpredictable
• Design skill isnt enough
• Evaluation with users is required
• Designers pride
• New ways to think, break out of the box
• Programmers stink at Usability

28
Usability is hard

• Programmers stink at Usability
• dont think like normal people
• know the software internals, technology first
• enjoy systems more than people
• arrogant (my software!)

29
4. How does it work?
Usability Engineering
Reqs Analysis
Design
Evaluate
Develop
30
4. How does it work?
Usability Engineering
Reqs Analysis
Design
Evaluate
Develop
many iterations
31
5. What will I learn?

• Task analysis
• Ethnography

Reqs Analysis

• Usability studies
• Controlled experiments

Design
Evaluate

• Activity design
• Information design
• Interaction design

Develop

• GUI programming
• Widgets, graphics, animation
• C

32
A Method Scenario-Based Usability Engineering

• Stories of people and their activities
• Typical elements of the story are
• A setting
• One or more actors or agents
• An orienting or motivating goal or objective
• Mental activity, plans or evaluation of behavior
• A storyline sequenced by actions and events
• Emphasis on use, i.e., peoples needs,
  expectations, actions, and reactions

33
ANALYZE
claims about current practice
analysis of stakeholders, field studies
Problem scenarios
Scenario-Based Design
DESIGN
Activity scenarios
iterative analysis of usability claims
and re-design
metaphors, information technology, HCI
theory, guidelines
Information scenarios
Interaction scenarios
PROTOTYPE EVALUATE
summative evaluation
formative evaluation
Usability specifications
34
Grander Goals?

• Get angry!
• Mental shift
• From system-centered design to user-centered
  design
• Break out of the box

35
Goals of Course (official version)

• Survey of human-computer interaction concepts,
  theory, and practice.
• Interdisciplinary underpinnings.
• Informed and critical evaluation of
  computer-based technology.
• User-oriented perspective, rather than
  system-oriented, with two thrusts human
  (cognitive, social) and technological
  (input/output, interactions styles, devices).
• Design guidelines, evaluation methods,
  participatory design, communication between users
  and system developers.

36
Goals of Course (Alternate version)

• Learn that HCI topic is both wide and deep.
• HCI is essentially about design and design
  involves asking good questions
• Convince some of you that HCI is phat / cool
• Convince the rest of you that HCI expertise is
  needed in most computer projects
• HCI is science and engineering

37
Before you Leave

• Prerequisites form!