Data completeness
Data is complete when every required value is present. There are no blank fields and no missing records, so everything the exchange needs has arrived.
Understanding Data completeness in QCE Digital Solutions Unit 4
What it does: The code tests a required field for an empty value and flags the record as incomplete, which checks for blank fields. Matching the received count to the sent count confirms no records were lost during the exchange. Records that never arrived are a completeness problem. The values in the 480 records may still be correct. Missing values can cause failed processing or misleading results. Incompleteness does not need an attacker, as it can be caused by faults or errors.
Common mistakes: The loop must go through the required fields. Looping over the record only checks fields that are already there, so missing ones are never found. It should be: for f in required:. A single = assigns the number of expected records to the variable. == is a comparison and would cause a NameError because expected does not exist yet. It should be: expected = 10.
Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.
This module's key terms are also in a printable crossword (Modules 127–333) and word search (Modules 127–401).
Take this worksheet further — free with Cloodit
Each concept is reinforced from every angle — learned, then applied, then tested.
Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.
Over 100 of them, across seven natural biomes.
Turns their work into revision material ready for Flash Cards and Exam study.
Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.
Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.
Quick Questions
Match the Pairs
Key Term
completenessFill in the Blanks
Spot the Error
Student with a class code? Join your class →