Software Engineering › Key terms › Y11 OOP › Object-oriented programming (OOP)
Object-oriented programming (OOP)
Term Y11 OOP
Definition
A paradigm that organises a program as objects, created from classes, that hold data (attributes) and behaviour (methods) and communicate by passing messages.
Example: Contrast: procedural = a list of subroutines acting on separate data; OOP = objects that own their data and methods.
Found in: syllabus, school notes, past SDD papers.
Where it is used in the test
Syllabus area: Y11 OOP.
Question types it can appear in
- Multiple choice: Pick the option that matches the definition or example.
- Matching or table: Match OOP features to descriptions
- Short answer: Compare procedural programming with OOP
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
- Sample exam Q24 (4 marks): Modelling tools (class diagram) The Software Engineering Project (Part B) · 4 marks
- 2025 HSC Q22 (3 marks): Modelling tools The Software Engineering Project (Part A) · 3 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: Object-oriented programming (OOP) in The Object-Oriented Paradigm (Year 11) · study that set
- Memorise: Object-oriented concepts
- Notes: Design, develop and apply ML regression models using an OOP to predict numeric values,… (Software Automation (Year 12))
- Notes: OOP, imperative, logic and functional Programmingc Paradigms (Year 11 content (Programming fundamentals, OOP, Mechatronics))
- Notes: Compare Object-Relational Mapping (ORM) to SQL. (Programming for the Web (Year 12))
- Notes: Apply neural network models using an OOP to make predictions. (Software Automation (Year 12))
How to use it in an answer
A model sentence
“A paradigm that organises a program as objects, created from classes, that hold data (attributes) and behaviour (methods) and communicate by passing messages.” Then apply it: Contrast: procedural = a list of subroutines acting on separate data; OOP = objects that own their data and methods.
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 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.
- 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
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).
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.
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: Class · Object · Attribute · Method · Constructor (__init__) · Encapsulation · Abstraction · Inheritance · Generalisation · Superclass and subclass · Polymorphism · Method overriding · Message passing · Procedural programming v OOP