 Class discussion, participation

 HWs/Projects: open-ended
 Group project
 Student presentations
THE PROJECT
 Team-based
 Topic: Intelligence Analysis
 Information Visualization

 Problem seeking / problem solving

 Understand users & problem, prototype, interim
review presentation, evaluate, revise, final
presentation
1. What is it?
2. Who cares?
3. Why is it hard?
4. What will I learn?
Human-Computer Interaction
 Human-Computer Interaction

“Human-computer interaction is a
discipline concerned with the design,
evaluation and implementation of
interactive computing systems for
human use, and with the study of major
phenomena surrounding them."
-ACM SIGCHI
An example:

HomeFinder
 Usability
 People are trying to accomplish their tasks in life.
(system independent)

task
person

system

 Introduce a system,
User Interface should maximize their ability.
 Reqs Analysis

Evaluate Design

Develop

A process for HCI production to ensure usability goals are met

 Reqs Analysis

Evaluate Design

Develop

many iterations
Everyone, because:
1. Everything is a User Interface
Everyone, because:
1. Everything is a User Interface

2. The User Interface is Everything

 Human error: Who’s fault is it?
 People (users) are all different
 People are unpredictable
 Design skill isn’t enough
 Evaluation with users is required
 Designer’s pride
 New ways to think, break out of the box
 People (users) are all different
 People are unpredictable
 Design skill isn’t enough
 Evaluation with users is required
 Designer’s pride
 New ways to think, break out of the box
 Programmers stink at Usability
 Programmers stink at Usability

 don’t think like ‘normal’ people

 know the software internals, technology first
 enjoy systems more than people

 arrogant (my software!)

 • Task analysis
• Ethnography

• Usability studies
Reqs Analysis
• Controlled experiments

Evaluate Design

• Activity design
• Information design
• Interaction design
Develop
• GUI programming
• Widgets, graphics, animation
• C#
 ANALYZE
analysis of Problem scenarios claims about
stakeholders, current
field studies practice
Scenario-Based Design

DESIGN
metaphors, Activity iterative
information scenarios analysis of
technology, usability
HCI theory, claims and
guidelines Information scenarios re-design

Interaction scenarios

PROTOTYPE & EVALUATE

summative Usability specifications formative
evaluation evaluation
Get angry! (about crummy user interfaces)

Mental shift:
From system-centered design
to user-centered design

Design: Break out of the box

Think: HCI is science and engineering

 Read: HANDOUT 1
 Project step 1: make teams of 4 students
 Start to review the Activity 1 (FOR LABORATORY SUBJECT)