Software Engineering › Key terms › Y11 Programming Fundamentals › Logic error
Logic error
Term Y11 Programming Fundamentals
Definition
The program runs but gives the wrong result because the algorithm is wrong, for example using > instead of >=. 2025 markers said students confused these with syntax errors.
Example: Average = total / 2 instead of total / count.
Found in: 2025 HSC marking guidelines, school notes, 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.
- Fill in the blanks: Choose this term to complete a statement or table.
- Short answer: Outline how a debugging tool finds logic errors
- Code reading: Code or algorithm reading: interpret a fragment and state its output or purpose.
Where it has appeared in the paper
The Software Engineering Project (Part A). Part letters follow each paper’s own layout.
Related past questions
- 2025 HSC Q15b (3 marks): Testing and debugging The Software Engineering Project (Part A) · 3 marks
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
- 2022 Software Design and Development Q28 The Software Engineering Project (Part D) · 6 marks · old syllabus
Study links
- Flashcard: Logic error in Programming Fundamentals (Year 11) · study that set
- Memorise: Testing and code quality (Year 11)
- Notes: Debugging tools and error types (The Software Engineering Project (Year 12))
- Notes: Errors (Year 11 content (Programming fundamentals, OOP, Mechatronics))
- Master answer: sdd2022-q28 (6 marks, short answer / extended) (Master model answers: The Software Engineering Project (written answers))
- Master answer: hsc2025-q15b (3 marks, short answer) (Master model answers: The Software Engineering Project (written answers))
How to use it in an answer
A model sentence
“The program runs but gives the wrong result because the algorithm is wrong, for example using > instead of >=.” Then apply it: Average = total / 2 instead of total / count.
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
- Outline: Sketch in general terms; indicate the main features of. (2025 HSC Q15b (3 marks): Testing and debugging)
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.
- Fill in the blanks: Choose the right word from a list; use exact syllabus terms.
- 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
Marker feedback: identify two debugging tools used for LOGIC errors; distinguish logic from syntax errors; distinguish manual testing from software debugging tools.
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: Quality criteria for evaluating code · Syntax error · Runtime error · Debugging tools · Breakpoint · Single line stepping · Watch window (variable watch) · Debugging output statements · Boundary values · Path coverage · Faulty and abnormal data · Code optimisation