Software Engineering › Key terms › Y12 Secure Software Architecture › Accountability
Accountability
Term Key terms bank Y12 Secure Software Architecture
Definition
Being able to trace actions to a user or system through logs and audit trails, so people answer for what they did.
Example: An audit log records who changed a record.
Found in: syllabus, school notes.
Actions are traceable to a person (logs).
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.
- Matching or table: Match it to its description, example or category.
- Fill in the blanks: Choose this term to complete a statement or table.
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 Q23c (3 marks): Fundamental software design security concepts 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: Accountability in Secure Software Architecture (Year 12) · study that set
- Memorise: Fundamental software design security concepts (six words)
- Key terms bank entry: Accountability
- Notes: When developing programming code, explore fundamental software design security concepts,… (Secure Software Architecture (Year 12))
- Notes: Fundamental software design security concepts (six words) (Secure Software Architecture (Year 12))
- Notes: Project management, communication and ethics (The Software Engineering Project (Year 12))
How to use it in an answer
A model sentence
“Being able to trace actions to a user or system through logs and audit trails, so people answer for what they did.” Then apply it: An audit log records who changed a record.
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.
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).
- Fill in the blanks: Choose the right word from a list; use exact syllabus terms.
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 · Privacy · Regulatory compliance