Software Engineering › Key terms › Y11 Programming Fundamentals › Code optimisation
Code optimisation
Term Y11 Programming Fundamentals
Definition
Improving the speed or memory use of working code (better algorithm, fewer repeated calculations, built-in functions).
Example: See language-dependent and language-independent optimisation.
Found in: syllabus, 2025 HSC marking guidelines, school notes.
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: Define, outline or explain it and tie it to the scenario.
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 Q4 (1 mark): Optimisation The Software Engineering Project (Part A) · 1 mark
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: Code optimisation in Programming Fundamentals (Year 11) · study that set
- Memorise: Testing and code quality (Year 11)
- Notes: Maintenance, version control, stubs and drivers, optimisation (The Software Engineering Project (Year 12))
How to use it in an answer
A model sentence
“Improving the speed or memory use of working code (better algorithm, fewer repeated calculations, built-in functions).” Then apply it: See language-dependent and language-independent optimisation.
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. (2025 HSC Q4 (1 mark): Optimisation)
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: Quality criteria for evaluating code · 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