Software Engineering › Key terms › Y11 Programming Fundamentals › Desk checking
Desk checking
Term Y11 Programming Fundamentals
Definition
Manually stepping through an algorithm with sample data and recording variable values (a trace table) to check it works before coding.
Example: A trace table has a column for each variable and a row for each step.
Found in: syllabus, past SDD papers.
Where it is used in the test
Syllabus area: Y11 Programming Fundamentals.
Question types it can appear in
- Multiple choice: Pick the option that matches the definition or example.
- Short answer: Outline desk checking
- Code reading: Trace pseudocode
Where it has appeared in the paper
The Software Engineering Project (Part D). Part letters follow each paper’s own layout.
Related past questions
- 2022 Software Design and Development HSC Q28 (6 marks): Desk check and debugging an algorithm The Software Engineering Project (Part D) · 6 marks · old syllabus
- 2023 Software Design and Development HSC Q28 (6 marks): Desk check and debugging (validation) The Software Engineering Project (Part D) · 6 marks · old syllabus
These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.
Other questions that mention it
- 2021 Software Design and Development Q28 The Software Engineering Project (Part D) · 5 marks · old syllabus
Study links
- Flashcard: Desk checking in Programming Fundamentals (Year 11) · study that set
- Memorise: Software development steps and algorithm design
- Notes: Debugging tools and error types (The Software Engineering Project (Year 12))
- Master answer: sdd2021-q28 (5 marks, short answer / extended) (Master model answers: The Software Engineering Project (written answers))
- Master answer: sdd2022-q28 (6 marks, short answer / extended) (Master model answers: The Software Engineering Project (written answers))
How to use it in an answer
A model sentence
“Manually stepping through an algorithm with sample data and recording variable values (a trace table) to check it works before coding.” Then apply it: A trace table has a column for each variable and a row for each step.
In a short answer, give the definition in your own words first, then tie it to the situation in the question. Do not copy the example above unless it fits the scenario.
Command words used with it
- Identify: Recognise and name. (2023 Software Design and Development HSC Q28 (6 marks): Desk check and debugging (validation))
Technique for the question types
- Multiple choice: Read all four options, rule out wrong ones, pick one; no penalty for guessing so never leave blank.
- Short answer: One clear point per mark, use the stimulus and course terms, and answer the command word.
What the marking guidelines and feedback say
Old-syllabus question. Use for practice on the overlapping skill only. The new Software Engineering exam does not use the old SDD terms (e.g. CASE tools, system flowcharts, EBNF, assembly).
Old-syllabus question. Use for practice on the overlapping skill only. The new Software Engineering exam does not use the old SDD terms (e.g. CASE tools, system flowcharts, EBNF, assembly).
Common mistakes
- Use the term exactly as the syllabus words it, then link it to the scenario in the question; the 2025 feedback repeatedly rewards using the stimulus.
- Answer the command word: outline gives main points only, explain gives a reason or cause, discuss gives both sides.
Related terms
Same group in the syllabus: Computational thinking · Algorithm · Sequence · Selection · Iteration (repetition) · Divide and conquer · Backtracking · Top-down design · Bottom-up design · Abstraction · Refinement · Pseudocode · Flowchart · Subroutine (module, subprogram, procedure)