Software Engineering › Key terms › Y11 OOP › Class
Class
Term Key terms bank Y11 OOP
Definition
A blueprint or template that defines the attributes and methods shared by all objects of one kind.
Example: 'class Student:' defines the template; each student is an object.
Found in: syllabus, course specifications, 2025 HSC marking guidelines, sample exam and familiarisation guidelines, school notes, past SDD papers.
Blueprint for objects.
Where it is used in the test
Syllabus area: Y11 OOP.
Question types it can appear in
- Drawing: class diagram box (name, attributes, methods)
- Python: class definition
- Multiple choice: Pick the option that matches the definition or example.
- Fill in the blanks: Choose this term to complete a statement or table.
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
- 2025 HSC Q22 (3 marks): Modelling tools The Software Engineering Project (Part A) · 3 marks
- Sample exam Q24 (4 marks): Modelling tools (class diagram) The Software Engineering Project (Part B) · 4 marks
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: Class in The Object-Oriented Paradigm (Year 11) · study that set
- Memorise: Object-oriented concepts
- Key terms bank entry: Class
How to use it in an answer
A model sentence
“A blueprint or template that defines the attributes and methods shared by all objects of one kind.” Then apply it: 'class Student:' defines the template; each student is an object.
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.
Technique for the question types
- Drawing: Use the online drawing tool: label every symbol and arrow, use the correct symbols from the specification, and add every required item.
- Python: Write code that runs: indentation, quotes, define functions before calling them, print the required output, meet every listed requirement.
- Multiple choice: Read all four options, rule out wrong ones, pick one; no penalty for guessing so never leave blank.
- Fill in the blanks: Choose the right word from a list; use exact syllabus terms.
What the marking guidelines and feedback say
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.
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
- Drawing questions (2025 HSC exam Q22): refine attributes into separate inherited classes; use appropriate class diagram symbols.
- Python questions (2025 HSC exam Q19): process string inputs; use a selection structure; code must execute in the environment; use correct indentation; call functions in the main program after defining them.
- Python questions (2025 HSC exam Q26): replicate the grid; use the random library; use selection and looping to access the list; include a method of checking the number of values; use meaningful variable names and constants; avoid overly complex structures such as nested IF loops.
- 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: Object-oriented programming (OOP) · Object · Attribute · Method · Constructor (__init__) · Encapsulation · Abstraction · Inheritance · Generalisation · Superclass and subclass · Polymorphism · Method overriding · Message passing · Procedural programming v OOP