Software Engineering › Key terms › Y11 Programming Fundamentals › Quality criteria for evaluating code
Quality criteria for evaluating code
Term Y11 Programming Fundamentals
Definition
The syllabus tests solutions against four qualities: functionality, performance, readability of code and quality of documentation.
Example: Mention all four when asked how you would evaluate or test code.
Found in: syllabus, 2025 HSC marking guidelines, sample exam and familiarisation 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.
- Short answer: Evaluate a solution
- Extended response: Use it as a supporting point linked to the stimulus.
Where it has appeared in the paper
The Software Engineering Project (Part D). Part letters follow each paper’s own layout.
Related past questions
- 2023 Software Design and Development HSC Q26 (9 marks): Code reading, maintainability and testing The Software Engineering Project (Part D) · 9 marks · old syllabus
- 2023 Software Design and Development HSC Q27 (10 marks): User interface, structure chart, quality assurance The Software Engineering Project (Part D) · 10 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.
Study links
- Flashcard: Quality criteria for evaluating code in Programming Fundamentals (Year 11) · study that set
- Memorise: Testing and code quality (Year 11)
How to use it in an answer
A model sentence
“The syllabus tests solutions against four qualities: functionality, performance, readability of code and quality of documentation.” Then apply it: Mention all four when asked how you would evaluate or test code.
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
- Explain: Relate cause and effect; make the relationship between things evident; provide why and/or how. (2023 Software Design and Development HSC Q26 (9 marks): Code reading, maintainability and testing)
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.
- Extended response: Plan with the command word, give a judgement or explanation supported by named details from the stimulus, use course terms and cover both sides when asked.
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: Syntax error · Logic 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