TK Study

Software Engineering › Key terms › Y11 OOP › Generalisation

Generalisation

Term Key terms bank Y11 OOP

Definition

Moving the features shared by several classes up into a common superclass (Student and Teacher generalised as Person). The 2025 marker note: refine attributes into separate inherited classes.

Example: Common attributes go in the superclass; unique ones stay in each subclass.

Found in: syllabus, school notes.

Short version to memorise (key terms bank)

Common features pulled up into a superclass.

Where it is used in the test

Syllabus area: Y11 OOP.

Question types it can appear in

Where it has appeared in the paper

The Software Engineering Project (Part A, B). Part letters follow each paper’s own layout.

Related past questions

These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.

Study links

How to use it in an answer

A model sentence

General advice, built from the definition and example above

“Moving the features shared by several classes up into a common superclass (Student and Teacher generalised as Person).” Then apply it: Common attributes go in the superclass; unique ones stay in each subclass.

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

General advice

No linked question shows the command word for this term. Across the past drawing and short answer 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

What the marking guidelines and feedback say

2025 HSC Q22 (3 marks): Modelling tools

Technique: move attributes shared by several classes up into a parent (superclass) and draw an inheritance arrow from each subclass to the parent; leave only unique attributes in subclasses. Marker feedback: refine attributes into separate inherited classes; use appropriate class diagram symbols.

Sample exam Q24 (4 marks): Modelling tools (class diagram)

A reasoned design (NOT the NESA diagram): classes Trip(tripID; assignTicket()), PassengerCar(carModelCode), Engine(engineModelCode), Area(areaType, numSeats) with subclasses Executive (20 seats) and Standard (400 seats), Passenger(email, phone; buyTicket()) with subclass FrequentTraveller(loyalty info), Ticket(ticketType, seatNumber). Relationships: Trip 1 to many PassengerCar; Trip 1 to 1 Engine; Trip 1 to 2 Area; Passenger 1 to 0..* Ticket; Ticket * to 1 Trip. Show multiplicities and inheritance arrows (hollow triangle).

Common mistakes

Marker feedback on other questions of the same type (code and diagram feedback often applies across questions)
  • Drawing questions (2025 HSC exam Q22): refine attributes into separate inherited classes; use appropriate class diagram symbols.
General advice
  • 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.

Same group in the syllabus: Object-oriented programming (OOP) · Class · Object · Attribute · Method · Constructor (__init__) · Encapsulation · Abstraction · Inheritance · Superclass and subclass · Polymorphism · Method overriding · Message passing · Procedural programming v OOP