Whole-Course Retrieval

Whole-course retrieval and command words

Retrieval: every lesson across this entire two-year course has ended with a "Check your understanding" prompt, and every question you've answered has used a command word — state, explain, evaluate, justify, and others — without ever pausing to teach what those words themselves actually demand of an answer. This lesson does exactly that, using retrieval across the whole specification as the vehicle.

Key vocabulary

• Command word — the specific instruction word in a question (state, define, describe, explain, compare, analyse, evaluate, justify, ...) that determines what kind of answer is actually required, independent of the topic being asked about.
• Descriptive answer — states or describes what something is or does.
• Analytical answer — breaks something down and examines how or why its parts work or relate.
• Evaluative answer — weighs evidence/criteria to reach and support a judgement.

Understand — the same topic, eight different demands

The command word changes what counts as a correct answer, even when the underlying topic is identical. Take "hash tables":

• State a property of a hash table. → "A hash table provides average O(1) lookup time." (a single fact, no justification needed)
• Define a hash table. → "A hash table is a data structure that maps keys to values using a hash function to compute an index into an array of buckets." (a precise, complete definition)
• Describe how a hash table stores a new value. → "The key is passed through a hash function, which produces an index; the value is stored at that index in the underlying array." (the mechanism, step by step, but not yet WHY it's good or bad)
• Explain why a hash table gives fast lookup. → "...because the hash function computes the storage location directly from the key, so looking a key up doesn't require searching through other entries at all, unlike a list." (the mechanism AND the reasoning behind it)
• Compare a hash table and a binary search tree for lookup speed. → states a similarity/difference between the two, e.g. average O(1) vs O(log n)
• Analyse why a poorly-chosen hash function causes performance problems. → breaks down HOW collisions arise and what effect they have on lookup time
• Evaluate whether a hash table is the right choice for a system needing sorted output. → weighs the hash table's strengths against this specific requirement to reach a judgement
• Justify a recommendation to use a hash table for a login-lookup system. → gives reasoned support for a specific, stated choice

See it — the escalation from descriptive to evaluative

Notice the vocabulary itself escalates: state/define/describe only need you to say what something IS; explain/analyse need you to say HOW or WHY; compare/evaluate/justify need you to weigh something and reach a conclusion. A student who only ever writes descriptively, even in response to an "evaluate" question, is answering a different, lower-demand question than the one actually asked — and will lose marks regardless of how accurate their description is.

Critique it — spot the mismatch

A question asks: "Evaluate whether a linked list or an array is more appropriate for a playlist that is frequently reordered." A student answers: "An array stores elements in contiguous memory with a fixed size, while a linked list stores elements as nodes connected by pointers, allowing dynamic resizing."

Identify what this response has done correctly, what is missing, and why it is descriptive rather than evaluative.

(Correct: the factual description of arrays vs linked lists (fixed contiguous memory vs dynamically-connected nodes) is accurate. Missing: nothing in the response actually WEIGHS the two options against the stated requirement (frequent reordering) or reaches a judgement - it never says which is more appropriate, or why, for THIS specific scenario. It is descriptive rather than evaluative because it only states what each structure IS, never applying that knowledge to reach and support a conclusion about which one suits frequent reordering better - a linked list, because reordering only requires updating a few pointers rather than shifting every subsequent array element.)

Common mistake

Assuming a longer or more detailed answer automatically satisfies a higher-demand command word. A long, accurate description is still only a description — length is not the same as analysis or evaluation. What actually changes the demand is whether the answer reasons about why, weighs alternatives, or reaches a supported judgement, not how many sentences it contains.

Check your understanding

A question asks students to "Justify" a choice of a Python dictionary over a list for a phone-book lookup app. State, in one sentence, what a justify-command answer must include that a describe-command answer would not. (A justify answer must give a specific reason FOR the stated choice, weighed against the alternative and the actual requirement (e.g. fast lookup by name) - a describe answer would only need to state what a dictionary or list IS, without needing to argue for choosing one over the other.)

Challenge

Choose any three command words from this lesson. Write one short, original question stem for each (different topics, drawn from anywhere across the whole course) that is genuinely written to that command word's demand — not simply the same question with the word swapped.

Looking ahead: the next two lessons apply this command-word awareness directly to Paper 1 (practical, programming-focused) and Paper 2 (theory, extended-response) examination technique.