HCI Lecture12
HCI Lecture12
1
Introduction to HCI
Lecture 1
2
Learning Outcomes:
a. Define HCI and understand its goals
b. Identify the fundamental concepts of an interactive
system design
c. Understand the capabilities and limitations of
human that affect their ability to use computer
systems
d. Understand the capabilities and limitations of the
computer and their effect on the interaction
e. Describe various models of interaction
3
Outline
• Introduction
• What is HCI?
– The HCI Challenge
– HCI is Not about
– HCI is about
• The goals of HCI
• What is Usability?
• Why is usability important?
– Why HCI is Important in the Context of WWW?
– It is not Simple to Make Good User Interfaces
• Examples of good and bad design
4
Introduction
5
Introduction..(cont.)
6
What is HCI?
• Human-computer interaction (HCI): “is a
discipline concerned with the design,
evaluation and implementation of interactive
systems for human use and with study of
major phenomena surrounding them.”
(ACM SIGCHI, 1992, p. 6)
What is HCI?
• HCI (human-computer interaction) is the
study of interaction between people (users)
and computers.
8
What ..(cont.)
HCI consists of three parts:
• Human: could be an individual user or a group
of users.
• Computer: could be any technology ranging
from the general desktop computer to a large
scale computer system.
• Interaction: any direct or indirect
communication between a human and
computer.
9
What ..(cont.)
• HCI concentrates on the study of human
factors
11
HCI is Not about
• Making the interface look pretty
12
HCI is about
• Understanding the users
• Understanding users tasks
• Understanding the surrounding environment
• GUI requirements gathering and analysis
• Design prototype
• Evaluate the system
13
Brief History of HCI
Human Computer Interaction(HCI) is an area of
research and practice that emerged in the late
1970s and early 1980s, initially as an area in
Computer Science.
HCI has expanded rapidly and steadily for three
decades, attracting professionals from many
other disciplines and incorporating diverse
concepts and approaches.
14
Brief History of HCI
1970s- The rise of the Personal Computer
The broad project of cognitive science, which
incorporated cognitive psychology, artificial
intelligence, linguistics, cognitive
anthropology, and the philosophy of mind,
had formed at the end of the 1970s.
15
Brief History of HCI
1980s- Graphical User Interface (GUI).
Graphical User Interface (GUI) is the interface
that is designed for the easier understanding of
the users of the computers. Before GUI, there
was a command prompt by which command
was given to the computers. GUI started the
graphical interface which is easy to use,
understand, visualize, and it improved the
working environment.
16
Brief History of HCI
1990s- The Internet and Collaborative works.
The Internet started journey in 1990s. So,
communications among people became easier.
In the consequence of this, many new
technologies arrived for better communication.
17
Brief History of HCI
2000s- Mobile Computing and Beyond.
Mobile phones, PDA (Personal Development
Assistance), and Smart Phones are ruling the
present world. They offer a wide range of
services to the people such as sms, mms,
multimedia, games, email, internet, chatting,
video conference, GPS etc.
18
Brief History of HCI
Now a days the HCI is used in the area of
Cognitive Science. With the help of the
Internet, medical facilities can be provided
remotely. Different interactive interfaces are
designed those can be used for the cognitive
rehabilitations.
19
The goals of HCI
• The goal of HCI “is to develop or improve the
safety, utility, effectiveness, efficiency and
usability of system that include computers.”
(Interacting with computers, 1989, p3)
20
The goals of HCI
• The goals of HCI are to produce usable and safe
systems, as well as functional systems. In order to
fulfill that, developers must attempt to:
– Understand how people use technology
– Building suitable systems
– Achieve efficient, effective, and safe interaction
– Put people first
21
What is Usability?
• A usable system is:
– easy to use
– easy to learn
– easy to remember how to use
– effective to use
– efficient to use
– safe to use
– enjoyable to use
22
Why is usability important?
A Good user-interface can:
1. Earn a company billions.
2. Increase users loyalty.
3. Increase users trust.
4. Makes users happy : )
23
Why ..(cont.)
A Bad user-interface can:
1. be annoying, embarrassing, frustrating, and
even deadly.
2. Increase mistakes in data entry and system
operation.
3. Makes functions become completely
inaccessible.
4. System failure because of user rejection.
24
Why HCI is Important in the Context
of WWW?
• Competition is very close (just another link…)
• Comparison is easily possible (example – Online-
Shop)
• Users who can’t find the product in the shop can not
buy it
• Users who are not able to fill in correctly the order
form are not going to buy
25
It is not Simple to Make Good
User Interfaces
Basic misconceptions:
• If I (the developer) can use it, everyone can use it
26
Examples of good and bad design
27
Examples ..(cont.)
28
Examples ..(cont.)
29
Examples ..(cont.)
30
Examples ..(cont.)
31
Examples ..(cont.)
32
Examples ..(cont.)
33
Introduction to HCI
Lecture 2
34
Outline
• Disciplines Contributing to Human-Computer
Interaction
• Is HCI really Important?
– A real life example
– The importance of HCI
– Reasons for Failures
• Traditional approach
• User-centred design
• Examples of good and bad design
35
Disciplines Contributing to Human-
Computer Interaction
36
Is HCI really Important?
37
A real life example
Example about: Health and safety concerns
If the video doesn’t record a TV
program because we pressed
the wrong button, we are likely
to feel angry.
38
A real ..(cont.)
www.metu.edu.tr/~acengiz/biltek_sunu
m 39
Time to Think!
• What is the percentage of software
development projects that fails?
• A. 20%
• B. 35%
• C. 55%
• D. 85%
40
• Fact
- Fletcher Buckley “: 85% of Software projects are
either late or delivered without satisfying the
specification.”
But WHY?
41
Reasons for Failures
Projects in general fail for various reasons:
43
Example of traditional approach
Requirements
specification
Analysis
Design
Implementation
Operation and
maintenance
44
Introduction to User Centered
approach
This approach normally involves a number of key
activities throughout the development of the
software including:
• Involving users
• Obtaining their feedback on the design
• Providing prototypes for system evaluation and re-
design in light of user feedback and comments.
45
User Centered approach
• Real users involved at each step of the process
46
The life cycle for interactive systems
cannot assume a linear
user needs Requirements sequence of activities
specification
as in the waterfall model
Analysis
Design
Implementation
Operation and
maintenance
47
User Centered Development
1. Data Collection
2. Data Analysis
3. Prototyping
4. Design
5. Evaluation
48
1. Data Collection
• Data recording
– Using media
• Interviews
– Stakeholder interviews
– Subject Matter Expert interviews
– User and customer interviews
• Questionnaires
– Surveys, product reviews
• Literature review
– Studying existing systems
49
2. Data Analysis
• Requirement analysis
– Formal specifications of the system
• User analysis
– Identifying and understanding the user
• Task analysis
– Steps user take to accomplish this task
• Functional analysis
– Functions that system perform to help the users
carry out their task
50
3. Prototyping
Advantages of Prototyping:
• Users are actively involved in the development
• It provides a better system to users
• The users get a better understanding of the system
being developed.
• Errors can be detected much earlier
• Quicker user feedback is available leading to better
solutions
51
4. Design
• Goals
– Achieving goals
• Users and systems
– Understanding the raw materials: computer and
human
• Limitations
– Accepting limitations of humans and of design
52
5. Evaluation
• Testing the usability, functionality and
acceptability of an interactive system
• Expert evaluation
– Evaluation by Subject Matter Experts
• User evaluation
– Evaluation by user or customer
53
Designer vs. Users
Making a photocopy
54
Designer vs. Users
55
Examples ..(cont.)
56
Examples ..(cont.)
57
Examples ..(cont.)
58
Examples ..(cont.)
59
Examples ..(cont.)
60
Examples ..(cont.)
61
Examples ..(cont.)
62
Examples ..(cont.)
63
Examples ..(cont.)
64
Examples ..(cont.)
65
References
• http://www.cs.bham.ac.uk/~rxb/Teaching/HCI%20II/intro.html
• http://www.baddesigns.com/examples.html
• http://www.goodexperience.com/tib/archives/webtech/
• http://pages.cpsc.ucalgary.ca/~saul/hci_topics/topics/psych.html
• http://homepage.mac.com/bradster/iarchitect/
• www.useit.com
• http://faculty.ed.umuc.edu/~meinkej/inss690/wilson.htm
66