Please enable JavaScript.
Coggle requires JavaScript to display documents.
Verification and validation of data in design (Validation - check that…
Verification and validation of data in design
Verification - process whereby we try to access whether the data is 'true' (correct, accurate)
Examples
E.g. Double entry (retype an email address
Built in verification workflows - email to the entered address and proceed only if contained link is accessed
Cross reference to other data - if a user is aged 11, does it seem likely that they earn $100k per annum
Confirmation - get users to confirm drastic actions such as deletes.
Self checking codes - check digits for critical codes. e.g. account numbers
Validation - check that data input is correct according to standards that have been set
Examples
Existence checks - a match record exists in a reference file
Format checks - NI number conforms to a certain format
Length checks - min and max digits allowed
Lookup table - code must coincide with a list in a table (Budget codes....)
Range check - the data value has a min and max value - ie. VLAN number
Cross-field validation - between related data items
passing validation does not guarantee that the data is 'true'
Design
Input
Minimise the amount of data required from user input
Use codes, lists, radio buttons, check boxes.
Long data entry processes should be broken up and checked in stages
Error messages should be clear, relevant and helpful
Any data input should be verified and validated
Output
Data output should go through sanity checks - don't send a final domain for a bill of -$0.001
Throughly test boundary conditions
Scrutiny and audit by real people