TK Study

Software Engineering › Key terms › Y11 OOP › Attribute

Attribute

Term Y11 OOP

Definition

A variable that belongs to an object and stores its data or state (name, age, balance).

Example: 'self.balance = 0' stores an attribute.

Found in: course specifications, 2025 HSC marking guidelines, sample exam and familiarisation guidelines, school notes, past SDD papers.

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.

Other questions that mention it

Study links

How to use it in an answer

A model sentence

General advice, built from the definition and example above

“A variable that belongs to an object and stores its data or state (name, age, balance).” Then apply it: 'self.balance = 0' stores an attribute.

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

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.
  • 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.
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 · Method · Constructor (__init__) · Encapsulation · Abstraction · Inheritance · Generalisation · Superclass and subclass · Polymorphism · Method overriding · Message passing · Procedural programming v OOP