A data dictionary describes every field a solution keeps, so that the business, developers and testers mean the same thing by "claim amount". For each field it records:
- Name and a plain definition ("claim_amount: the amount the policyholder asks to be paid, before any excess").
- Data type: text, whole number, decimal, date, yes or no, or a code list (a fixed set of allowed values).
- Format and length: YYYY-MM-DD, two decimal places, 12 characters.
- Required or optional, and any validation rule ("not in the future").
- Source and owner: where the value comes from, who decides its meaning.
The trap that catches people: codes that look like numbers. A policy number such as 0048213 is text, not a whole number: stored as a number it loses its leading zero, and nobody ever adds two policy numbers together. If you would never do arithmetic on it, it is probably text.
Part of a data dictionary.