Software Engineering › Key terms › Y11 Programming Fundamentals › Maintenance
Maintenance
Process Term Y11 Programming Fundamentals Y12 SE Project
Definition
Maintenance Y11 Programming Fundamentals Process
Changes made after release to keep software working and useful: corrective (fix errors), adaptive (new environment) and perfective (improve or add features).
Example: A patch to fix a crash is corrective maintenance.
Found in: syllabus, school notes, past SDD papers.
Maintenance Y12 SE Project Term
Updating the software after release to fix errors, add features or adapt to change.
Example: Release a patch for a security bug.
Found in: syllabus, school notes, past SDD papers.
Where it is used in the test
Syllabus area: Y11 Programming Fundamentals Y12 SE Project.
Question types it can appear in
- Multiple choice: Pick the option that matches the definition or example.
- Matching or table: Match each type of maintenance to an 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 D). Part letters follow each paper’s own layout.
Related past questions
- 2022 Software Design and Development HSC Q22 (6 marks): Maintenance The Software Engineering Project (Part D) · 6 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: Maintenance in Programming Fundamentals (Year 11) · study that set
- Flashcard: Maintenance in The Software Engineering Project (Year 12) · study that set
- Memorise: Software development steps and algorithm design
- Memorise: Define and analyse the requirements of a problem
How to use it in an answer
A model sentence
“Changes made after release to keep software working and useful: corrective (fix errors), adaptive (new environment) and perfective (improve or add features).” Then apply it: A patch to fix a crash is corrective maintenance.
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. (2022 Software Design and Development HSC Q22 (6 marks): Maintenance)
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.
- Matching or table: Tick or match each statement to the right column (for example ORM v SQL, SAST v DAST).
- 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
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: Software development steps (the order) · Requirements definition · Determining specifications · Design · Development · Integration · Testing and debugging · Installation · Online code collaboration tools · Requirements · Need or opportunity · Feasibility · Functionality and performance requirements · Boundaries