Software Engineering › Key terms › Y11 Programming Fundamentals › Abstraction
Abstraction
Term Key terms bank Y11 Programming Fundamentals Y11 OOP
Also listed as: Abstraction (in OOP)
Definition
Abstraction Y11 Programming Fundamentals Term
Hiding unnecessary detail so you focus on what matters, such as calling a subroutine without knowing how it works.
Example: Also an OOP principle (see Object-oriented card).
Found in: syllabus, course specifications, school notes, past SDD papers.
Abstraction (in OOP) Y11 OOP Term
Hiding complex implementation detail and exposing only what is needed, so a user calls account.deposit() without knowing how it works.
Example: The class hides how interest is calculated; the user just calls addInterest().
Found in: syllabus, course specifications, school notes, past SDD papers.
Hiding detail so only the essential features are shown.
Where it is used in the test
Syllabus area: Y11 Programming Fundamentals Y11 OOP.
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.
- Drawing: class diagram
- Matching or table: Match it to its description, example or category.
No past question in this bank is linked to this term yet. It can still be tested through the question types above.
Study links
- Flashcard: Abstraction in Programming Fundamentals (Year 11) · study that set
- Flashcard: Abstraction (in OOP) in The Object-Oriented Paradigm (Year 11) · study that set
- Memorise: Software development steps and algorithm design
- Memorise: Object-oriented concepts
- Key terms bank entry: Abstraction
- Notes: Generalisation and Abstraction (Year 11 content (Programming fundamentals, OOP, Mechatronics))
- Notes: Compare Object-Relational Mapping (ORM) to SQL. (Programming for the Web (Year 12))
- Notes: OOP, imperative, logic and functional Programmingc Paradigms (Year 11 content (Programming fundamentals, OOP, Mechatronics))
- Notes: SQL vs ORM (Programming for the Web (Year 12))
How to use it in an answer
A model sentence
“Hiding unnecessary detail so you focus on what matters, such as calling a subroutine without knowing how it works.” Then apply it: Also an OOP principle (see Object-oriented card).
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
No linked question shows the command word for this term. Across the past short answer and drawing questions in this bank the words used most are: Explain, Outline, Describe, Compare, Classify, Analyse. Check the actual word in your question.
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.
- Drawing: Use the online drawing tool: label every symbol and arrow, use the correct symbols from the specification, and add every required item.
- Matching or table: Tick or match each statement to the right column (for example ORM v SQL, SAST v DAST).
Common mistakes
- Drawing questions (2025 HSC exam Q22): refine attributes into separate inherited classes; use appropriate class diagram symbols.
- 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: Computational thinking · Algorithm · Sequence · Selection · Iteration (repetition) · Divide and conquer · Backtracking · Top-down design · Bottom-up design · Refinement · Pseudocode · Flowchart · Subroutine (module, subprogram, procedure) · Function v procedure