C3 COMP3423 · Crash course Midterm · Sat 31 Oct 2026 · 11:30

Human–Computer Interaction Up to week 7 45 minutes · MCQ + short

Everything examinable, in one sitting.

Seven weeks of lectures, one test, 45 minutes. This course compresses the decks into only what the exam can ask — the definitions, the mechanisms, the worked examples and the arguments — then makes you prove you know it with concept checks and paper-style questions.

4 chapters 32 concept-check MCQs 13 exam-style questions with model answers 1 full mock paper ≈ 1 h 45 cover-to-cover
The syllabus, in one box

"Scope: up to week 7 materials (except Figma); format: MCQs + short questions; duration 45 minutes." That is the authoritative statement. Week 7 is Lecture 04, Part 1, so everything from week 8 — large language models, transformers, speech acts, Grice, scripts — is out. So is all of ergonomics (week 9). Figma is in scope only as a concept: know that it is a high-fidelity prototyping tool and why you would use one, not how to operate it.

The syllabus, week by week

The cut falls halfway through Lecture 04
WeekLectureWhat it is really aboutChapter
1–2Intro to HCI, Parts 1–2Why HCI exists, what it is, where it came from, who it borrows from01 · Use & context
3–4Human Information Processing, Parts 1–2Perception → memory → problem solving → motor output; Fitts' law02 · The human
5–6Visual Perception & Computer Graphics, Parts 1–2How the eye lies, Gestalt grouping, reading, typography, CRAP03 · The visual
7Language, Communication & Dialogue, Part 1 onlyThree kinds of language, dialog levels and notations, STN, the NLP pipeline04 · Language
8–9Language Part 2 · ErgonomicsAfter the cut — LLMs, speech acts, Grice, scripts, I/O devices, BCI. Not on the midterm.—

Tutorial material is examinable too, but the Figma operations are explicitly excluded. There is a reference page on ergonomics at 05 · Ergonomics — kept for the final exam, clearly not part of this paper.

Chapters

Read → self-test → answer one exam question out loud
Chapter 01 · Weeks 1–2

Use & Context

Lecture 01, Parts 1 & 2

Why bad design costs money and lives, what HCI officially is, and the history that explains today's interfaces — batch → time-sharing → personal computing → the user takes centre stage.

cost of redesignAA965 · Three Mile IslandSIGCHI definitionMemex → Star → Macpioneers vs settlers
0/8 concepts nailedRead →
Chapter 02 · Weeks 3–4

The Human

Lecture 02, Parts 1 & 2

The human as an information processor: what perception, memory and problem solving can and cannot do — and the one formula you must be able to compute.

goal state · problem spacemeans–end analysisrepresentation levelsFitts' lawID · IP · reaction time
0/8 concepts nailedRead →
Chapter 03 · Weeks 5–6

The Visual

Lecture 03, Parts 1 & 2

Colour is not in the light, depth is not in the retina, patterns are not in the data. Then the practical half: Gestalt, reading, typography, CRAP and icons.

rods · cones · acuityGestalt laws3D cuessaccades · fixationsCRAP + gridsambiguity
0/8 concepts nailedRead →
Chapter 04 · Week 7

Language & Dialogue

Lecture 04, Part 1 only

Three kinds of language — coding, dialog, natural. STNs you can draw under time pressure, and the NLP pipeline: tokenisation, tagging, parsing, semantics, coreference.

lexical · syntactic · semanticSTN · escapestokenisationcoreferenceparse treeambiguity
0/8 concepts nailedRead →
Final rehearsal · 45 minutes · matches the real format

Mock midterm paper

10 multiple-choice and 3 short questions — exactly the two sections the midterm uses, restricted to weeks 1–7. Every item has a “Show answer” button with a model answer and a marking note, so you can mark yourself the way the examiner will.

Sit the paper →

If you only have this evening

Roughly 2 hours, in this order
Step 1 · 50 min

Read 02 and 03

They carry the most computable material: Fitts' law, problem-solving vocabulary, Gestalt, typography. Do the concept checks as you go — in a 45-minute paper, the MC section is the cheapest marks.

Step 2 · 35 min

Read 04

STN drawing and the NLP pipeline. Sketch the ATM diagram from memory, then check it. Say the five pipeline stages aloud in order, with one failure mode each.

Step 3 · 45 min

Sit the mock, closed book

Forty-five minutes on a timer, exactly like the real thing. Only afterwards open the model answers and the marking notes.

Step 4 · 10 min

Recite the facts

Scroll to the high-yield list below. If you can say each line without looking, you are done. If not, jump to the chapter it came from.

What the paper looks like

Format stated for the midterm; style borrowed from the past papers
Read this before you trust the mock

The midterm is 45 minutes, MCQs plus short questions — no long case study, no 20-mark essay. The past papers in the repository are final exams: two to three hours, whole-course syllabus, including evaluation, VR and testing material that is not examinable now. They are useful for question style only — the phrasing of an MC item, the “draw an STN” task, the “name and explain” short question. The mock keeps that style and restricts the content to weeks 1–7.

SectionFormatWhat it asks forWhere to practise
AMultiple choice, one best answer, no negative markingDefinitions, one-line discriminations, “which principle explains this screenshot”, small calculations32 concept checks across four chapters
BShort questions — name, explain, apply, justifyFitts parameters, dialog levels, draw an STN, typography critique, NLP stage analysis13 exam-style questions with model answers
45 minutes total. Budget: ~12 minutes on the MC, ~28 on the short questions, ~5 to check. A short question is roughly 5–10 marks, so two or three sentences per mark-point — not an essay.

Recurring archetypes across the four papers: draw an STN from a prose scenario (ATM, login CLI, toy camera, smart speaker) · Fitts' law parameters, and whether the law survives in 3D or microgravity · characterise a user's problem-solving (strategy + representation level) · explain a perception or typography failure · find the NLP failure in a dialogue log. Only the first four are in scope now; the NLP-failure archetype survives in a week-7 form (tokenisation, coreference, parsing), not in its speech-act or Grice form.

Fourteen facts that keep coming back

Say each one out loud before you close the laptop
  1. Usability engineering is software engineering. 63% of large projects overrun cost; the four user-related reasons are requested changes, overlooked tasks, users not understanding their own requirements, and poor user–developer communication. Pay a little now or a lot later.
  2. HCI is the design, implementation and evaluation of interactive computing systems for human use — an input language for the user, an output language for the machine, and a protocol for interaction.
  3. AA965 (Cali, 1995) typed ROMEO instead of ROZO and got no feedback on the chosen beacon: officially “pilot error”, actually poor HCI. Three Mile Island: a lamp said “valve closed” while it was open, 1,500 alarms, an on/off silencer.
  4. Pioneer systems innovate but are commercially unviable (Xerox Star, $15,000); settler systems make the ideas succeed later (Macintosh, $2,500, developer toolkit, interface guidelines).
  5. Fitts' law: T = a + b·log₂(2D/W). Difficulty rises with distance and falls with target width; ID belongs to the task, a and b belong to the device; IP = 1/b.
  6. Well-defined problem = full specification of data, actions, strategies and goal states, representable as a problem space. Ill-defined = partial specification, e.g. a mission statement.
  7. Difference reduction moves toward the goal one visible step at a time and gets trapped in local maxima; means–end analysis accepts sub-goals that temporarily increase the distance.
  8. Colour is not a property of light; it is the eye's interpretation of frequencies. 3D is not a property of the retina; it is constructed from fixations, memory imputation, motion parallax and optic flow.
  9. Gestalt: similarity, proximity, symmetry, continuity, closure, smallness, surroundedness. Patterns are constructed, not recognised — which is why a Dalmatian appears in dots and why a model can fail on the same image.
  10. CRAP — contrast, repetition, alignment, proximity — plus unity and grids. One to two typefaces, two weights, two slants, four sizes, ≥2 pt apart; sans-serif on screen, ≤60 characters per line in print.
  11. Dialog levels: lexical = shape of the control; syntactic = order of inputs and outputs; semantic = effect on the application's data. A good answer names the level before naming the fix.
  12. STN: circles are states, arcs are actions/events, labels are action / condition. Draw escapes once at a meta level, or the diagram becomes spaghetti of duplicated behaviour.
  13. NLP pipeline: tokenisation → POS tagging → parsing (parse tree) → semantic analysis → coreference resolution. Errors cascade, so accuracy drops with sentence length. Tokenisation is the hard stage across languages: Chinese has no spaces, Turkish packs a clause into one word.
  14. Ambiguity is the reason all of this exists. The 121 most frequent English nouns average 7.8 meanings each; one ordinary sentence yields ~14 quadrillion possible interpretations — and speakers do not notice the ambiguity at all.