Software Engineering › Key terms › Y11 OOP › Version control
Version control
Term Key terms bank Y11 OOP Y12 Programming for the Web Y12 SE Project
Also listed as: Version control (web); Version control (project)
Definition
Version control Y11 OOP Term
A system (such as Git) that records every change to the code with who and when, supports branches and merging and allows rollback, so teams can work together safely.
Example: Git history lets the team revert to the last working version.
Found in: syllabus, school notes, past SDD papers.
Version control (web) Y12 Programming for the Web Term
Recording changes to files so you can see history, work in branches, merge and roll back; essential when several developers build a web app.
Example: Git branches let front-end and back-end work separately.
Found in: syllabus, school notes, past SDD papers.
Version control (project) Y12 SE Project Term
Keeping a history of file versions so changes can be tracked and undone and several people work together with branches and merges.
Example: Commit after each feature.
Found in: syllabus, school notes, past SDD papers.
Tracks changes, branches, merges and reverts code.
Where it is used in the test
Syllabus area: Y11 OOP Y12 Programming for the Web Y12 SE Project.
Question types it can appear in
- Multiple choice: Pick the option that matches the definition or example.
- Multi-select: Collaboration features (sample Q4)
- 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
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: Version control in The Object-Oriented Paradigm (Year 11) · study that set
- Flashcard: Version control (web) in Programming for the Web (Year 12) · study that set
- Flashcard: Version control (project) in The Software Engineering Project (Year 12) · study that set
- Memorise: Object-oriented concepts
- Memorise: Web development system: front end, back end, databases
- Memorise: Maintenance, version control, stubs and drivers, optimisation
- Key terms bank entry: Version control
- Notes: Investigate the reasons for version control and apply it when developing web applications. (Programming for the Web (Year 12))
- Notes: Version control, libraries, open source (Programming for the Web (Year 12))
- Notes: Project management, communication and ethics (The Software Engineering Project (Year 12))
- Notes: Maintenance, version control, stubs and drivers, optimisation (The Software Engineering Project (Year 12))
How to use it in an answer
A model sentence
“A system (such as Git) that records every change to the code with who and when, supports branches and merging and allows rollback, so teams can work together safely.” Then apply it: Git history lets the team revert to the last working version.
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 and extended response 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.
- Multi-select: Pick ALL correct options; the guideline marks it right only if you tick every correct one (and no wrong one).
- 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.
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: Task definition · Facade pattern · Agility · Consistency (collaboration) · Code commenting · Feedback · W3C and WAI · Client-side (front-end) programming · Server-side (back-end) programming · SQL and non-SQL databases · Web browser and developer (dev) tools · Cascading style sheets (CSS) · CSS selectors (id v class) · CSS maintenance tools