English:Human-Computer Interaction
Human-Computer Interaction
Introduction
Human-Computer Interaction or HCI is the study and design of interactions between people and interactive computing systems. HCI combines ideas from computer science, cognitive psychology, design, human factors, communication, and the social sciences. Its central question is not simply “Can a system perform a task?” but “Can people understand, control, trust, and use the system effectively in a real context?”
For learners in Grades 11–13, HCI is useful because nearly every digital product you encounter has an interface: a phone, website, game, navigation system, smart appliance, learning platform, ticket machine, medical device, or AI assistant. Good interaction design can reduce mistakes, save time, improve accessibility, and support informed decisions. Poor interaction design can create confusion, exclusion, frustration, privacy risks, and even safety problems.
By the end of this aiMOOC, you should be able to explain major HCI concepts, analyze interfaces, create and test prototypes, interpret usability evidence, and justify design decisions for different users and contexts.
What HCI Studies
HCI studies the complete interaction between a person, a technology, a task, and a context. The “computer” may be visible, as in a laptop, or embedded in another object, as in a car dashboard or smart thermostat. The “interaction” may involve clicking, touching, typing, speaking, gesturing, looking, moving, or receiving haptic, auditory, or visual feedback.
A useful HCI analysis asks several kinds of questions. What is the user trying to achieve? What information does the system require? What actions are possible? What feedback follows an action? What knowledge must the user remember? Which errors are likely? How does the environment affect use? Which people might be excluded by the design?
A strong HCI solution therefore balances several goals. Effectiveness concerns whether users can achieve the intended goal. Efficiency concerns the time, effort, and resources required. Learnability concerns how easily a newcomer can begin. Safety concerns preventing harmful actions and supporting recovery. Accessibility concerns whether people with diverse abilities can perceive, operate, understand, and use the system. User experience includes the broader quality of the interaction, such as confidence, satisfaction, meaning, and perceived control.
A Short History of Interactive Computing
Early computers were operated mainly by specialists through switches, punched media, and command-oriented interfaces. Over time, interactive computing became more direct and more widely available. Research in the 1960s explored pointing devices, hypertext, collaborative computing, and interactive displays. Douglas Engelbart’s research group at SRI demonstrated many influential interaction ideas in 1968; a mouse prototype associated with that work was built by Bill English.
The Xerox Alto, developed in the 1970s, became an influential research system for graphical interaction. Graphical user interfaces later popularized windows, icons, menus, and pointing. Personal computers, the Web, smartphones, multitouch screens, voice assistants, wearables, and immersive systems expanded the range of interactions further.
HCI history is important because interaction techniques are not inevitable. They result from design choices, technical possibilities, social expectations, and repeated evaluation. Today, interfaces increasingly include sensors, machine learning, augmented reality, and systems that adapt to users.
Humans: Capabilities, Limits, and Mental Models
Human perception and cognition shape interface design. People have limited attention and working memory, so an interface that forces users to remember many unrelated details can increase cognitive load. Recognition is often easier than recall: selecting a clearly labeled option is usually easier than remembering an exact command. Visual grouping, readable typography, meaningful labels, and consistent placement can reduce unnecessary mental effort.
A mental model is a user’s internal explanation of how a system works. If the interface behaves in ways that match a useful mental model, users can predict what will happen next. If the design suggests one behavior but produces another, users may make errors even when the software is technically functioning correctly.
Feedback helps users connect an action with its result. A pressed button that visibly changes state, a progress indicator during a long operation, or a clear confirmation after saving can reduce uncertainty. Feedback should be timely, noticeable, and proportional to the importance of the action.
Constraints restrict possible actions. A date field that only accepts valid dates, a disabled “Submit” button until required information is complete, or a connector that fits only one way can prevent some errors. Good constraints guide users without creating unnecessary barriers.
Affordances are possibilities for action, while signifiers communicate where or how an action can be performed. A button-shaped control may signify that it can be pressed. In digital interfaces, signifiers are especially important because the screen itself does not physically reveal every possible action.
Input, Output, and Multimodal Interaction
Interaction can use many input channels. Keyboards support precise text entry; pointing devices support spatial selection; touchscreens enable direct manipulation; microphones support speech input; cameras and sensors can detect movement or context; eye trackers can measure or sometimes enable gaze-based interaction. Output may be visual, auditory, or haptic.
.jpg)
Different modalities have different strengths and limitations. Voice input may be useful when hands are occupied, but it can be inappropriate in a noisy or private environment. Touch is direct, but small targets are difficult to select accurately. Visual alerts can be missed when attention is elsewhere, so critical systems may combine visual, auditory, and haptic feedback.
Multimodal design should not assume that every user can use every channel. Redundant alternatives can improve robustness: captions can complement audio, keyboard access can complement pointing, and text labels can complement color.
Efficiency and Fitts's Law
A classic HCI model, Fitts's law, predicts the time required to point to a target as a function of the target’s distance and size. A common form is:
Here, is movement time, is the distance to the target, is the target width along the direction of movement, and and are empirically measured constants for a particular interaction setting.
The design implication is intuitive: targets that are larger or closer are generally faster to acquire. This helps explain why frequently used controls should not be tiny and why edges or corners can be effective target locations in some pointer-based interfaces. However, Fitts's law is a model of pointing performance, not a complete theory of interface quality. Meaning, visibility, motor ability, device type, context, and error costs also matter.
A useful classroom experiment is to compare selection times for targets with different widths and distances. You can then plot movement time against the index of difficulty and examine whether the data approximately follow the predicted trend.
User Experience and User Needs
User experience or UX includes a person’s perceptions and responses before, during, and after interacting with a product or service. HCI and UX overlap strongly, but HCI is also an academic field that develops theories, methods, and empirical findings about interaction.
Design should begin with user needs rather than with features. A “need” is not the same as a requested interface element. If a student says, “I need a large dashboard,” the deeper need might be to see deadlines quickly, compare priorities, or reduce the risk of forgetting work. HCI research tries to uncover goals, constraints, habits, environments, and existing workarounds.
Common research methods include observation, interviews, contextual inquiry, diary studies, surveys, analysis of existing tasks, and usability testing. No single method answers every question. Qualitative methods can explain why a problem occurs; quantitative measures can estimate how often, how quickly, or how successfully something happens.
Interaction Design Principles
Several principles can help you analyze an interface.
Visibility of system status means users should be able to tell what the system is doing. A loading state, upload progress, or clear connection indicator prevents uncertainty.
Match with the real world means concepts, labels, and sequences should fit the user’s task rather than expose unnecessary technical details.
Consistency means similar elements should behave similarly. Consistency reduces learning effort, but it should not preserve a bad pattern merely for uniformity.
Error prevention is often better than error messages after failure. Interfaces can use constraints, previews, validation, and safer defaults to prevent predictable mistakes.
Error recovery matters when prevention is impossible. Users should be able to undo, revise, cancel, or understand what went wrong.
User control means the interface should not trap people in unwanted states. Actions with major consequences should be clearly distinguished from routine actions.
Recognition over recall reduces memory demands by making relevant options, history, or instructions visible when needed.
Progressive disclosure can keep complex systems manageable by showing essential options first and advanced options when they become relevant.
These are not rigid laws. Designers must interpret them in context and test whether a proposed solution actually helps the intended users.
Accessibility and Inclusive Design
Accessibility is a core HCI responsibility. An accessible interface should support users with diverse visual, auditory, motor, speech, cognitive, and neurological characteristics. Accessibility also matters when ability is temporarily or situationally limited, such as using a device in bright sunlight, with an injured hand, or in a noisy room.
The Web Content Accessibility Guidelines organize accessibility around four principles often summarized as POUR: content should be perceivable, operable, understandable, and robust. Practical design choices include sufficient text contrast, meaningful headings, keyboard-operable controls, visible focus indicators, captions and transcripts, informative alternative text, clear error messages, and layouts that remain usable when text is enlarged.
Accessibility testing should combine automated checks with human evaluation. Automated tools can identify some technical problems, but they cannot determine whether instructions are understandable, alternative text is meaningful, task flow is practical, or keyboard order matches user expectations.
Inclusive design also asks who was included in the research. If all test participants have similar abilities, devices, language backgrounds, or experience, important barriers may remain invisible.
From Problem to Prototype
A human-centered design process is iterative. A simplified cycle is:
- User research: Study users, goals, tasks, constraints, and context.
- Requirements analysis: Translate evidence into clear needs and design criteria.
- Ideation: Generate several possible solutions before committing to one.
- Prototyping: Build representations that are detailed enough to answer a design question.
- Usability testing: Observe representative users attempting realistic tasks.
- Iteration: Revise the design based on evidence and test again.
A low-fidelity prototype might be a paper sketch, storyboard, or clickable wireframe. It is cheap to change and useful for exploring structure and task flow. A high-fidelity prototype more closely resembles the intended product and can test visual details, interactions, timing, and content. The right fidelity depends on the question you are trying to answer.
A prototype should not be mistaken for proof that a design is good. It is a tool for learning. The most valuable prototype is often the one that reveals a mistaken assumption early.
Usability Testing and Evaluation
In a usability test, a facilitator asks a participant to attempt realistic tasks using a product or prototype while the researcher observes behavior and listens to feedback. The goal is to identify usability problems and opportunities, not to test whether the participant is “good at computers.”
Strong usability tasks describe a goal without giving away the steps. Instead of saying “Click Settings, then Privacy, then Export,” a task might say, “You want a copy of the data this service stores about you. Show how you would try to get it.” This preserves the chance to discover whether the interface itself supports the goal.
Useful measures include task completion, time on task, error counts, paths taken, and ratings. Qualitative evidence such as hesitation, confusion, comments, and strategies can explain why a problem occurs. Measures must be interpreted carefully: a faster time is not automatically better if it comes with more errors or lower confidence.
A heuristic evaluation is different from user testing. In heuristic evaluation, knowledgeable reviewers inspect an interface using established usability principles. It can find many issues efficiently, but it does not replace observing actual users.
Ethical testing requires respect for participants. Explain the study, obtain appropriate consent, collect only necessary data, protect privacy, avoid deceptive pressure, and make it clear that participants may stop. In school projects, follow institutional rules for research involving classmates or minors.
Experimental Thinking in HCI
HCI often uses experiments to compare design alternatives. A clear experiment identifies an independent variable that the researcher changes, such as button size, and a dependent variable that is measured, such as selection time or error rate.
A fair comparison tries to control confounding factors. If one interface is tested on a fast computer in a quiet room and another on a slow computer in a noisy room, differences in results cannot be attributed confidently to the interface alone.
Repeated-measures designs let the same participants try multiple conditions, which can reduce differences caused by individual skill. However, order effects can occur because people learn or become tired. Counterbalancing the order can reduce this problem.
Statistical results should be interpreted together with practical significance. A tiny measurable difference may not matter to users, while a rare but severe error may matter greatly even if average performance looks good.
Ubiquitous, Intelligent, and Emerging Interfaces
Computing is increasingly embedded in everyday environments. Ubiquitous computing describes situations in which computation is distributed across devices, objects, and spaces rather than confined to one desktop computer.
Emerging HCI areas include voice interfaces, wearables, augmented and virtual reality, tangible interfaces, brain-computer interfaces, and AI-supported interaction. These technologies create new design opportunities but also new risks.
AI interfaces deserve particular care because outputs may be probabilistic, incomplete, or wrong. Good interaction design can communicate uncertainty, support verification, preserve user control, show relevant provenance when available, and make correction possible. Designers should also consider automation bias: people may trust automated suggestions too readily, especially when the interface presents them with unwarranted confidence.
For adaptive systems, personalization can improve relevance but can also reduce predictability. Users need meaningful control over settings, data collection, and important automated decisions.
A Design Case Study: A School Deadline Planner
Imagine that your class is designing a deadline planner for students. A feature-driven approach might begin by listing calendars, badges, AI recommendations, chat, and color themes. An HCI approach begins with users and tasks.
Research might reveal that students need to see which deadlines are urgent, distinguish estimated work from fixed due dates, understand dependencies between tasks, and enter information quickly on a phone. Some students may rely on screen readers or keyboard navigation. Others may share devices or have unreliable internet access.
You could sketch three alternative designs. One might use a chronological list, one a weekly calendar, and one a priority matrix. A usability study could ask students to add an assignment, identify the next urgent task, reschedule work after an absence, and find overdue items. You would observe where they hesitate, what they misunderstand, and which information they need.
The result may be a design that looks different from your first idea. That is a success of the process: HCI treats evidence-driven revision as learning, not as failure.
Media Reflection
The historical mouse, Xerox Alto, touchscreen image, eye-tracking equipment, and Fitts’s law diagrams show that HCI spans hardware, software, perception, and empirical measurement. The videos add complementary perspectives on HCI foundations, design, UX, accessibility, and usability testing. When studying media, ask what claim each item supports and what it cannot prove by itself.
Interactive Tasks
Quiz: Test Your Knowledge
What is a central concern of Human-Computer Interaction? (How people understand and use interactive systems) (!How to maximize processor clock speed) (!How to eliminate all human decision making) (!How to store files without interfaces)
What does timely feedback help a user understand? (The result or status of an action) (!The manufacturing cost of a device) (!The source code of every feature) (!The age of the operating system)
What does Fitts's law model in HCI? (The time required to point to a target) (!The accuracy of speech recognition) (!The brightness of a display) (!The memory capacity of a computer)
Which change generally makes a pointing target easier to acquire according to Fitts's law? (Making the target larger) (!Making the target invisible) (!Increasing the distance to the target) (!Removing all feedback)
What is the main purpose of a low-fidelity prototype? (To explore ideas quickly and cheaply) (!To prove that the final system has no defects) (!To replace all user research) (!To measure network bandwidth)
What happens in a usability test? (A participant attempts realistic tasks while a researcher observes) (!A compiler checks the interface for syntax errors) (!A manager predicts every user action) (!A database automatically redesigns the product)
Which principle is represented by making similar controls behave similarly? (Consistency) (!Randomization) (!Compression) (!Encryption)
Which option best describes accessibility? (Designing interaction so people with diverse abilities can use it) (!Designing only for expert users) (!Removing all keyboard controls) (!Using color as the only source of information)
What is a mental model? (A user's internal explanation of how a system works) (!A backup copy of the operating system) (!A physical model of the processor) (!A list of every programming language)
Why should AI interfaces communicate uncertainty when it matters? (To help users judge and verify probabilistic outputs) (!To make every answer longer) (!To prevent all human oversight) (!To hide the origin of information)
Memory Game
| Affordance | A possibility for action offered by an object or interface |
| Feedback | Information showing the result or status of an action |
| Prototype | An early representation built to explore or test a design |
| Usability | The quality of achieving goals effectively and efficiently in context |
| Accessibility | The quality of supporting use by people with diverse abilities |
| Mental model | A user's internal explanation of how a system behaves |
Drag and Drop
| Match the correct terms. | Topic |
|---|---|
| Think-aloud method | A participant verbalizes thoughts while attempting a task |
| Wireframe | A simplified representation of interface structure |
| Heuristic evaluation | Reviewers inspect an interface using usability principles |
| Responsive design | A layout adapts to different screen sizes and conditions |
| Progressive disclosure | Advanced options appear when they become relevant |
...
Crossword Puzzle
| Affordance | What term describes a possibility for action offered by a design? |
| Feedback | What tells a user about the result or status of an action? |
| Usability | What quality concerns effective and efficient goal achievement in context? |
| Prototype | What early design representation is built for exploration and testing? |
| Accessibility | What field of design aims to remove barriers for people with diverse abilities? |
| Consistency | What principle makes similar controls behave in similar ways? |
LearningApps
Cloze Text
Open-Ended Tasks
Easy
- Interface diary: For one day, record five interfaces you use, the goal you had, one effective design choice, and one moment of friction; explain each observation with an HCI concept.
- Signifier photo study: Photograph or sketch four everyday controls and annotate how each design signals possible actions, then compare physical and digital signifiers.
- Accessibility quick audit: Choose a school website or learning platform and inspect keyboard access, headings, text enlargement, captions, and color dependence; summarize two strengths and two barriers.
- Paper prototype: Create a paper prototype for a three-screen school service and ask a classmate to complete one realistic task without instructions.
Standard
- Usability test plan: Write a short test plan for a familiar app with a research question, participant profile, three goal-based tasks, observations to record, and an ethical consent statement.
- Fitts's law experiment: Build or use a simple target-selection activity with at least three target sizes or distances, collect timing data, graph the results, and discuss whether the pattern supports the model.
- Interface redesign: Select a confusing form or menu, identify problems using feedback, consistency, error prevention, recognition, and accessibility, then create and justify a revised wireframe.
- User interview project: Interview at least two people about a shared digital task, code their comments into needs and pain points, and distinguish requested features from underlying goals.
Advanced
- Comparative usability study: Compare two interfaces for the same task using a controlled procedure, combine quantitative and qualitative evidence, and discuss confounding variables and limitations.
- Inclusive design project: Design a prototype for users with at least two different access needs, justify alternative input and output channels, and evaluate the design with accessibility criteria.
- AI interaction critique: Analyze an AI-supported interface for uncertainty, user control, correction, provenance, privacy, and automation bias, then propose a safer interaction pattern.
- HCI research video: Produce a five-minute documentary-style video that explains an HCI question, demonstrates a small study or prototype, reports evidence, and reflects on ethics and limitations.
Learning Assessment
- Evidence-based redesign: Analyze an unfamiliar interface, identify at least three usability or accessibility problems, and justify a redesign by connecting each change to observed evidence or an HCI principle.
- Experimental reasoning: Given results from two interface conditions, decide whether the evidence supports a design change, identify possible confounds, and explain what further data would strengthen the conclusion.
- Transfer to safety-critical systems: Apply feedback, constraints, error prevention, and recovery to a medical or transport interface and explain why the cost of an error changes design priorities.
- Model application: Use Fitts's law qualitatively or quantitatively to compare two target layouts, then explain at least two important factors the model does not capture.
- Accessibility argument: Evaluate a multimodal interface against perceivable, operable, understandable, and robust design goals, and recommend changes for at least two different user needs.
- Responsible AI design: Create a decision flow for an AI-supported feature that includes uncertainty communication, verification, correction, privacy, and a meaningful human override.
Evidence of Learning
Knowledge: You can explain core HCI ideas including user needs, mental models, affordances, signifiers, feedback, constraints, usability, accessibility, prototyping, Fitts's law, and iterative evaluation.
Skills: You can observe interaction carefully, write unbiased task scenarios, build prototypes, conduct basic usability studies, analyze qualitative and quantitative evidence, identify accessibility barriers, and justify design decisions.
Products: Strong evidence may include annotated interface analyses, interview notes, paper or digital prototypes, usability test plans, study data, charts, redesigns, accessibility audits, and short explanatory videos.
Reasoning: You can distinguish a design preference from evidence, identify confounding variables, explain limitations, compare alternatives, and connect an observed problem to a plausible design principle.
Transfer: You can apply HCI thinking to new domains such as education, healthcare, transport, games, public services, AI tools, smart devices, and immersive environments while adapting priorities to the users and risks involved.
OERs on the Topic
Further Open Learning Resources
The HCI Lecture project provides openly licensed university-level teaching material on HCI, including videos on user needs, models, input and output, prototyping, design, and evaluation.
The Web Accessibility Initiative provides standards, explanations, and educational resources for accessible web design.
The Nielsen Norman Group user-testing resources provide practical explanations of usability testing and UX research methods.
Wikimedia Commons provides reusable media for studying the history and practice of HCI, including images of early pointing devices, interactive computers, touchscreens, and diagrams of Fitts's law.
Linked Learning Areas
aiMOOC Projects
MOOCwiki · Deutsch
Nach dem Lernen ist vor dem Lernen
Entdecke direkt den nächsten Lernkurs. Weitere Inhalte erscheinen, wenn Du weiter nach unten scrollst.
Zur MOOCwiki-HauptseiteMediathek wird aus dem Wiki geladen ...
Keine passenden Inhalte gefunden. Bitte ändere Suche oder Filter.