TK Study

Software Engineering › Key terms › Y12 Secure Software Architecture › Intellectual property

Intellectual property

Term Y12 Secure Software Architecture

Definition

Creations of the mind (code, designs, brands) that are legally owned and protected by the creator.

Example: Protect the app's source code as IP.

Found in: syllabus, school notes, past SDD papers.

Where it is used in the test

Syllabus area: Y12 Secure Software Architecture.

Question types it can appear in

Where it has appeared in the paper

Secure Software Architecture (Part D). 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

“Creations of the mind (code, designs, brands) that are legally owned and protected by the creator.” Then apply it: Protect the app's source code as IP.

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

From the linked past questions
  • Describe: Provide characteristics and features. (2022 Software Design and Development HSC Q21 (3 marks): Social, ethical and legal responsibilities)

Technique for the question types

What the marking guidelines and feedback say

2022 Software Design and Development HSC Q21 (3 marks): Social, ethical and legal responsibilities

Old-syllabus question. Use for practice on the overlapping skill only. The new Software Engineering exam does not use the old SDD terms (e.g. CASE tools, system flowcharts, EBNF, assembly).

Common mistakes

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: Benefits of collaboration (secure development) · Benefits to an enterprise of secure development · Social, ethical and legal issues · Employment (impact) · Copyright · Digital disruption · Programmed backup · Software development steps for secure code (order) · SQL injection · General Data Protection Regulation (GDPR)

← IntegrityIn Y12 Secure Software ArchitectureInvalid forwarding and redirecting →