TK Study

Software Engineering › Learn step by step › Y11 OOP

Item 135 of 426 · Year 11: The Object-Oriented Paradigm, 20 of 33

Version control

Term Key terms bank

Jump to a topic
  1. Exam format, question types and command words (46)
  2. Year 11: Programming Fundamentals (69)
  3. Year 11: The Object-Oriented Paradigm (33)
  4. Year 11: Programming Mechatronics (29)
  5. Year 12: Secure Software Architecture (57)
  6. Year 12: Programming for the Web (59)
  7. Year 12: Software Automation (35)
  8. Year 12: The Software Engineering Project (47)
  9. Diagrams and modelling tools (18)
  10. Python, SQL, pseudocode and CSS patterns (33)

See every item in the sequence

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.

Short version to memorise (key terms bank)

Tracks changes, branches, merges and reverts code.

Where you'll use it in the test

Syllabus area: Y11 OOP Y12 Programming for the Web Y12 SE Project.

Question types it can appear in

Where it has appeared in the paper

The Software Engineering Project (Part B). Part letters follow each paper’s own layout.

Related past questions

How to use it

A model sentence

General advice, built from the definition and example above

“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

General advice

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.

Official worked answer

Sample exam Q4 (1 mark): Collaboration (1 mark): official 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.

Open the question page

Go deeper

Check yourself

Explain “Version control” in one sentence, give an example, and name a question type that could test it.

Reveal the answer

Version control: 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.

Version control (web): 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.

Version control (project): 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.

Could be tested as: Multiple choice, Multi-select, Short answer, Extended response.

Quick multiple choice

What is the main benefit of using version control (e.g. Git) in a web project?

  1. It hides the source code from users
  2. It tracks changes, lets developers work on branches and restore earlier versions
  3. It removes the need for testing
  4. It makes the code run faster
Show the answer

B

Version control stores history, supports collaboration through branching/merging and allows rollback.

Source: original (written for this study pack; not a NESA question). Open it in the multiple-choice bank.