Intellectual property in software you write
The legal right of the person who writes original code to control who can copy, share or sell it. Others need the owner's permission, even for a classmate's code.
Understanding Intellectual property in software you write in VCE Software Development U4O2
What it does: Naming yourself as author and owner records that you hold the copyright in your own original code. Being shown code does not give you the right to copy it. Copying a classmate's code without permission breaches their copyright and is also academic misconduct. Code written for a client can belong to the client if the agreement says so. Always check the contract before reusing that code. Ownership stays with the person who wrote the original code, no matter who has a copy of it.
Common mistakes: The person who writes original code usually owns the copyright, so the author of your own code should have owns_copyright = True. == compares values, so owner is never created and print() fails. Use a single = to store "me" as the owner of your own code.
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 97–130) and word search (Modules 49–130).
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
copyrightFill in the Blanks
Spot the Error
Student with a class code? Join your class →