A trace table is a disciplined record of state change. The learner follows the algorithm in execution order, updates only the values changed by the current statement, preserves every other live value, evaluates conditions from the present state and records output only when the algorithm produces it. The table is therefore a model of a running process, not a decorative rewrite of the code.
For Cambridge IGCSE Computer Science 0478 examinations in 2026, 2027 and 2028, the official syllabus includes completing a trace table to document a dry-run of an algorithm, including variables, outputs and user prompts at each step. This guide uses original algorithms and examples. It does not reproduce or predict examination questions, and it keeps the current paper-based syllabus distinct from the revised 2029 course.
Find your next learning step
A practical guide to Cambridge IGCSE Computer Science 0478 trace tables: dry-run algorithms one executed statement at a time, preserve variable state, record outputs and prompts, diagnose loop errors and transfer the method to unfamiliar code.
ROUTE 1 · CHAPTERS 1–3
Understand the task
Identify the task boundary and the first decisions.
ROUTE 2 · CHAPTERS 4–6
Build the mechanism
Work through the process from first principles.
ROUTE 3 · CHAPTERS 7–9
Use evidence precisely
Connect detail to a defensible result.
ROUTE 4 · CHAPTERS 10–12
Diagnose and transfer
Repair causes and test changed contexts.
ROUTE 5 · CHAPTERS 13–15
Practise and verify
Build a loop and keep source boundaries visible.
Full chapter index · Independent learning check · Education parent guide
Full chapter index
Understand the task · Chapters 1–3
Build the mechanism · Chapters 4–6
Use evidence precisely · Chapters 7–9
Diagnose and transfer · Chapters 10–12
Practise and verify · Chapters 13–15
This chapter focuses on treat the table as a state timeline. Each row records an execution event and what is true now, not the final answer copied backward.
Mechanism. Each row records an execution event and what is true now, not the final answer copied backward. The learner should make the state of the problem visible before using a technique. This turns a remembered rule into a chain of decisions that another reader can inspect. The explanation should identify what information enters the step, what transformation occurs and what result becomes available for the next step.
Worked case. total starts at zero, then total←total+price reads the old total and stores a new one. After reaching the result, explain why the step was justified and what evidence would have changed it. That second explanation prevents a correct-looking answer from becoming a lucky routine. It also gives a teacher a precise place to test understanding.
Changed context. Replace one important feature of the case while keeping the underlying decision. Ask what remains stable and what must change. Transfer is demonstrated when the learner preserves the reasoning mechanism without copying surface language, numbers or labels from the first example. A useful comparison names both the invariant decision and the changed evidence.
Failure and repair. Columns are filled with final values. Trace statement order. The repair should be used immediately on a near case and then on a farther case. The near case confirms the correction; the farther case checks whether the learner understands the cause rather than the appearance of the original mistake.
Action. Point to the current line before writing a row. A useful feedback note names the decision, cites the evidence and gives the next small task. It does not merely report that the answer was wrong. Over time, this creates an error history that distinguishes a one-off slip from a recurring misconception.
Student, parent and teacher roles. The student owns the explanation and records the error cause. The teacher chooses the smallest task that can expose the cause and checks a changed case. The parent can protect regular practice, ask the learner to explain the decision aloud and avoid supplying a polished answer that hides the learner's current model.
Evidence boundary. This case is illustrative and original. It demonstrates a reasoning process, not a guaranteed examination response or score. The learner should follow current official instructions and keep each claim within what the prompt, text, design or algorithm can support.
This chapter focuses on separate assignment from equality. Assignment reads current right-side values, computes and stores on the left.
Mechanism. Assignment reads current right-side values, computes and stores on the left. The learner should make the state of the problem visible before using a technique. This turns a remembered rule into a chain of decisions that another reader can inspect. The explanation should identify what information enters the step, what transformation occurs and what result becomes available for the next step.
Worked case. With count 3, count←count+1 reads 3 and stores 4; it is not the equation 3=4. After reaching the result, explain why the step was justified and what evidence would have changed it. That second explanation prevents a correct-looking answer from becoming a lucky routine. It also gives a teacher a precise place to test understanding.
Changed context. Replace one important feature of the case while keeping the underlying decision. Ask what remains stable and what must change. Transfer is demonstrated when the learner preserves the reasoning mechanism without copying surface language, numbers or labels from the first example. A useful comparison names both the invariant decision and the changed evidence.
Failure and repair. Learners update before evaluating. Use read, compute, write. The repair should be used immediately on a near case and then on a farther case. The near case confirms the correction; the farther case checks whether the learner understands the cause rather than the appearance of the original mistake.
Action. Annotate old and new values on self-referential assignments. A useful feedback note names the decision, cites the evidence and gives the next small task. It does not merely report that the answer was wrong. Over time, this creates an error history that distinguishes a one-off slip from a recurring misconception.
Student, parent and teacher roles. The student owns the explanation and records the error cause. The teacher chooses the smallest task that can expose the cause and checks a changed case. The parent can protect regular practice, ask the learner to explain the decision aloud and avoid supplying a polished answer that hides the learner's current model.
Evidence boundary. This case is illustrative and original. It demonstrates a reasoning process, not a guaranteed examination response or score. The learner should follow current official instructions and keep each claim within what the prompt, text, design or algorithm can support.
This chapter focuses on preserve unchanged values. Variables retain values until later assignments change them; a new row does not reset the machine.
Mechanism. Variables retain values until later assignments change them; a new row does not reset the machine. The learner should make the state of the problem visible before using a technique. This turns a remembered rule into a chain of decisions that another reader can inspect. The explanation should identify what information enters the step, what transformation occurs and what result becomes available for the next step.
Worked case. If score remains 12 while lives falls from 3 to 2, the state still contains score 12. After reaching the result, explain why the step was justified and what evidence would have changed it. That second explanation prevents a correct-looking answer from becoming a lucky routine. It also gives a teacher a precise place to test understanding.
Changed context. Replace one important feature of the case while keeping the underlying decision. Ask what remains stable and what must change. Transfer is demonstrated when the learner preserves the reasoning mechanism without copying surface language, numbers or labels from the first example. A useful comparison names both the invariant decision and the changed evidence.
Failure and repair. Stable values are erased or blanks become ambiguous. Set a clear convention. The repair should be used immediately on a near case and then on a farther case. The near case confirms the correction; the farther case checks whether the learner understands the cause rather than the appearance of the original mistake.
Action. Highlight changed cells while still reading the full state. A useful feedback note names the decision, cites the evidence and gives the next small task. It does not merely report that the answer was wrong. Over time, this creates an error history that distinguishes a one-off slip from a recurring misconception.
Student, parent and teacher roles. The student owns the explanation and records the error cause. The teacher chooses the smallest task that can expose the cause and checks a changed case. The parent can protect regular practice, ask the learner to explain the decision aloud and avoid supplying a polished answer that hides the learner's current model.
Evidence boundary. This case is illustrative and original. It demonstrates a reasoning process, not a guaranteed examination response or score. The learner should follow current official instructions and keep each claim within what the prompt, text, design or algorithm can support.
This chapter focuses on evaluate present-state conditions. A branch or loop test uses values existing at that moment and controls the next path.
Mechanism. A branch or loop test uses values existing at that moment and controls the next path. The learner should make the state of the problem visible before using a technique. This turns a remembered rule into a chain of decisions that another reader can inspect. The explanation should identify what information enters the step, what transformation occurs and what result becomes available for the next step.
Worked case. attempts 2 and limit 3 makes attempts<limit true; after increment to 3 the next test is false. After reaching the result, explain why the step was justified and what evidence would have changed it. That second explanation prevents a correct-looking answer from becoming a lucky routine. It also gives a teacher a precise place to test understanding.
Changed context. Replace one important feature of the case while keeping the underlying decision. Ask what remains stable and what must change. Transfer is demonstrated when the learner preserves the reasoning mechanism without copying surface language, numbers or labels from the first example. A useful comparison names both the invariant decision and the changed evidence.
Failure and repair. The intended outcome replaces actual substitution. Record true or false. The repair should be used immediately on a near case and then on a farther case. The near case confirms the correction; the farther case checks whether the learner understands the cause rather than the appearance of the original mistake.
Action. Verbalise each test with current values. A useful feedback note names the decision, cites the evidence and gives the next small task. It does not merely report that the answer was wrong. Over time, this creates an error history that distinguishes a one-off slip from a recurring misconception.
Student, parent and teacher roles. The student owns the explanation and records the error cause. The teacher chooses the smallest task that can expose the cause and checks a changed case. The parent can protect regular practice, ask the learner to explain the decision aloud and avoid supplying a polished answer that hides the learner's current model.
Evidence boundary. This case is illustrative and original. It demonstrates a reasoning process, not a guaranteed examination response or score. The learner should follow current official instructions and keep each claim within what the prompt, text, design or algorithm can support.
This chapter focuses on trace one branch. Only the selected if or else branch executes; nested selection depends on reachability.
Mechanism. Only the selected if or else branch executes; nested selection depends on reachability. The learner should make the state of the problem visible before using a technique. This turns a remembered rule into a chain of decisions that another reader can inspect. The explanation should identify what information enters the step, what transformation occurs and what result becomes available for the next step.
Worked case. Age passes an outer test, consent fails an inner test and produces a waiting message; the outer alternative is skipped. After reaching the result, explain why the step was justified and what evidence would have changed it. That second explanation prevents a correct-looking answer from becoming a lucky routine. It also gives a teacher a precise place to test understanding.
Changed context. Replace one important feature of the case while keeping the underlying decision. Ask what remains stable and what must change. Transfer is demonstrated when the learner preserves the reasoning mechanism without copying surface language, numbers or labels from the first example. A useful comparison names both the invariant decision and the changed evidence.
Failure and repair. Both visible branches are executed. Draw the path. The repair should be used immediately on a near case and then on a farther case. The near case confirms the correction; the farther case checks whether the learner understands the cause rather than the appearance of the original mistake.
Action. Compare inputs that diverge at exactly one condition. A useful feedback note names the decision, cites the evidence and gives the next small task. It does not merely report that the answer was wrong. Over time, this creates an error history that distinguishes a one-off slip from a recurring misconception.
Student, parent and teacher roles. The student owns the explanation and records the error cause. The teacher chooses the smallest task that can expose the cause and checks a changed case. The parent can protect regular practice, ask the learner to explain the decision aloud and avoid supplying a polished answer that hides the learner's current model.
Evidence boundary. This case is illustrative and original. It demonstrates a reasoning process, not a guaranteed examination response or score. The learner should follow current official instructions and keep each claim within what the prompt, text, design or algorithm can support.
| Trace event | What to record | What to preserve |
|---|---|---|
| Assignment | New value after evaluating the right side | Variables not assigned |
| Condition | Result used to select the next path | Current state unless a branch changes it |
| Input | Prompt and supplied value | Prior state plus new input |
| Output | Value or message produced now | State unless code also assigns |
This chapter focuses on trace count-controlled loops. Initialization, test, body and update must appear in order; inclusive bounds control the last iteration.
Mechanism. Initialization, test, body and update must appear in order; inclusive bounds control the last iteration. The learner should make the state of the problem visible before using a technique. This turns a remembered rule into a chain of decisions that another reader can inspect. The explanation should identify what information enters the step, what transformation occurs and what result becomes available for the next step.
Worked case. For i from 1 to 3, output occurs at 1, 2 and 3 before termination. After reaching the result, explain why the step was justified and what evidence would have changed it. That second explanation prevents a correct-looking answer from becoming a lucky routine. It also gives a teacher a precise place to test understanding.
Changed context. Replace one important feature of the case while keeping the underlying decision. Ask what remains stable and what must change. Transfer is demonstrated when the learner preserves the reasoning mechanism without copying surface language, numbers or labels from the first example. A useful comparison names both the invariant decision and the changed evidence.
Failure and repair. An extra iteration appears or the last is omitted. List test, action and next value. The repair should be used immediately on a near case and then on a farther case. The near case confirms the correction; the farther case checks whether the learner understands the cause rather than the appearance of the original mistake.
Action. Number iterations and vary inclusive boundaries. A useful feedback note names the decision, cites the evidence and gives the next small task. It does not merely report that the answer was wrong. Over time, this creates an error history that distinguishes a one-off slip from a recurring misconception.
Student, parent and teacher roles. The student owns the explanation and records the error cause. The teacher chooses the smallest task that can expose the cause and checks a changed case. The parent can protect regular practice, ask the learner to explain the decision aloud and avoid supplying a polished answer that hides the learner's current model.
Evidence boundary. This case is illustrative and original. It demonstrates a reasoning process, not a guaranteed examination response or score. The learner should follow current official instructions and keep each claim within what the prompt, text, design or algorithm can support.
This chapter focuses on trace condition-controlled loops. While and repeat-until place their tests differently; a progress variable should move toward termination.
Mechanism. While and repeat-until place their tests differently; a progress variable should move toward termination. The learner should make the state of the problem visible before using a technique. This turns a remembered rule into a chain of decisions that another reader can inspect. The explanation should identify what information enters the step, what transformation occurs and what result becomes available for the next step.
Worked case. A balance loop subtracts payment and includes a final failed test even though the body does not run again. After reaching the result, explain why the step was justified and what evidence would have changed it. That second explanation prevents a correct-looking answer from becoming a lucky routine. It also gives a teacher a precise place to test understanding.
Changed context. Replace one important feature of the case while keeping the underlying decision. Ask what remains stable and what must change. Transfer is demonstrated when the learner preserves the reasoning mechanism without copying surface language, numbers or labels from the first example. A useful comparison names both the invariant decision and the changed evidence.
Failure and repair. The terminating test is omitted or termination is assumed. Identify progress. The repair should be used immediately on a near case and then on a farther case. The near case confirms the correction; the farther case checks whether the learner understands the cause rather than the appearance of the original mistake.
Action. State what change makes stopping inevitable. A useful feedback note names the decision, cites the evidence and gives the next small task. It does not merely report that the answer was wrong. Over time, this creates an error history that distinguishes a one-off slip from a recurring misconception.
Student, parent and teacher roles. The student owns the explanation and records the error cause. The teacher chooses the smallest task that can expose the cause and checks a changed case. The parent can protect regular practice, ask the learner to explain the decision aloud and avoid supplying a polished answer that hides the learner's current model.
Evidence boundary. This case is illustrative and original. It demonstrates a reasoning process, not a guaranteed examination response or score. The learner should follow current official instructions and keep each claim within what the prompt, text, design or algorithm can support.
This chapter focuses on separate counters and accumulators. Counters change by fixed amounts; accumulators add varying data and preserve a different invariant.
Mechanism. Counters change by fixed amounts; accumulators add varying data and preserve a different invariant. The learner should make the state of the problem visible before using a technique. This turns a remembered rule into a chain of decisions that another reader can inspect. The explanation should identify what information enters the step, what transformation occurs and what result becomes available for the next step.
Worked case. readingCount adds one while total adds each temperature before average is computed. After reaching the result, explain why the step was justified and what evidence would have changed it. That second explanation prevents a correct-looking answer from becoming a lucky routine. It also gives a teacher a precise place to test understanding.
Changed context. Replace one important feature of the case while keeping the underlying decision. Ask what remains stable and what must change. Transfer is demonstrated when the learner preserves the reasoning mechanism without copying surface language, numbers or labels from the first example. A useful comparison names both the invariant decision and the changed evidence.
Failure and repair. The item is added to the counter or one is added to the total. Name roles. The repair should be used immediately on a near case and then on a farther case. The near case confirms the correction; the farther case checks whether the learner understands the cause rather than the appearance of the original mistake.
Action. Label each variable with a one-sentence invariant. A useful feedback note names the decision, cites the evidence and gives the next small task. It does not merely report that the answer was wrong. Over time, this creates an error history that distinguishes a one-off slip from a recurring misconception.
Student, parent and teacher roles. The student owns the explanation and records the error cause. The teacher chooses the smallest task that can expose the cause and checks a changed case. The parent can protect regular practice, ask the learner to explain the decision aloud and avoid supplying a polished answer that hides the learner's current model.
Evidence boundary. This case is illustrative and original. It demonstrates a reasoning process, not a guaranteed examination response or score. The learner should follow current official instructions and keep each claim within what the prompt, text, design or algorithm can support.
This chapter focuses on record prompts, input and output. Prompts occur before input, supplied values then change state, and outputs appear exactly when executed.
Mechanism. Prompts occur before input, supplied values then change state, and outputs appear exactly when executed. The learner should make the state of the problem visible before using a technique. This turns a remembered rule into a chain of decisions that another reader can inspect. The explanation should identify what information enters the step, what transformation occurs and what result becomes available for the next step.
Worked case. Display Enter mark, receive 72, store it, then later output Pass as separate events. After reaching the result, explain why the step was justified and what evidence would have changed it. That second explanation prevents a correct-looking answer from becoming a lucky routine. It also gives a teacher a precise place to test understanding.
Changed context. Replace one important feature of the case while keeping the underlying decision. Ask what remains stable and what must change. Transfer is demonstrated when the learner preserves the reasoning mechanism without copying surface language, numbers or labels from the first example. A useful comparison names both the invariant decision and the changed evidence.
Failure and repair. All output is moved to the end and input appears magically. Trace interaction. The repair should be used immediately on a near case and then on a farther case. The near case confirms the correction; the farther case checks whether the learner understands the cause rather than the appearance of the original mistake.
Action. Role-play user and machine and provide values only after prompts. A useful feedback note names the decision, cites the evidence and gives the next small task. It does not merely report that the answer was wrong. Over time, this creates an error history that distinguishes a one-off slip from a recurring misconception.
Student, parent and teacher roles. The student owns the explanation and records the error cause. The teacher chooses the smallest task that can expose the cause and checks a changed case. The parent can protect regular practice, ask the learner to explain the decision aloud and avoid supplying a polished answer that hides the learner's current model.
Evidence boundary. This case is illustrative and original. It demonstrates a reasoning process, not a guaranteed examination response or score. The learner should follow current official instructions and keep each claim within what the prompt, text, design or algorithm can support.
This chapter focuses on separate array index and value. An index locates an element; the index variable, element and later update are distinct state.
Mechanism. An index locates an element; the index variable, element and later update are distinct state. The learner should make the state of the problem visible before using a technique. This turns a remembered rule into a chain of decisions that another reader can inspect. The explanation should identify what information enters the step, what transformation occurs and what result becomes available for the next step.
Worked case. names[2] is Kai and index is 2; output produces Kai, then incrementing index does not change the array. After reaching the result, explain why the step was justified and what evidence would have changed it. That second explanation prevents a correct-looking answer from becoming a lucky routine. It also gives a teacher a precise place to test understanding.
Changed context. Replace one important feature of the case while keeping the underlying decision. Ask what remains stable and what must change. Transfer is demonstrated when the learner preserves the reasoning mechanism without copying surface language, numbers or labels from the first example. A useful comparison names both the invariant decision and the changed evidence.
Failure and repair. Position and content are confused or one-based assumptions intrude. Draw boxes. The repair should be used immediately on a near case and then on a farther case. The near case confirms the correction; the farther case checks whether the learner understands the cause rather than the appearance of the original mistake.
Action. Annotate index-value pairs and use duplicate values to test understanding. A useful feedback note names the decision, cites the evidence and gives the next small task. It does not merely report that the answer was wrong. Over time, this creates an error history that distinguishes a one-off slip from a recurring misconception.
Student, parent and teacher roles. The student owns the explanation and records the error cause. The teacher chooses the smallest task that can expose the cause and checks a changed case. The parent can protect regular practice, ask the learner to explain the decision aloud and avoid supplying a polished answer that hides the learner's current model.
Evidence boundary. This case is illustrative and original. It demonstrates a reasoning process, not a guaranteed examination response or score. The learner should follow current official instructions and keep each claim within what the prompt, text, design or algorithm can support.
This chapter focuses on preserve outer state in nested loops. The outer variable remains fixed while the inner cycle completes, then the inner variable reinitialises.
Mechanism. The outer variable remains fixed while the inner cycle completes, then the inner variable reinitialises. The learner should make the state of the problem visible before using a technique. This turns a remembered rule into a chain of decisions that another reader can inspect. The explanation should identify what information enters the step, what transformation occurs and what result becomes available for the next step.
Worked case. For each row r, column c visits three cells; r stays fixed for those visits. After reaching the result, explain why the step was justified and what evidence would have changed it. That second explanation prevents a correct-looking answer from becoming a lucky routine. It also gives a teacher a precise place to test understanding.
Changed context. Replace one important feature of the case while keeping the underlying decision. Ask what remains stable and what must change. Transfer is demonstrated when the learner preserves the reasoning mechanism without copying surface language, numbers or labels from the first example. A useful comparison names both the invariant decision and the changed evidence.
Failure and repair. Both variables increment together. Use indentation and loop-entry rows. The repair should be used immediately on a near case and then on a farther case. The near case confirms the correction; the farther case checks whether the learner understands the cause rather than the appearance of the original mistake.
Action. Group trace rows by outer iteration. A useful feedback note names the decision, cites the evidence and gives the next small task. It does not merely report that the answer was wrong. Over time, this creates an error history that distinguishes a one-off slip from a recurring misconception.
Student, parent and teacher roles. The student owns the explanation and records the error cause. The teacher chooses the smallest task that can expose the cause and checks a changed case. The parent can protect regular practice, ask the learner to explain the decision aloud and avoid supplying a polished answer that hides the learner's current model.
Evidence boundary. This case is illustrative and original. It demonstrates a reasoning process, not a guaranteed examination response or score. The learner should follow current official instructions and keep each claim within what the prompt, text, design or algorithm can support.
This chapter focuses on use traces to diagnose defects. The first row where actual state diverges from intended state often identifies the faulty initialization, test, update or index.
Mechanism. The first row where actual state diverges from intended state often identifies the faulty initialization, test, update or index. The learner should make the state of the problem visible before using a technique. This turns a remembered rule into a chain of decisions that another reader can inspect. The explanation should identify what information enters the step, what transformation occurs and what result becomes available for the next step.
Worked case. A maximum initialized to zero fails for all-negative data because maximum never changes. After reaching the result, explain why the step was justified and what evidence would have changed it. That second explanation prevents a correct-looking answer from becoming a lucky routine. It also gives a teacher a precise place to test understanding.
Changed context. Replace one important feature of the case while keeping the underlying decision. Ask what remains stable and what must change. Transfer is demonstrated when the learner preserves the reasoning mechanism without copying surface language, numbers or labels from the first example. A useful comparison names both the invariant decision and the changed evidence.
Failure and repair. Only final output is inspected. Compare expected and actual state at every row. The repair should be used immediately on a near case and then on a farther case. The near case confirms the correction; the farther case checks whether the learner understands the cause rather than the appearance of the original mistake.
Action. Mark the first bad state before proposing a correction. A useful feedback note names the decision, cites the evidence and gives the next small task. It does not merely report that the answer was wrong. Over time, this creates an error history that distinguishes a one-off slip from a recurring misconception.
Student, parent and teacher roles. The student owns the explanation and records the error cause. The teacher chooses the smallest task that can expose the cause and checks a changed case. The parent can protect regular practice, ask the learner to explain the decision aloud and avoid supplying a polished answer that hides the learner's current model.
Evidence boundary. This case is illustrative and original. It demonstrates a reasoning process, not a guaranteed examination response or score. The learner should follow current official instructions and keep each claim within what the prompt, text, design or algorithm can support.
This chapter focuses on choose fault-revealing data. Normal, boundary, abnormal and extreme cases exercise different paths; one friendly case cannot expose every defect.
Mechanism. Normal, boundary, abnormal and extreme cases exercise different paths; one friendly case cannot expose every defect. The learner should make the state of the problem visible before using a technique. This turns a remembered rule into a chain of decisions that another reader can inspect. The explanation should identify what information enters the step, what transformation occurs and what result becomes available for the next step.
Worked case. For values allowed 1 to 10, use 1, 10, 0 and 11 to test boundaries and rejection. After reaching the result, explain why the step was justified and what evidence would have changed it. That second explanation prevents a correct-looking answer from becoming a lucky routine. It also gives a teacher a precise place to test understanding.
Changed context. Replace one important feature of the case while keeping the underlying decision. Ask what remains stable and what must change. Transfer is demonstrated when the learner preserves the reasoning mechanism without copying surface language, numbers or labels from the first example. A useful comparison names both the invariant decision and the changed evidence.
Failure and repair. Middle values repeat the same path. Map every case to the branch it targets. The repair should be used immediately on a near case and then on a farther case. The near case confirms the correction; the farther case checks whether the learner understands the cause rather than the appearance of the original mistake.
Action. Predict path coverage before executing. A useful feedback note names the decision, cites the evidence and gives the next small task. It does not merely report that the answer was wrong. Over time, this creates an error history that distinguishes a one-off slip from a recurring misconception.
Student, parent and teacher roles. The student owns the explanation and records the error cause. The teacher chooses the smallest task that can expose the cause and checks a changed case. The parent can protect regular practice, ask the learner to explain the decision aloud and avoid supplying a polished answer that hides the learner's current model.
Evidence boundary. This case is illustrative and original. It demonstrates a reasoning process, not a guaranteed examination response or score. The learner should follow current official instructions and keep each claim within what the prompt, text, design or algorithm can support.
This chapter focuses on transfer across notation. The method transfers, but operator, division, indexing and evaluation rules follow the presented language or notation.
Mechanism. The method transfers, but operator, division, indexing and evaluation rules follow the presented language or notation. The learner should make the state of the problem visible before using a technique. This turns a remembered rule into a chain of decisions that another reader can inspect. The explanation should identify what information enters the step, what transformation occurs and what result becomes available for the next step.
Worked case. 7 DIV 2 differs from ordinary division, and a Boolean short-circuit may skip a second test. After reaching the result, explain why the step was justified and what evidence would have changed it. That second explanation prevents a correct-looking answer from becoming a lucky routine. It also gives a teacher a precise place to test understanding.
Changed context. Replace one important feature of the case while keeping the underlying decision. Ask what remains stable and what must change. Transfer is demonstrated when the learner preserves the reasoning mechanism without copying surface language, numbers or labels from the first example. A useful comparison names both the invariant decision and the changed evidence.
Failure and repair. Rules from another language are imported. Build a notation glossary. The repair should be used immediately on a near case and then on a farther case. The near case confirms the correction; the farther case checks whether the learner understands the cause rather than the appearance of the original mistake.
Action. Test one unfamiliar expression before tracing the full algorithm. A useful feedback note names the decision, cites the evidence and gives the next small task. It does not merely report that the answer was wrong. Over time, this creates an error history that distinguishes a one-off slip from a recurring misconception.
Student, parent and teacher roles. The student owns the explanation and records the error cause. The teacher chooses the smallest task that can expose the cause and checks a changed case. The parent can protect regular practice, ask the learner to explain the decision aloud and avoid supplying a polished answer that hides the learner's current model.
Evidence boundary. This case is illustrative and original. It demonstrates a reasoning process, not a guaranteed examination response or score. The learner should follow current official instructions and keep each claim within what the prompt, text, design or algorithm can support.
This chapter focuses on keep the exam-year boundary. The 2026–2028 syllabus explicitly includes variables, outputs and prompts in dry-run trace tables; the 2029 revision changes the course and removes pseudocode references.
Mechanism. The 2026–2028 syllabus explicitly includes variables, outputs and prompts in dry-run trace tables; the 2029 revision changes the course and removes pseudocode references. The learner should make the state of the problem visible before using a technique. This turns a remembered rule into a chain of decisions that another reader can inspect. The explanation should identify what information enters the step, what transformation occurs and what result becomes available for the next step.
Worked case. These original examples support current reasoning without predicting a paper layout. After reaching the result, explain why the step was justified and what evidence would have changed it. That second explanation prevents a correct-looking answer from becoming a lucky routine. It also gives a teacher a precise place to test understanding.
Changed context. Replace one important feature of the case while keeping the underlying decision. Ask what remains stable and what must change. Transfer is demonstrated when the learner preserves the reasoning mechanism without copying surface language, numbers or labels from the first example. A useful comparison names both the invariant decision and the changed evidence.
Failure and repair. 2029 materials are mixed into 2027 preparation. Check syllabus code and year. The repair should be used immediately on a near case and then on a farther case. The near case confirms the correction; the farther case checks whether the learner understands the cause rather than the appearance of the original mistake.
Action. Label folders by exam year and verify the official syllabus before using materials. A useful feedback note names the decision, cites the evidence and gives the next small task. It does not merely report that the answer was wrong. Over time, this creates an error history that distinguishes a one-off slip from a recurring misconception.
Student, parent and teacher roles. The student owns the explanation and records the error cause. The teacher chooses the smallest task that can expose the cause and checks a changed case. The parent can protect regular practice, ask the learner to explain the decision aloud and avoid supplying a polished answer that hides the learner's current model.
Evidence boundary. This case is illustrative and original. It demonstrates a reasoning process, not a guaranteed examination response or score. The learner should follow current official instructions and keep each claim within what the prompt, text, design or algorithm can support.
Sources: Cambridge IGCSE Computer Science 0478 syllabus for 2026–2028 · Cambridge IGCSE Computer Science overview · Cambridge specimen and past-paper resources
Related reading: Education parent guide · Cambridge AS Computer Science fault-revealing test data · AP Computer Science A ArrayList removal