HCI (2019 Pattern) – Insem Solved Answers (Expanded, Exam-Ready)
Language: Simple, with correct technical terms. Each 5-mark answer has enough
depth/examples for full marks.
OCT 2022 – HUMAN COMPUTER INTERACTION (314444)
Q1 a) General Principles of HCI [5]
Explain at least five; write point + 1-line justification + tiny example.
Consistency: Same visual/behavioral patterns across screens reduce cognitive load. Eg:
Progress spinner + 'Uploading…' after pressing 'Submit'.
Feedback: System immediately tells user the result of an action (visual, sound, haptics).
Eg: Progress spinner + 'Uploading…' after pressing 'Submit'.
Visibility: Important controls are clearly visible; hidden options increase errors. Eg:
Progress spinner + 'Uploading…' after pressing 'Submit'.
Affordance & Signifiers: Control looks like how it is used; signifiers indicate interaction.
Eg: Progress spinner + 'Uploading…' after pressing 'Submit'.
Error Prevention & Recovery: Constrain invalid input; provide undo/confirm dialogs.
Eg: Progress spinner + 'Uploading…' after pressing 'Submit'.
User Control & Freedom: Allow cancel, back, escape hatch; avoid dead ends. Eg:
Progress spinner + 'Uploading…' after pressing 'Submit'.
Q1 b) What is HCI? Two application areas [5]
Definition: HCI is the study and design of human–computer interaction to maximize
usability, usefulness, accessibility, and user experience (UX).
Applications (any two, write domain + how HCI helps):
ATMs/Kiosks – clear menu hierarchy, large buttons, timeout prompts for safety.
Mobile banking apps – visual hierarchy, biometrics, error messages for failed
transactions.
Q1 c) Opinion: “A design should be User-Centric” [5]
Argument: User-Centred Design (UCD) reduces learning time and errors, improves
satisfaction, and aligns with business KPIs (conversion, retention).
Evidence: Iterative usability tests often find >30% task-time reductions after redesigns.
Example: Food-delivery app moving 'Reorder' to home screen increased task success
and NPS.
Q2 a) Why study HCI? [5]
Usability & Efficiency: Faster task completion, fewer clicks, less mental effort.
Safety & Error Reduction: Critical in healthcare, finance, aviation.
Accessibility & Inclusion: Supports users with diverse abilities (WCAG).
Business Impact: Higher conversion, lower support cost, better reviews.
Compliance & Ethics: Privacy notices, transparent choices (dark-pattern avoidance).
Q2 b) UCD principles [5]
Understand context of use (users, tasks, environment, constraints).
Involve users continuously (interviews, observations, usability tests).
Iterative design (prototype → test → refine).
Define usability goals & metrics (TTF, error rate, SUS score).
Holistic experience (content, IA, interaction, visual, accessibility).
Q2 c) Psychology of everyday things [5]
Key ideas from Norman applied to daily objects and UIs:
Mental models: Users predict outcomes; mismatch causes errors (e.g., mislabeled icons).
Affordances/signifiers: Door handle suggests pulling; flat plate suggests pushing.
Mapping: Control layout mirrors results (stove knobs → burners).
Feedback: Immediate visible/audible response prevents repeated actions.
Constraints: Physical, logical, cultural constraints prevent wrong actions.
Q3 a) Role of emotions in GUI [5]
Positive affect (pleasant visuals, micro-interactions) → better problem-solving,
perceived speed.
Aesthetics–Usability effect: Attractive UIs are judged as more usable.
Use calming colors, friendly empty states, success animations to reduce anxiety.
Example: Payment screen with progress + reassurance copy reduces abandonment.
Avoid stressors: flashing alerts, dense text, ambiguous errors.
Q3 b) WIMP interface & how to use its elements [5]
Windows: Separate task spaces; avoid overlap; allow resize/maximize.
Icons: Pictorial shortcuts; include labels/tooltips; consistent metaphor.
Menus: Organized by task frequency; keyboard shortcuts; disable illegal options.
Pointer: Precise selection; hover states; cursor feedback (busy, text-caret).
Design: Follow Fitts’s Law (bigger, closer targets), keep accelerators for experts.
Q3 c) Human senses; most important to HCI [5]
Sight (primary in GUIs): color, contrast, typography, layout.
Hearing: alerts, confirmations, screen-readers.
Touch: haptics, touch-targets, gestures on mobile.
Smell & Taste: Rarely used in mainstream computing.
Most important: Sight, Hearing, Touch – core to visual/audio/tactile interfaces.
Q4 a) Interaction styles; CLI pros/cons [5]
Styles: Command-Line (CLI), Menu selection, Form fill-in, Direct manipulation (drag-drop),
Natural language (voice/chat).
CLI Advantages: Fast for experts, scriptable, low resource use.
CLI Disadvantages: Steep learning curve, memorization, low discoverability.
Q4 b) Ergonomics with example [5]
Ergonomics = Fit the system to human body/capabilities to reduce fatigue and injury.
Examples: Adjustable chair/monitor height; wrist-friendly keyboard; readable font
sizes; sufficient contrast; touch targets ≥ 44×44 px.
Q4 c) Short-term vs Long-term memory [5]
STM/Working memory: Capacity ≈ 4–7 chunks, duration seconds; supports current
tasks.
LTM: Large, durable; semantic (facts), episodic (events), procedural (skills).
Design: Chunk info, progressive disclosure, recognition over recall, visible cues.
SEP 2023 – HUMAN COMPUTER INTERACTION (314444)
Q1 a) HCI → enhanced UX (justify) [5]
Better discoverability → quicker first-time success (e.g., clear CTAs).
Lower cognitive load → fewer errors (simple navigation, consistent layout).
Accessibility → larger audience (captions, keyboard nav).
Example: ATM with clear menu hierarchy reduces wrong withdrawals.
Metrics: Reduced time-to-task, higher SUS/NPS.
Q1 b) Three disciplines contributing to HCI [5]
Computer Science: algorithms, data, performance, security constraints.
Cognitive Psychology: perception, memory limits, attention, mental models.
Design/Human Factors: visual hierarchy, typography, ergonomics, prototyping.
Q1 c) Any two Norman’s Principles [5]
Visibility: Controls should be seen when needed (e.g., play/pause on media).
Feedback: System shows status after action (e.g., 'Saved' toast, loading bar).
Q2 a) Windows OS ↔ human factors (any two) [5]
Time to learn: Start menu + search lowers learning curve.
Speed of performance: Keyboard shortcuts, jump lists accelerate expert use.
User errors: Disabled menu items prevent invalid actions.
Retention: Consistent UI across versions helps recall.
Subjective satisfaction: Personalization, themes, smooth animations.
Q2 b) Achieving HCI principles via… (any two) [5]
Information access interfaces: Global search, filters, faceted navigation.
Reducing memory load: Autocomplete, defaults, recognition, recent files.
Alternative interfaces: Voice control, screen readers, high-contrast modes.
Q2 c) Two Golden Rules of Shneiderman [5]
Strive for consistency (terminology, colors, layouts).
Offer informative feedback (micro-copy, status messages, progress).
Q3 a) Structure of memory with diagram (described) [5]
Sensory → raw stimuli, ms duration.
Short-Term/Working → limited capacity for active tasks.
Long-Term → durable storage (semantic, episodic, procedural).
Flow: Sensory input → attention → STM → rehearsal/encoding → LTM; retrieval returns to
STM.
Q3 b) Models of interaction [5]
Norman’s Execution–Evaluation Cycle: form goal → execute → perceive → interpret →
evaluate.
Abowd & Beale: user, input, system, output; translations between them.
GOMS/KLM: predicts expert task time via operators/keystrokes.
Q3 c) Five individual differences to consider [5]
Age & motor control (target sizes, timing).
Language & literacy (plain language, icons with labels).
Culture (date formats, icons meaning).
Accessibility needs (screen reader, color-blind safe palettes).
Digital skills (onboarding, tooltips, progressive disclosure).
Q4 a) Affect and performance [5]
Negative affect (stress) narrows attention → more slips; show calming UI, clear errors.
Positive affect broadens thinking → better problem-solving; use friendly
visuals/microcopy.
Example: Friendly error pages reduce abandonment.
Q4 b) Two sub-types of LTM [5]
Declarative (explicit): semantic (facts) + episodic (events).
Procedural (implicit): skills and habits (e.g., typing).
Q4 c) Measures to reduce human errors [5]
Prevent: constraints, validated inputs, disable invalid actions.
Detect & recover: confirmations for destructive actions, undo, version history.
Explain: clear error messages with fix steps; highlight fields.
SEP 2024 – HUMAN COMPUTER INTERACTION (314444)
Q1 a) Importance of HCI with example [5]
Improves learnability, speed, accuracy, satisfaction.
Example: UPI app with big pay button, QR scan, and clear success feedback.
Q1 b) Two disciplines with examples [5]
Psychology: apply working-memory limits to keep steps ≤ 5 per task.
Ergonomics: kiosk screen height for standing users; glare reduction.
Q1 c) Feedback & Constraint scenarios [5]
Missing feedback: Elevator call button without light → users press repeatedly; fix with
LED + chime.
Unnecessary constraint: App blocks screenshots on non-sensitive screens; allow with
warning.
Q2 a) Apply two Norman concepts to a product [5]
Visible affordances (mobile camera): shutter button looks pressable → easy capture.
Mapping (volume keys): up/down maps to louder/softer → immediate understanding.
Opinion: These reduce learning time and user errors.
Q2 b) UCD process [5]
Research: stakeholder goals, user interviews, task analysis, context.
Define: personas, scenarios, usability goals (success rate, time).
Design: IA, wireframes, interactive prototypes.
Evaluate: usability tests, analytics, accessibility checks.
Iterate: refine based on findings.
Q2 c) MS Word vs measurable factors [5]
Time to learn: ribbon groups by tasks; tooltips help newbies.
Speed: keyboard shortcuts, quick access toolbar.
Errors: auto-recover, version history, spellcheck reduce damage.
Retention: consistent ribbon across versions restores memory.
Satisfaction: templates, themes, smooth formatting.
Q3 a) Passbook kiosk → interaction styles [5]
Covered: Menu selection, Form fill-in (account no.), Direct manipulation (touch).
Not covered: Natural language/voice; CLI.
Q3 b) HCI ↔ Ergonomics relationship [5]
HCI targets cognitive usability; ergonomics targets physical comfort/safety; both aim at
overall UX.
Example: ATM angle + large fonts + simple flow together reduce errors and strain.
Q3 c) Five individual differences [5]
Vision (color-blindness, low vision) → high contrast, scalable text.
Motor abilities → large targets, dwell options.
Cognition → simple steps, chunking, reminders.
Language → localized UI, icons with text.
Device constraints → responsive design, offline states.
Q4 a) Fastest→slowest human response (justify) [5]
Loud noise near ear (startle reflex, ~140 ms) – fastest involuntary reaction.
Touching hot iron (withdrawal reflex) – fast spinal reflex but may involve more
processing.
Applying brakes to red signal – slower, needs perception → decision → action.
Ordered: Loud noise → Touch hot surface → Apply brakes. If exam expects heat first, justify
with reflex types and context.
Q4 b) Intuitive design reduces memory load – two apps [5]
Google Maps: turn-by-turn guidance, landmark names → recognition not recall.
Online tax portal: step-by-step wizard, saved progress, inline help.
Q4 c) LTM script: Owner visits vet with dog [5]
Episodic: date/time, clinic location, vet’s name, dog’s symptoms, treatment.
Semantic: medical terms learned (vaccines, dosage).
Procedural: handling leash, paying bill, booking follow-up.
Encoding cues: clinic smell, pet weight number; Retrieval: next visit reminders trigger
recall.