UNIT 1:INTRODUCTION TO HCI

Topic 1

1. Definition of HCI: Human-Computer Interaction (HCI) is the interdisciplinary field that

focuses on the design, implementation, and evaluation of interactive computing systems for
human use, and the study of the interactions between people (users) and computers.

Key Aspects:

 "Human": Understanding users—their needs, behaviors, limitations, and expectations.

 "Computer": Encompasses all forms of digital technology—desktops, mobile devices, kiosks,
smart systems, etc.
 "Interaction": The communication between the user and the system through interfaces
(e.g., visual, voice, gestures

2. Core Disciplines Involved

HCI is interdisciplinary and draws from:

 Computer Science (interface development, systems)

 Psychology (cognition, perception, user behavior)
 Design (visual design, user experience)
 Human Factors/Ergonomics (efficiency, safety)

3. Key Principles

 Usability: How easy and efficient it is for users to achieve their goals.
 Affordance: Visual cues that suggest how an object should be used.
 Feedback: System response to user actions.
 Consistency: Uniformity in design and behavior.
 Learnability: How easy it is for users to learn a system.
 Error Prevention and Recovery: Designing to avoid or easily fix mistakes.

4. Interaction Styles

 Command-line interfaces (CLI)

 Graphical user interfaces (GUI)
  Touch interfaces
 Voice interfaces
 Virtual/Augmented Reality

5. User-Centered Design (UCD)

An iterative process that puts the user at the center of each design phase:

1. Understand users and their context.

2. Define requirements.
3. Develop prototypes.
4. Evaluate and refine.

6. Evaluation Methods

 Heuristic evaluation
 Usability testing
 Surveys and questionnaires
 A/B testing
 Eye-tracking and analytics

7. Cognitive Models

Models that describe how users think and process information, e.g.:

 GOMS Model (Goals, Operators, Methods, and Selection rules)

 KLM (Keystroke-Level Model)

8. Accessibility

Designing for users with diverse abilities and disabilities to ensure inclusive experiences.

9. Ethics in HCI

Concerns include user privacy, data protection, persuasive technologies, and dark patterns.

Topic 2:
History of Human-Computer Interaction (HCI)

The history of HCI reflects how computing evolved from technical tools to user-centered systems

History of Human-Computer Interaction (HCI)

The history of HCI reflects how computing evolved from technical tools to user-centered
systems. Here's a timeline of key developments:

1940s–1950s: Foundations of Computing

 Early computers like ENIAC were operated using punch cards and switches.
 Interfaces were purely mechanical and accessible only to trained engineers.
 ENIAC full form: Electronic Numerical Integrator and Computer (A 30 Ton
computer!!)
 Speed: Could perform 5,000 additions per second — extremely fast at the time.
 There was no keyboard, screen, or mouse.
 Users programmed ENIAC by manually setting switches and plugging cables—a
process that was complex and time-consuming.


1960s: Interactive Computing Emerges

 Douglas Engelbart invented the computer mouse and demonstrated interactive

computing in his 1968 "Mother of All Demos."
 Ivan Sutherland’s Sketchpad (1963) introduced graphical interaction—precursor to
GUIs.
 Concept of “man-machine interaction” begins to emerge.

1970s: Command-Line Interfaces (CLI)

 Users interacted through text-based commands (e.g., UNIX terminal).

 Still required technical expertise; interfaces were not user-friendly for general users.

1980s: Birth of Modern HCI

 Xerox PARC introduced the Graphical User Interface (GUI): windows, icons,
menus, and mouse (WIMP model).
 Apple Lisa and Macintosh popularized GUIs.
 HCI becomes a distinct academic field, combining computer science, cognitive
psychology, and design.
 ACM SIGCHI (Special Interest Group on Computer–Human Interaction) was
established in 1982.
1990s: Usability and User-Centered Design

 Emphasis on usability, accessibility, and task efficiency.

 Rise of web interfaces, which brought design and HCI to a broader audience.
 Concepts like user personas, user testing, and iterative design gained traction.

2000s: Mobile and Ubiquitous Computing

 Introduction of smartphones, touch interfaces, and gesture-based input.

 HCI extended to everyday devices—ubiquitous computing.

||||||Good to know::Ubiquitous Computing (Ubicomp)

Ubiquitous computing—also known as pervasive computing—refers to a computing model where

technology is seamlessly integrated into the environment and becomes invisible to users through
everyday objects and activities.

Key Characteristics:

  Invisibility: Technology blends into the background (not the center of attention).
  Context-awareness: Devices adapt based on location, activity, or user needs.
  Networked: Devices communicate with each other to provide a smooth experience.
  Embedded: Computing is built into physical objects (e.g., smart appliances,
wearables).
  Proactive: Systems may anticipate user needs and act without explicit commands.

Application Description
Lights, thermostats, and security systems that auto-adjust based on
Smart Homes
behavior.
Wearable
Smartwatches, fitness trackers monitoring health and activity.
Tech
Smart Cities Traffic lights, sensors, and public systems optimizing urban life.
Healthcare Remote monitoring of patients via sensors and smart devices.
Retail Stores using RFID tags, digital signage, and smart shelves.||||||

”””

 Human-centered design (HCD) and experience design (UX) grew in importance.

2010s–Present: Beyond the Screen

 HCI now includes voice assistants (e.g., Alexa, Siri), AR/VR, AI-driven systems,
and brain-computer interfaces.
 Focus on emotion-aware systems, ethical AI, and inclusive design.
 Emergence of natural user interfaces (NUIs) and multi-modal interaction.

Natural User Interfaces (NUIs)

Natural User Interfaces (NUIs) are interfaces that allow users to interact with computers in ways
that feel natural and intuitive, often mimicking real-world behaviors, without needing complex
commands or abstract controls.

Examples of Natural User Interfaces:

Interface Type Example

Touch Pinch to zoom on smartphones or tablets

Gesture Swiping or waving to control a smart TV

Voice Speaking commands to Alexa, Siri, or Google Assistant

Facial Recognition Unlocking a phone with Face ID

Motion Tracking Playing games with Kinect or VR systems like Oculus

Eye Tracking Navigating a screen or interface using eye movement

Topic 3

Human Factors in Human-Computer Interaction (HCI)

🧠 Human Factors in Human-Computer Interaction (HCI) –

📘 Definition:

Human Factors in HCI refer to the study of how humans interact with computers, with a
focus on designing systems that match human physical, cognitive, and emotional abilities.
✅ 10 Key Points

1. User-Centered Design:

User-centered design (UCD) is a development approach that focuses on the needs,

preferences, and limitations of users at every stage of the design process. It involves
user research, testing, and feedback to ensure the product is intuitive and efficient.
The goal is to create systems that are easy to learn and satisfying to use. This principle
is foundational to all HCI design.

2. Physical Ergonomics

Physical ergonomics deals with designing hardware and interfaces to fit the user’s
body and capabilities. It considers hand size, posture, screen angles, and button
placement. A well-ergonomic design reduces fatigue and physical strain. For
example, mobile devices should be operable with one hand for many users.

3. Cognitive Load

Cognitive load is the amount of mental effort required to use a system. Interfaces should
minimize this by presenting information in manageable chunks and using familiar terms and
visuals. Overloading users with too many choices or complex processes can lead to
frustration and errors. Designers aim to keep interactions simple and logical.

4. Perception and Sensory Limits

Human perception varies—some users may have visual, auditory, or tactile limitations.
Interfaces should use high-contrast text, readable fonts, and clear audio cues to support
different sensory abilities. Design should also avoid relying solely on one sense (e.g., not just
color to indicate status). Inclusive perception improves usability for all.

5. Consistency and Predictability

Users rely on consistent design patterns to predict how a system will behave. Consistent
navigation, terminology, and iconography help users learn systems faster and reduce errors.
For example, a save icon should look and work the same across screens. Predictability builds
user trust and efficiency.

6. Error Prevention and Recovery

Good design prevents user errors and provides clear ways to recover from them. Examples
include disabling irrelevant options, showing confirmation dialogs, or offering undo buttons.
If errors do occur, the system should display helpful messages—not just "error 404." The
goal is to reduce frustration and improve control.

7. Attention and Focus

Humans have limited attention, especially when multitasking. Interfaces should guide the
user's focus using layout, color, and motion to highlight important elements. Unnecessary
animations, pop-ups, or clutter should be avoided. Keeping screens clean and task-focused
improves performance and reduces distraction.

8. Adaptability and Accessibility

Interfaces must work for users with different abilities, devices, and environments. This
includes screen readers for the blind, adjustable font sizes, and alternative input methods.
Systems should also adapt to various conditions like low light or noisy surroundings.
Accessibility ensures fairness and legal compliance.

9. Feedback and Responsiveness

Feedback tells users their actions were received and understood by the system. This can be
visual (loading spinner), auditory (click sound), or haptic (vibration). Without feedback, users
feel uncertain or think the system is broken. Fast, meaningful feedback improves user
confidence and experience.

10. Safety and Comfort

Systems should minimize the risk of physical harm and mental stress, especially in high-
stakes environments like healthcare or aviation. Interfaces must be intuitive and prevent
dangerous mistakes. Additionally, repetitive tasks should not cause physical discomfort (e.g.,
strain from mouse use). Safety is both a design and ethical priority.

Topic 4

Cognitive Psychology Principles:

In HCI, cognitive psychology helps designers create systems and interfaces that align with the way
users naturally think and behave, making technology easier to use, more intuitive, and more
effective.
Here are 10 key principles of cognitive psychology that are applied in Human-Computer
Interaction .

1. Mental Models

 Users develop mental representations of how systems work based on their

experiences. Aligning interface designs with these models makes systems easier to
understand and navigate.

2. Cognitive Load

 The amount of mental effort required to perform tasks. Minimizing cognitive load by
simplifying information presentation and interface design helps users focus on key
tasks without feeling overwhelmed.

3. Attention

 Attention is the process of focusing cognitive resources on specific stimuli while

ignoring others. Interface designs should guide users’ attention to important elements
to avoid distractions and improve task performance.

4. Memory

 Memory refers to how information is encoded, stored, and retrieved. To support

memory, designs should provide visual cues, limit the amount of information
presented at once, and allow easy access to previously used data.

5. Decision Making

 Decision-making involves evaluating alternatives and selecting a course of action.

HCI designs should simplify the decision-making process by presenting clear choices,
minimizing options, and providing helpful feedback.

6. Chunking

 Chunking is the process of grouping information into smaller, manageable units. In

HCI, chunking helps users process large amounts of information by organizing data
into digestible sections (e.g., grouping related menu options or information).

7. Perception

 Perception is the way users interpret and make sense of sensory input. Interfaces
should account for how users visually interpret elements, such as buttons, icons, and
colors, to ensure clarity and reduce confusion.

8. Pattern Recognition
  Humans tend to recognize familiar patterns based on past experiences. HCI systems
can use familiar design patterns (like conventional button placements or navigation
systems) to make interfaces more intuitive and easier to use.

9. Feedback

 Feedback provides users with information about the outcomes of their actions. In
HCI, immediate and clear feedback reassures users that their actions have been
recognized and informs them about the results of their behavior.

10. Error Recovery

 Error recovery involves the ability to recover from mistakes quickly. Systems should
provide users with clear error messages, guide them through corrective actions, and
minimize the likelihood of repeated errors by supporting intuitive interaction paths.

By understanding and applying these principles, designers can create more effective, user-
friendly systems that align with the cognitive processes of users, improving usability and user
satisfaction.

_______________________________________________________________

Topic 5: User-Centered Design (UCD) is a design approach that focuses on the needs,
preferences, and limitations of end users throughout the design process. UCD principles aim
to create interfaces and systems that are intuitive, effective, and accessible by involving users
at every stage of development. Here are the key User-Centered Design principles in HCI:

1. Understand Users and Their Context

 Principle: Design should be based on an understanding of the users, their tasks, and their
environment.
 Application: Conduct user research through methods like interviews, surveys, and
observation to understand user needs, goals, and behaviors. The context of use (physical,
social, and cultural) must also be considered to ensure the design is relevant.

2. Involve Users Throughout the Design Process

 Principle: Users should be involved in every stage of the design process, from planning
through testing.
 Application: Engage users early in the design process through feedback, usability testing,
and iterative development. This helps ensure that the design aligns with user expectations
and needs.

3. Focus on Users' Goals and Tasks

 Principle: The design should support users in achieving their goals efficiently and effectively.
  Application: Identify the primary tasks users need to accomplish and prioritize these tasks in
the design. Tools and interactions should be designed to facilitate these tasks with minimal
effort.

4. Iterative Design

 Principle: Design should be an iterative process with continuous refinement based on user
feedback.
 Application: Create prototypes early and test them with real users. Use feedback to identify
areas for improvement, and refine the design iteratively. This ensures the final product
better aligns with user needs and preferences.

5. Design for Accessibility

 Principle: Ensure the system is accessible to a wide range of users, including those with
disabilities.
 Application: Design interfaces that accommodate users with varying abilities. This includes
considering visual, auditory, and motor impairments. For example, providing alternative text
for images, keyboard navigation, and voice commands.

6. Simplify and Prioritize

 Principle: Keep the design simple and focus on the most important features and
functionality.
 Application: Avoid unnecessary complexity by prioritizing key tasks and making the interface
easy to navigate. Streamline interactions, reduce the number of steps required to perform
tasks, and eliminate irrelevant features.

7. Provide Feedback and Affordances

 Principle: Ensure users receive timely and clear feedback on their actions, and provide
intuitive cues on how to interact with the system.
 Application: Interface elements should suggest their use (e.g., buttons look clickable).
Provide feedback when actions are completed (e.g., loading indicators or success messages)
so users know what is happening and whether their actions were successful.

8. Design for Flexibility and Efficiency

 Principle: Design interfaces that allow for flexibility in usage, accommodating both novice
and expert users.
 Application: Provide options for users to customize their interactions or provide shortcuts
for more experienced users. This enhances both the usability and efficiency of the system.

9. Ensure Consistency

 Principle: Consistency across the interface is key to helping users feel comfortable and
confident with the system.
 Application: Use consistent design patterns, language, and navigation throughout the
interface to minimize confusion. For instance, the same button should always perform the
same action in different parts of the system.
10. Minimize User Errors

 Principle: Design should minimize the risk of user errors and make error recovery easy.
 Application: Anticipate common errors and prevent them where possible (e.g., disabling
buttons that cannot be used). If errors occur, provide clear error messages and simple
instructions on how to recover.

Topic 6: Usability testing and evaluation methods are critical components of the User-
Centered Design (UCD) process. They help ensure that systems and interfaces meet the
needs of users, are easy to use, and are efficient for their intended tasks. Below are some
commonly used usability testing and evaluation methods:

1. Usability Testing

 Definition: A method of evaluating a system or interface by observing real users as

they perform tasks.
 Types:
o Formative Testing: Conducted early in the design process, focusing on
gathering insights for iterative improvement.
o Summative Testing: Conducted after the system is near completion,
measuring the final usability of the product.
 How It Works: Participants are asked to perform specific tasks on the system or
interface. Their performance is observed and recorded, focusing on task completion
rates, time on task, error rates, and user satisfaction.

Here are the key usability metrics commonly used in HCI:

1.1 Effectiveness

 Definition: How accurately and completely users achieve their goals.

 Metrics:
o Task Success Rate: Percentage of tasks completed correctly.
o Error Rate: Number or frequency of mistakes users make.
o Assistance Requests: How often users need help or support.

1.2 Efficiency

 Definition: The resources (e.g., time, clicks) users expend to accomplish a task.
 Metrics:
o Time on Task: How long it takes users to complete a task.
o Number of Clicks or Steps: Interactions required to complete a task.
o Navigation Efficiency: Whether users follow the optimal path.
1.3 Satisfaction

 Definition: Users' subjective feelings about the ease and comfort of using the system.
 Metrics:
o System Usability Scale (SUS): A 10-item questionnaire that yields a score from 0–
100.
o Net Promoter Score (NPS): Measures likelihood of users recommending the
product.
o Post-Task or Post-Test Ratings: User ratings (often on a Likert scale) for each task or
the overall experience.

1.4 Learnability

 Definition: How easily new users can accomplish tasks the first time.
 Metrics:
o Time to First Task Completion: How long it takes a new user to complete a task.
o Number of Errors by First-Time Users: Mistakes made during initial use.
o User Confidence: How confident users feel during and after use.

1.5 Retention

 Definition: How well users remember how to use the system over time.
 Metrics:
o Task Recompletion Success: Can users perform the same task correctly after a
period of non-use?
o Memory Recall: Accuracy of recalling steps or interface functions.

2. Think-Aloud Protocol

 Definition: A method where users verbalize their thoughts as they interact with a
system.
 How It Works: While completing tasks, users are asked to speak aloud their
thoughts, feelings, and reasoning. This gives designers insight into how users
approach tasks and identify usability issues.
 Strengths: Provides valuable qualitative data about the user's thought process and
decision-making.
 Limitations: Some users may find it difficult to verbalize their thoughts, which may
affect the validity of the data.

3. Heuristic Evaluation

 Definition: An expert-based method where usability experts review an interface

against established usability principles (heuristics).
  How It Works: Evaluators examine the system and identify usability issues based on
heuristics like Nielsen's 10 Usability Heuristics (e.g., visibility of system status, user
control and freedom, consistency).
 Strengths: Can be done quickly and with relatively low cost; useful for identifying
major usability issues early.
 Limitations: It is subjective and dependent on the expertise of the evaluators, and it
may not always capture user-specific issues.

4. Cognitive Walkthrough

 Definition: An evaluation method where a usability expert walks through the system,
step by step, to simulate the user's thought process during task completion.
 How It Works: The evaluator steps through the interface from a user’s perspective,
considering whether each action is clear and logical, especially for new users. Focus
is placed on understanding potential difficulties in performing specific tasks.
 Strengths: Especially useful for identifying areas of confusion for first-time users.
 Limitations: Limited by the evaluator’s assumptions and expertise; doesn't directly
involve actual users.

5. A/B Testing (Split Testing)

 Definition: A method of comparing two or more versions of an interface to see which

one performs better.
 How It Works: Users are randomly assigned to use different versions of the system
or interface, and their interactions are measured to see which design leads to better
performance (e.g., task completion rates, user satisfaction).
 Strengths: Provides empirical data on user preferences and behavior.
 Limitations: Requires a large sample size to produce statistically significant results.

6. Surveys and Questionnaires

 Definition: Collecting quantitative and qualitative data from users about their
experiences with the system.
 How It Works: After using the system, users are asked to fill out a survey or
questionnaire to rate their experience. Common tools include the System Usability
Scale (SUS), Single Ease Question (SEQ), and Net Promoter Score (NPS).
 Strengths: Provides valuable subjective feedback and allows gathering data from a
large number of users.
 Limitations: Users may not always articulate their experience accurately or
thoroughly.

7. Card Sorting

 Definition: A technique used to understand how users categorize and organize

information.
 How It Works: Participants are given a set of items (e.g., menu options or features)
and asked to organize them into categories that make sense to them. This method is
useful for designing information architecture and navigation.
 Strengths: Helps align the system’s structure with users’ mental models.
  Limitations: Results may vary based on how well participants understand the content
being sorted.

8. Eye Tracking

 Definition: A method of tracking where users look on a screen while interacting with
a system.
 How It Works: Special devices or software track users’ eye movements to determine
where they focus their attention, which parts of the interface attract or distract them,
and how they navigate the screen.
 Strengths: Provides highly detailed data about user attention and behavior.
 Limitations: Requires specialized equipment and can be costly. It also doesn't
directly measure comprehension or usability.

9. Task Analysis

 Definition: A method of studying how users perform tasks to identify steps,

resources, and potential obstacles.
 How It Works: Designers break down tasks into smaller components and examine
how users complete each step. This helps identify inefficiencies, bottlenecks, and
opportunities for improvement.
 Strengths: Helps understand user workflows and improves task efficiency.
 Limitations: Time-consuming and requires detailed observation.

10. Remote Usability Testing

 Definition: Testing where users interact with a system from their own environment,
often using screen-sharing software or recorded sessions.
 How It Works: Users perform tasks on the system in their natural settings (e.g., at
home or in the office), and their interactions are recorded for later analysis.
 Strengths: Users are in their natural environment, which can provide more authentic
data.
 Limitations: Limited control over the testing environment and potential technical
issues.

Conclusion:

Usability testing and evaluation methods are essential for ensuring that products are user-
friendly, effective, and meet user needs. Depending on the project stage, resources, and goals,
designers may use a combination of these methods to gather both qualitative and quantitative
insights. These evaluations help in identifying issues early in the design process, iterating on
improvements, and ultimately delivering a product that provides an optimal user experience.