Computer ScienceExam code: 0984

Problem Solving and Design

Algorithm Design and Problem Solving

Verification is a check that the data entered into the system matches the data that was intended.

Validation asks "Is this input sensible?" Verification asks "Did the user actually mean to type this?"

Two common verification methods:

Double-entry verification

The user enters the same value twice; the program checks that the two entries match.

Visual check

The system displays the entered data back to the user and asks them to confirm it is correct before continuing.

When to use which

  • Double-entry verification is best for values the user cannot easily check by reading (passwords, where the characters are usually masked).
  • Visual verification is best for values the user can easily eyeball (addresses, names, phone numbers).

Common exam question

Verification checks and why they are used

Question: Explain why input data is verified, outline one or two types of verification check and their use, or tick the check that is verification (1–4 marks).

Asked in 5 of the 17 papers. Explaining the purpose is two marks: data is copied accurately, with no changes to the values intended, and is copied from one source to another. One tick-box puts it as a value that has not changed during input, and the one verification check in a list of validation checks is the visual check.

For the types, the name is one mark and its use the second. Visual check: the user reads back the data entered on screen and confirms it is correct, or corrects any errors. Double entry check: the user enters the data twice, the computer compares the two entries and asks for a re-entry if they differ. Asked why a program adds a double entry check, answer "to verify the data": verification, not validation.

The big-picture difference

ValidationVerification
What it asksIs the input plausible / sensible?Did the user actually mean to type this?
Performed byThe program (automatically), based on rulesThe user (with a prompt from the program)
MethodsRange, length, type, presence, format, check digitDouble-entry, visual check
CatchesInvalid types, blank fields, out-of-range values, typos in formatted codesTyping the wrong but plausible value (e.g. wrong email address)
LimitCan confirm input is sensible, not that it is correctCan confirm the user typed what they meant, but not that the meaning is right

Quick check

4 short questions on this note. See what has stuck, and where to look if something hasn't.

About 2 minutes

Build on this topic