What is the difference between validation and verification in the context of algorithm design?

In the context of algorithm design, validation ensures that the algorithm meets the requirements and solves the intended problem, while verification checks that the algorithm is implemented correctly and functions as expected. Validation asks 'Are we building the right product?' whereas verification asks 'Are we building the product right?'

Why is validation important in the Cambridge IGCSE Computer Science curriculum?

Validation is crucial in the Cambridge IGCSE Computer Science curriculum because it ensures that algorithms and programs meet the specified requirements and solve the intended problems. This process helps students develop critical thinking and problem-solving skills by ensuring their solutions are fit for purpose.

How does verification contribute to effective problem-solving in computer science?

Verification contributes to effective problem-solving by ensuring that algorithms and programs are implemented correctly and function as intended. This process helps identify and fix errors early in the development cycle, leading to more reliable and efficient solutions, which is a key focus in computer science education, including the Cambridge IGCSE curriculum.

What are some common methods of validation used in algorithm design?

Common methods of validation in algorithm design include desk checking, where the algorithm is manually traced with test data; using test cases to ensure the algorithm handles various inputs correctly; and reviewing requirements to ensure the algorithm aligns with the problem's needs. These methods help ensure the algorithm's effectiveness and correctness.

Can you provide an example of how verification is applied in a computer science project?

In a computer science project, verification might involve unit testing, where individual components of a program are tested for correct operation. For example, if a student designs an algorithm to sort numbers, verification would involve testing the algorithm with different sets of numbers to ensure it consistently produces the correct sorted order, thus confirming the algorithm's correct implementation.

Why is "Treating validation and verification as the same thing" a common mistake in Validation and Verification?

Why it happens: Both check data. How to avoid it: VALIDATION = is the data SENSIBLE? VERIFICATION = was it TYPED CORRECTLY? Different goals; usually used together. Source: 0478 Examiner Reports 2022-2024

Why is "Saying validation 'prevents typos'" a common mistake in Validation and Verification?

Why it happens: Both relate to bad data. How to avoid it: Validation can't tell that '15' was a typo for '12'. Both pass a range check. Verification (re-entry / display + confirm) catches that kind of mistake.

Why is "Calling a check digit a format check" a common mistake in Validation and Verification?

Why it happens: Both check 'how' data looks. How to avoid it: Format check = pattern (letters/digits arrangement). Check digit = extra digit COMPUTED from the others, used to detect transcription errors.

Why is "Confusing presence check with type check" a common mistake in Validation and Verification?

Why it happens: Both reject empty fields in some cases. How to avoid it: PRESENCE check = was something entered? TYPE check = is what was entered the right kind (number vs text)?

Algorithm design and problem-solvingCambridge IGCSE Computer Science (0478)

Validation and Verification

Work through the notes, try the practice questions, then take the quiz. The report tells you exactly what to revise next.

Previous Next

Learn this Topic

Start with the slides for the quick version, then go deeper with the full study notes.

Short Study Notes in the form of Slides

Read the notes first. If the method in a worked example clicks, you're ready for the questions.

Page 1 / 0

Detailed Study Notes

Full prose, callouts and a recap — built for A* mastery, not just a quick scan.

Take these study notes with you

Download a branded PDF — full prose, callouts, recap and memorise list for Validation and Verification, ready to print or save offline.

Validation and Verification Study Notes — Cambridge IGCSE Computer Science 0478 (2026-2028 syllabus)

Two complementary checks on input data. VALIDATION asks 'is this data SENSIBLE?' (automatic). VERIFICATION asks 'was it TYPED CORRECTLY?' (human check). Together they catch most input errors before they pollute your data.

What you’ll learn

Mapped to the Cambridge IGCSE 0478 syllabus (2026-2028).

1.19.1 — Distinguish validation and verification.
1.19.2 — Identify validation checks and match each to a scenario.
1.19.3 — Identify verification methods.

Validation vs verification — get this right

Different goals, different methods.

These two terms are tested on every paper and consistently confused.

Validation asks 'is this data SENSIBLE?'. The system checks the data against rules — is it in the right RANGE? the right TYPE? the right FORMAT? long enough? short enough? from a known list? It's an AUTOMATIC check by the program.

Verification asks 'was this data TYPED CORRECTLY?'. Someone or something compares what was entered against the original. It's typically a HUMAN check — re-typing, reading back, comparing to a source document.

Why both matter. Validation catches systematic errors (someone typed -5 for an age). Verification catches typos that PASS validation (someone meant to type 25 but typed 35 — both are valid).

Use BOTH together: validation rejects nonsensical data; verification rejects mistyped data.

Cambridge tip. When asked to distinguish, name the GOAL ('sensible' vs 'typed correctly') AND the METHOD ('automatic against rules' vs 'human comparison').

Validation = sensible? (automatic).
Verification = typed correctly? (human).
Use both for robust input.

See the full worked example for validation and verification →

Validation checks — pick the right one

Match the check to the data type and the constraint.

Cambridge expects students to know seven validation checks and when to use each.

Range check. Data within MIN and MAX. Use for: ages (0-120), months (1-12), exam marks (0-100), temperatures (-50 to 60 maybe).

Length check. Data has the right number of characters. Use for: phone numbers (11 digits), passwords (>= 8 chars), national IDs.

Type check. Data is the correct DATA TYPE. Use for: ensuring age is an integer not text, name is text not a number.

Format check. Data matches a specific PATTERN. Use for: email (letters@letters.letters), date (DD/MM/YYYY), postcode (UK pattern), credit-card layout.

Presence check. Data has been ENTERED — field is not empty. Use for: required fields on any form.

Lookup check. Data matches one of a list of valid values. Use for: country code in a list of country codes, product code in a product list.

Check digit. An EXTRA digit calculated from the others. Used for: ISBN, credit-card numbers (Luhn algorithm), bank account numbers, barcodes.

Cambridge tip. Mark scheme expects SCENARIO → CHECK pairing. Don't just list checks — match each to a typical use case.

Seven validation checks, each for a different constraint.
Always pair the check with a scenario.
Multiple checks can be combined on the same field.

See the full worked example for validation and verification →

Verification methods

Two main methods: double-entry and screen confirmation.

Double-entry verification. The user enters the same data TWICE; the system COMPARES the two entries. Mismatches are rejected.

Common with passwords (confirm-password field).
Used in data-entry roles where one user types and a second re-types.
Catches typos because two independent typings rarely have the same typo in the same place.

Visual / screen verification. The system DISPLAYS the entered data and asks the user to CONFIRM it before saving.

Common in online forms ('Are these details correct?').
Used in payment / booking flows where mistakes are costly.
Catches typos the user can spot when reading back.

Other verification (less commonly tested).

Parity — adding a parity bit to detect transmission errors (covered in Topic 3 Data Transmission).
Checksums and hashes — comparing fingerprints of original and copy (e.g. when downloading a file, the website lists a checksum to verify the download).

Cambridge tip. Mark scheme typically wants double-entry AND screen verification with descriptions. Both are valid; both are commonly tested.

Double-entry: type twice; system compares.
Screen verification: display + confirm.
Catches typos that pass validation.

See the full worked example for validation and verification →

How it’s examined

Validation and verification appear on most Paper 2s. Most-tested questions: distinguish the two (4 marks), match validation checks to scenarios (8 marks), describe verification methods (4-6 marks). Examiner reports flag the validation/verification confusion as the most common error.

Sources: Cambridge IGCSE Computer Science 0478 syllabus (2026-2028); 0478 Examiner Reports 2022-2024; 0478/22 Oct/Nov 2024 question paper and mark scheme. Last reviewed 2026-05-09.

Master this Topic

Worked examples, formulae, definitions and the mistakes examiners flag — everything you need to push from a pass to an A*.

Take this whole topic with you

Download a branded revision sheet — worked examples, formulae, definitions and common mistakes for Validation and Verification, ready to print or save as PDF.

Step-by-step worked examples — Validation and Verification

Step-by-step solutions to past-paper-style questions on validation and verification, written exactly the way a tutor would explain them at the board.

1Identify validation checks (8 marks)
Extended• Adapted from 0478/22 Oct/Nov 2024 Q3• validation
Question
For each scenario, name the most appropriate validation check and describe what it does: (a) A user enters their age. (2 marks) (b) A user enters a postcode. (2 marks) (c) A user enters a credit-card number. (2 marks) (d) A required field on a form. (2 marks)
Step-by-step solution
1. Step 1
  (a) RANGE check (2 marks). Age should be between, say, 0 and 120. Rejects values outside this range.
2. Step 2
  (b) FORMAT check (2 marks). Postcode follows a specific pattern (UK example: letters and digits in a defined arrangement). Rejects strings not matching the pattern.
3. Step 3
  (c) CHECK DIGIT (2 marks). Credit-card numbers use the LUHN algorithm — the last digit is computed from the others. The system recomputes and compares; if they don't match, it's rejected.
4. Step 4
  (d) PRESENCE check (2 marks). The field must NOT be empty. Rejects blank submissions.
Answer
(a) Range, (b) format, (c) check digit, (d) presence. (Other valid: length, type, lookup against a list.)
2Distinguish validation and verification (4 marks)
Core• validation, verification
Question
State TWO differences between VALIDATION and VERIFICATION. (4 marks)
Step-by-step solution
1. Step 1
  Purpose (2 marks). Validation checks data is REASONABLE / SENSIBLE (in the right range, format, etc.). Verification checks data was ENTERED CORRECTLY (no typos).
2. Step 2
  Method (2 marks). Validation is an AUTOMATIC check by the system against rules. Verification is typically a HUMAN check (re-entry, on-screen confirmation) or comparison against the original.
Answer
Validation: sensible? (automatic, against rules). Verification: typed correctly? (human/comparison check).
3Describe verification methods (4 marks)
Extended• verification
Question
Describe TWO methods of verification used during data entry. (4 marks)
Step-by-step solution
1. Step 1
  Double-entry verification (2 marks). The user types the same data TWICE (e.g. password confirmation, email when creating an account). The system compares the two entries; mismatches are rejected.
2. Step 2
  Visual / screen verification (2 marks). The system displays the entered data and asks the user to CONFIRM it's correct before saving (e.g. 'Are these details correct?'). Catches typos the user can spot when reading back.
Answer
Double-entry (type twice; system compares) and visual / screen verification (display + confirm).

Key Definitions and Keywords — Validation and Verification

Definitions to memorise and the exact keywords mark schemes credit for validation and verification answers — sharpened from recent examiner reports for the 2026 0478 sitting.

Validation
Examiner keyword
Automatic checks performed by software to ensure data is REASONABLE or SENSIBLE — in the right range, format, type or length.
Verification
Examiner keyword
Checks that data has been ENTERED CORRECTLY. Typically a human check or comparison against the original.
Range check
Examiner keyword
Checks data is within a specified MINIMUM and MAXIMUM (e.g. age 0-120, month 1-12).
Length check
Examiner keyword
Checks data has the right number of characters (e.g. a UK postcode 6-7 chars, a phone number 11 digits).
Type check
Examiner keyword
Checks data is the correct DATA TYPE (e.g. age must be integer, name must be text only).
Format check
Examiner keyword
Checks data matches a specific PATTERN (e.g. email = letters@letters.letters; date = DD/MM/YYYY).
Presence check
Examiner keyword
Checks data has been ENTERED — the field is not empty.
Lookup check
Examiner keyword
Checks data exists in a list of valid values (e.g. country code matches a list of valid country codes).
Check digit
Examiner keyword
An extra digit appended to a number, calculated from the others. Used to detect transcription errors (e.g. ISBN, credit-card numbers via Luhn algorithm).
Double-entry verification
Examiner keyword
User enters the same data TWICE; the system compares the two for a match.
Visual / screen verification
System displays the entered data; user CONFIRMS it visually before saving.

Common Mistakes and Misconceptions — Validation and Verification

The traps other students keep falling into on validation and verification questions — taken from recent Cambridge IGCSE 0478 examiner reports and mark schemes — and how to avoid them.

✕Treating validation and verification as the same thing
0478 Examiner Reports 2022-2024
Why it happens
Both check data.
How to avoid it
VALIDATION = is the data SENSIBLE? VERIFICATION = was it TYPED CORRECTLY? Different goals; usually used together.
✕Saying validation 'prevents typos'
Why it happens
Both relate to bad data.
How to avoid it
Validation can't tell that '15' was a typo for '12'. Both pass a range check. Verification (re-entry / display + confirm) catches that kind of mistake.
✕Calling a check digit a format check
Why it happens
Both check 'how' data looks.
How to avoid it
Format check = pattern (letters/digits arrangement). Check digit = extra digit COMPUTED from the others, used to detect transcription errors.
✕Confusing presence check with type check
Why it happens
Both reject empty fields in some cases.
How to avoid it
PRESENCE check = was something entered? TYPE check = is what was entered the right kind (number vs text)?

Practice questions

Exam-style questions with step-by-step worked solutions. Try one before checking the method.

Past paper style quiz

Get a report showing which sub-topics you've nailed and which ones still need work.

Validation and Verification — frequently asked questions

The things students keep getting wrong in this sub-topic, answered.

Algorithm design and problem-solvingCambridge IGCSE Computer Science (0478)

Validation and Verification

Work through the notes, try the practice questions, then take the quiz. The report tells you exactly what to revise next.

Previous Next

Learn this Topic

Start with the slides for the quick version, then go deeper with the full study notes.

Short Study Notes in the form of Slides

Read the notes first. If the method in a worked example clicks, you're ready for the questions.

Page 1 / 0

Detailed Study Notes

Full prose, callouts and a recap — built for A* mastery, not just a quick scan.

Take these study notes with you

Download a branded PDF — full prose, callouts, recap and memorise list for Validation and Verification, ready to print or save offline.

Validation and Verification Study Notes — Cambridge IGCSE Computer Science 0478 (2026-2028 syllabus)

What you’ll learn

Mapped to the Cambridge IGCSE 0478 syllabus (2026-2028).

1.19.1 — Distinguish validation and verification.
1.19.2 — Identify validation checks and match each to a scenario.
1.19.3 — Identify verification methods.

Validation vs verification — get this right

Different goals, different methods.

These two terms are tested on every paper and consistently confused.

Why both matter. Validation catches systematic errors (someone typed -5 for an age). Verification catches typos that PASS validation (someone meant to type 25 but typed 35 — both are valid).

Use BOTH together: validation rejects nonsensical data; verification rejects mistyped data.

Cambridge tip. When asked to distinguish, name the GOAL ('sensible' vs 'typed correctly') AND the METHOD ('automatic against rules' vs 'human comparison').

Validation = sensible? (automatic).
Verification = typed correctly? (human).
Use both for robust input.