Introduction to Data Validation and Verification
Welcome to one of the most important chapters in AS 2: Fundamentals of Digital Technology! Whenever data is entered into a computer system—whether you are creating a new social media profile, ordering items online, or processing employee payroll—errors can easily slip in. If bad data enters a system, it leads to the classic computing problem of Garbage In, Garbage Out (GIGO).
In this chapter, we will master the two vital techniques used to catch data entry errors: Validation and Verification. Don't worry if these sound similar at first; by the end of these notes, you will know exactly how they differ, how each check operates, and how to score full marks in your CCEA AS 2 exam.
Quick Summary of the Core Difference:
• Data Validation: An automatic computer check to ensure data entered is sensible, reasonable, and conforms to defined rules.
• Data Verification: A check to confirm that data entered into the computer exactly matches the original source data.
Validation vs Verification: The Crucial Distinction
Examiners frequently test whether you understand the precise boundary between validation and verification. Let's look at the official BCS (British Computer Society) definitions required by CCEA:
Data Validation is an automatic check carried out by software to ensure that data conforms to predefined rules or constraints. It checks whether data is sensible, reasonable, and allowable. For example, if a form asks for an age and a user types \(-15\) or "apple", validation rules will automatically reject it.
Data Verification is the process of checking that data has been copied across or keyed in accurately from the source document without introducing transcription errors (typing the wrong character) or transposition errors (swapping adjacent characters around, such as typing \(35\) instead of \(53\)).
Analogy Time: The Club Door vs The Passport Check
Think of Validation like a bouncer checking your dress code at a venue. The bouncer checks if your outfit is acceptable according to the venue rules (e.g., "Must wear shoes, no sportswear").
Think of Verification like a passport officer checking your identity. The officer checks whether the name on your boarding pass identically matches the original document in your hand.
Crucial Examiner Warning: Neither Guarantees 100% Accuracy!
A classic exam pitfall is claiming that validation or verification ensures data is "100% correct". Neither method can guarantee that the original source data was factually true in the real world:
• If a customer writes on a paper form that their age is \(25\), but they are actually \(52\), validation will accept \(25\) because it is a reasonable age number.
• Verification will also confirm that the typist correctly keyed in \(25\) from the paper form.
• The system now holds verified, validated data that is still factually incorrect!
Key Takeaway: Validation checks if data is reasonable and permitted; Verification checks if data matches the source.
Official CCEA Validation Checks
The CCEA AS 2 specification requires you to understand, describe, and apply seven specific validation checks.
1. Range Check
What it does: Checks that a numeric value or date falls within predefined upper and lower boundaries.
Example: Checking that an entered calendar month satisfies the condition \(\ge 1\) and \(\le 12\), or that an entered human age is between \(0\) and \(120\).
2. Type Check (Character Check)
What it does: Ensures that the data entered consists purely of the expected character type (e.g., only letters, or only numbers).
Example: Ensuring a customer's surname contains purely alphabetic characters, or an item quantity contains purely numeric digits.
3. Length Check
What it does: Confirms that an input string contains an exact required number of characters, or stays within a permitted minimum and maximum character boundary.
Example: Checking that a standard UK bank account number is exactly \(8\) digits long, or that a UK postcode fits within standard length boundaries.
4. Format Check (Picture / Pattern Check)
What it does: Ensures that data follows a specific predefined layout, pattern, or mask.
Example: Checking that a date matches the pattern DD/MM/YYYY, or that a UK National Insurance number follows the pattern of two letters, six digits, and a final letter (e.g., \(LLNNNNNNL\)).
5. Presence Check
What it does: Checks that a mandatory field has not been left blank or null before the record is submitted.
Example: Preventing an online order from proceeding if the "Home Address" or "Email Address" field is left empty.
6. Lookup Check
What it does: Compares an entered value against an existing list of valid stored options or a lookup table.
Example: Selecting a title from a dropdown containing [Mr, Mrs, Ms, Dr], or ensuring an entered county exists in a pre-stored list of UK counties.
7. Modulus 11 Check Digit
What it does: An extra calculated digit added to the end of a numeric sequence. It is designed to instantly detect transcription and transposition errors during data entry.
Step-by-Step: How to Calculate a Modulus 11 Check Digit
CCEA examiners allocate method marks for showing full arithmetic working. Always lay out your calculation clearly using these five steps:
Step 1: Write down the raw number and assign descending weights (usually starting from \(6, 5, 4, 3, 2\)) to each digit from left to right.
Step 2: Multiply each digit by its assigned weight.
Step 3: Calculate the total sum of these products.
Step 4: Divide the total sum by \(11\) to determine the remainder.
Step 5: Subtract the remainder from \(11\) (\(11 - \text{remainder}\)) to get the check digit.
• Rule A: If the remainder is \(0\), the check digit is simply \(0\).
• Rule B: If the final calculation gives \(10\), the check digit is conventionally written as the character 'X' (to keep it as a single character).
Worked Example:
Let's calculate the check digit for the 4-digit product code 4 3 8 2 using weights 5, 4, 3, 2:
• Multiply by weights:
\(4 \times 5 = 20\)
\(3 \times 4 = 12\)
\(8 \times 3 = 24\)
\(2 \times 2 = 4\)
• Sum the products:
\(\text{Sum} = 20 + 12 + 24 + 4 = 60\)
• Divide by 11 to find remainder:
\(60 \div 11 = 5\) with a remainder of 5 (since \(5 \times 11 = 55\), and \(60 - 55 = 5\)).
• Subtract remainder from 11:
\(\text{Check Digit} = 11 - 5 = 6\)
• Final full number: 43826
Key Takeaway: Validation checks are automatic software filters. Learn the 7 check types: Range, Type, Length, Format, Presence, Lookup, and Modulus 11.
Official CCEA Verification Methods
Verification confirms that data has been transferred from the source accurately. CCEA specifies three main verification methods:
1. Double Entry
How it works: The same data is keyed into the computer system twice (either by two different operators or independently by the same operator). The computer compares the two inputs character by character. If there is any mismatch, the system flags a discrepancy and prompts the user to re-enter the data.
Everyday Example: When setting up a new password online, you are asked to type your chosen password twice to ensure you haven't made a typing error.
2. Proofreading (Visual Verification / Screen Check)
How it works: The user carefully reads the data displayed on the screen and visually compares it against the original paper or source document line-by-line before pressing submit.
Limitation: Proofreading relies on human concentration; eye fatigue can cause operators to overlook small errors.
3. Batch Control Totals
When large collections of records are processed together in a batch (e.g., overnight payroll or utility billing), control totals are calculated before and after processing to ensure no records were lost, added, or corrupted during input.
There are three distinct types of batch control totals you must know:
A. Batch Total (Financial Total):
The sum of a meaningful numeric field across all records in the batch. For example, adding up the total monetary value of all sales invoices in a batch (e.g., total batch revenue = £14,850.50).
B. Hash Total:
The sum of a numeric field that has no inherent real-world arithmetic meaning. It is calculated purely for error-detection purposes. For example, adding together all the Customer Account Numbers or Employee ID Numbers in a batch (e.g., summing account numbers \(1004 + 1082 + 2190 = 4276\)). The number \(4276\) has no financial meaning, but if a digit is typed incorrectly, the hash total will change, alerting the system to an error.
C. Record Count:
A simple count of the total number of individual records contained within the batch (e.g., verifying that exactly \(150\) transaction slips were entered).
Key Takeaway: Verification methods include Double Entry, Proofreading, and Batch Control Totals (consisting of Batch Totals, Hash Totals, and Record Counts).
Common Pitfalls & Examiner Advice for AS 2
Make sure you avoid these common traps highlighted in CCEA Chief Examiner reports:
1. Avoid Vague Language:
Never say a validation check "makes sure data is right" or "checks that the number fits". Use precise BCS terms: validation checks if data is sensible, reasonable, and conforms to rules. Use terms like transcription error and transposition error when discussing verification.
2. Don't Skip Modulus 11 Working Steps:
Even if your final check digit is correct, you can lose method marks if you do not show: (1) multiplication by weights, (2) summation of products, (3) division by 11 with the remainder clearly identified, and (4) subtraction from 11.
3. Distinguish Between Batch and Hash Totals:
• If the field has arithmetic meaning (e.g., hours worked, total cost), it is a Batch Total.
• If summing the field produces a meaningless number (e.g., summing phone numbers, product codes, NI number digits), it is a Hash Total.
Quick Review Checklist
Before sitting your AS 2 exam, make sure you can answer these questions with confidence:
• Can you state the exact definition of data validation and data verification?
• Can you name and give an example of all 7 validation checks?
• Can you calculate a Modulus 11 check digit from scratch showing all 5 steps?
• Can you explain the difference between a Batch Total and a Hash Total?
• Can you explain why a record can pass both validation and verification but still contain incorrect information?