Software Engineering › Key terms › Y11 Programming Fundamentals › Peer checking
Peer checking
Term Y11 Programming Fundamentals
Definition
Another person reviews the algorithm or code to find errors you may have missed.
Example: Contrast: desk checking is by the author; peer checking is by someone else.
Found in: syllabus.
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: Compare desk checking with peer checking
No past question in this bank is linked to this term yet. It can still be tested through the question types above.
Study links
- Flashcard: Peer 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))
How to use it in an answer
A model sentence
“Another person reviews the algorithm or code to find errors you may have missed.” Then apply it: Contrast: desk checking is by the author; peer checking is by someone else.
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
No linked question shows the command word for this term. Across the past short answer questions in this bank the words used most are: Explain, Outline, Describe, Compare, Classify, Analyse. Check the actual word in your question.
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.
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)