Software Engineering › Key terms › Y12 Secure Software Architecture › Privacy
Privacy
Term Y12 Secure Software Architecture
Definition
The right of people to control how their personal information is collected, used and shared.
Example: Collect only the data needed.
Found in: syllabus, 2025 HSC marking guidelines, sample exam and familiarisation guidelines, school notes, past SDD papers.
Where it is used in the test
Syllabus area: Y12 Secure Software Architecture.
Question types it can appear in
- Multiple choice: Pick the option that matches the definition or example.
- Short answer: Define, outline or explain it and tie it to the scenario.
- Extended response: Use it as a supporting point linked to the stimulus.
Where it has appeared in the paper
Secure Software Architecture (Part A). Part letters follow each paper’s own layout.
Related past questions
- 2025 HSC Q16c (3 marks): Privacy by design Secure Software Architecture (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: Privacy in Secure Software Architecture (Year 12) · study that set
- Memorise: Fundamental software design security concepts (six words)
How to use it in an answer
A model sentence
“The right of people to control how their personal information is collected, used and shared.” Then apply it: Collect only the data needed.
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
- Describe: Provide characteristics and features. (2025 HSC Q16c (3 marks): Privacy by design)
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.
- Short answer: One clear point per mark, use the stimulus and course terms, and answer the command word.
- Extended response: Plan with the command word, give a judgement or explanation supported by named details from the stimulus, use course terms and cover both sides when asked.
What the marking guidelines and feedback say
Marker feedback: understand privacy by design (proactive not reactive; embed privacy into design; respect for user privacy) rather than generalising about privacy techniques; link to the scenario, e.g. live location data.
Worked answers from the marking guidelines
2025 HSC Q16c (3 marks): Privacy by design (3 marks): criteria and sample answer
Criteria
3: Describes ONE way privacy by design could be implemented in the weather app. 2: Outlines ONE feature of privacy by design. 1: Identifies a feature of privacy by design.
Sample answer
Embedded within the design of the weather app would be a process for regularly deleting identifiable data. For example, the app would likely record a person's live location to deliver relevant weather details. The privacy by design approach would incorporate a regular process to delete these locations from cache.
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: Confidentiality · Integrity · Availability · Authentication · Authorisation · Accountability · Regulatory compliance