Applying a naming convention to code structures
A consistent rule for naming code structures: snake_case verbs for functions and methods (get_total), CamelCase nouns for classes (StudentRecord). Pick one style and stick to it.
Understanding Applying a naming convention to code structures in VCE Software Development U3O1
What it does: get_total is lowercase with an underscore and begins with the verb get, so it matches the convention for functions and methods. Functions do something, so they get a verb name in snake_case, like calculate_average. A bare noun in CamelCase looks like a class. Class names use CamelCase, with each word starting with a capital letter and no underscores. Naming conventions don't change how fast the code runs. They make the structure of the code predictable for anyone who reads or maintains it.
Common mistakes: Methods use snake_case, not CamelCase. CamelCase is for class names. It should be def add_funds(self, amt):. Module names use lowercase snake_case, not CamelCase. It should be from string_utils import clean.
Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.
This module's key terms are also in a printable crossword (Modules 48–71) and word search (Modules 10–71).
Take this worksheet further — free with Cloodit
Each concept is reinforced from every angle — learned, then applied, then tested.
Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.
Over 100 of them, across seven natural biomes.
Turns their work into revision material ready for Flash Cards and Exam study.
Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.
Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.
Quick Questions
Match the Pairs
Key Term
naming conventionFill in the Blanks
Spot the Error
Student with a class code? Join your class →