TK Study

Software Engineering › Key terms › Y11 OOP › Regular backup

Regular backup

Term Y11 OOP

Definition

Making frequent copies of code and data (ideally off-site or in the cloud) so work can be restored after loss or corruption.

Example: Push the code to a repository each day.

Found in: syllabus, school notes.

Where it is used in the test

Syllabus area: Y11 OOP.

Question types it can appear in

No past question in this bank is linked to this term yet. It can still be tested through the question types above.

Study links

How to use it in an answer

A model sentence

General advice, built from the definition and example above

“Making frequent copies of code and data (ideally off-site or in the cloud) so work can be restored after loss or corruption.” Then apply it: Push the code to a repository each day.

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 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

Common mistakes

General advice
  • 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.

Same group in the syllabus: Clear and uncluttered mainline · One logical task per subroutine · Stub · Ease of maintenance · Unit testing · Subsystem testing · System testing · Black box testing · White box testing · Grey box testing · Quality assurance