Software Engineering › Key terms › Y11 Programming Fundamentals › Debugging output statements
Debugging output statements
Term Y11 Programming Fundamentals
Definition
Print statements added to show that a section was reached or the value of a variable.
Example: print("total =", total)
Found in: syllabus, 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
- Short answer: Name one software debugging tool
- Python: Write or complete it in the online Python tool.
- Fill in the blanks: Choose this term to complete a statement or table.
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
- 2024 Software Design and Development Q28 The Software Engineering Project (Part D) · 3 marks · old syllabus
Study links
- Flashcard: Debugging output statements in Programming Fundamentals (Year 11) · study that set
- Memorise: Testing and code quality (Year 11)
- Master answer: sdd2024-q28 (3 marks, short answer / extended) (Master model answers: The Software Engineering Project (written answers))
- Notes: Debugging tools and error types (The Software Engineering Project (Year 12))
- Notes: Part 3. Where this has been examined (see ../../question_bank.md) (The Software Engineering Project (Year 12))
- Master answer: Topics in this module (Master model answers: The Software Engineering Project (written answers))
How to use it in an answer
A model sentence
“Print statements added to show that a section was reached or the value of a variable.” Then apply it: print("total =", total)
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
- Short answer: One clear point per mark, use the stimulus and course terms, and answer the command word.
- Python: Write code that runs: indentation, quotes, define functions before calling them, print the required output, meet every listed requirement.
- Fill in the blanks: Choose the right word from a list; use exact syllabus terms.
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
- Python questions (2025 HSC exam Q19): process string inputs; use a selection structure; code must execute in the environment; use correct indentation; call functions in the main program after defining them.
- Python questions (2025 HSC exam Q26): replicate the grid; use the random library; use selection and looping to access the list; include a method of checking the number of values; use meaningful variable names and constants; avoid overly complex structures such as nested IF loops.
- 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 · Logic error · Runtime error · Debugging tools · Breakpoint · Single line stepping · Watch window (variable watch) · Boundary values · Path coverage · Faulty and abnormal data · Code optimisation