POWERED BY
📚 ReferMe: Your Academic Companion
A Student-Centric Platform by Pixen
🔹 About ReferMe
ReferMe, by Pixen, offers curated academic resources to help students study
smarter and succeed faster.
✅ Class Notes
✅ Previous Year Question Papers (PYQs)
✅ Updated Syllabus
✅ Quick Revision Material
🔹 About Pixen
Pixen is a tech company helping students and startups turn ideas into reality.
Alongside ReferMe, we also offer:
✅ Custom Websites
✅ Machine learning
✅ Web Applications
✅ E‑Commerce Stores
✅ Landing Pages
[Link] [Link]
Powered by
hule Pune Un
ai P ive
ib
tr r
vi
sit
Sa
y
Computer Engineering - HCI
HCI - Unit 2
OVERVIEW OF HCI
Know your user/client: Understanding how people interact with
computers, Important human characteristics in Design, Human
considerations in design of Business systems, Human Interaction
speeds, Performance versus Preference, Methods of gaining an
understanding of users, Miller’s Law. Design Guidelines: Navigating
the interface, Organizing the display, Getting user’s attention,
Facilitating data entry. Principles: Determine user’s skill level,
Identify the tasks, interaction style, Natural Language, Eight
Golden rules of Interface design, Prevent errors, Ensuring Human
control while increasing automation. Theories: Design-by-level,
Stages of action, Consistency, Contextual Theories, Dynamic
theories.
More Stuff Inside → Click here
Powered by
HCI – Knowing Your User & Design Guidelines
1. Know Your User/Client
Definition:
The process of understanding the needs, abilities, limitations, and
preferences of the target audience before designing an interactive system.
1.1 Understanding How People Interact with Computers
Interaction involves input (commands) → processing → output
(feedback).
Must consider perception, cognition, motor skills, and emotional state.
1.2 Important Human Characteristics in Design
Physical abilities: vision, hearing, motor control.
Cognitive abilities: memory capacity, problem-solving skills.
Cultural & language differences.
1.3 Human Considerations in Business Systems
Minimize data entry errors.
Support multiple user roles (admin, staff, customer).
Ensure accessibility for all employees.
1.4 Human Interaction Speeds
Keystroke: ~0.2s
Mouse click: ~0.1–0.2s
Eye movement: ~0.02s
Design should match natural user speed for efficiency.
1.5 Performance vs Preference
Performance: How quickly/accurately a task is completed.
Preference: What the user likes to use (may not always be most
efficient).
More Stuff Inside → Click here
Powered by
1.6 Methods to Understand Users
Observation (shadowing users)
Interviews/Surveys
Focus groups
Usability testing
Analytics & logs
1.7 Miller’s Law
The average person can hold 7 ± 2 items in short-term memory.
Interfaces should avoid overwhelming the user with too many choices.
2. Design Guidelines
2.1 Navigating the Interface
Provide clear menus, breadcrumbs, and search options.
2.2 Organizing the Display
Group related information.
Use alignment and white space effectively.
2.3 Getting User’s Attention
Use color, size, animation, or sound for important alerts.
2.4 Facilitating Data Entry
Provide drop-downs, auto-complete, and error prompts.
3. Design Principles
3.1 Determine User’s Skill Level
Novice: Needs guided navigation and tooltips.
Expert: Needs shortcuts and automation.
3.2 Identify the Tasks
Focus on high-frequency and high-importance tasks first.
More Stuff Inside → Click here
Powered by
3.3 Choose an Interaction Style
Command line, menu-driven, direct manipulation, or natural language.
3.4 Natural Language
Use human-like commands and conversational UI.
3.5 Eight Golden Rules of Interface Design (Shneiderman)
Strive for consistency.
Enable shortcuts for frequent users.
Offer informative feedback.
Design dialogs to yield closure.
Offer simple error handling.
Permit easy reversal of actions.
Support internal locus of control.
Reduce short-term memory load.
3.6 Prevent Errors
Input validation, confirmation prompts.
3.7 Ensure Human Control while Increasing Automation
Allow manual override of automated decisions.
4. Design Theories
Design-by-Level: Break down design tasks into abstraction levels.
Stages of Action (Norman):Forming goals
Executing actions
Evaluating results
Consistency Theory: Similar operations & UI elements behave the same.
Contextual Theories: UI should adapt to the user’s environment.
Dynamic Theories: Systems should evolve with changing user needs.
More Stuff Inside → Click here
Powered by
Real-Life Example:
Good: Google Docs – consistent, responsive, shortcuts for experts,
tooltips for beginners.
Poor: Complex enterprise ERP with too many menus and no
guided help.
More Stuff Inside → Click here
