Software Engineering › Key terms › Y12 Secure Software Architecture › Code review
Code review
Term Key terms bank Y12 Secure Software Architecture
Definition
Other developers read the source code to find errors, security flaws and poor practice before release.
Example: Peer review spots missing input validation.
Found in: syllabus, school notes.
People read code to find flaws.
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.
- Matching or table: Match it to its description, example or category.
Where it has appeared in the paper
The Software Engineering Project (Part B). Part letters follow each paper’s own layout.
Related past questions
- Sample exam Q4 (1 mark): Collaboration The Software Engineering Project (Part B) · 1 mark
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: Code review in Secure Software Architecture (Year 12) · study that set
- Memorise: Test and evaluate security and resilience
- Key terms bank entry: Code review
- Notes: Apply and evaluate strategies used by software developers to manage the security of… (Secure Software Architecture (Year 12))
- Notes: Code security strategies: code review, SAST, DAST, vulnerability assessment, pen testing (Secure Software Architecture (Year 12))
- Notes: Test and evaluate security and resilience (Secure Software Architecture (Year 12))
- Notes: Interpret and apply fundamental software development steps to develop secure code,… (Secure Software Architecture (Year 12))
How to use it in an answer
A model sentence
“Other developers read the source code to find errors, security flaws and poor practice before release.” Then apply it: Peer review spots missing input validation.
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
No linked question shows the command word for this term. Across the past short answer questions in this bank the words used most are: Explain, Outline, Describe, Compare, Classify, Analyse. Check the actual word in your question.
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.
- Matching or table: Tick or match each statement to the right column (for example ORM v SQL, SAST v DAST).
Worked answers from the marking guidelines
Sample exam Q4 (1 mark): Collaboration (1 mark): criteria and sample answer
Criteria
1: Correctly identifies the benefits.
Sample answer
Different points of view can be considered. Tasks can be delegated to those with expertise.
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: Determining vulnerabilities · Hardening systems · Handling breaches · Business continuity · Disaster recovery · Static application security testing (SAST) · Dynamic application security testing (DAST) · Vulnerability assessment · Penetration testing