[Priya Shah]

Field names alone may not explain meaning, allowed values, relationships, or changes. When is a data dictionary important?

[Marcus Reed]

Accepted answer

Require it when the buyer must integrate, migrate, report on, audit, retain, or reuse data outside the application. It should define fields, types, units, code lists, stable identifiers, relationships, null behavior, ownership, and version changes. Bind delivery timing and update obligations to the contract. FAR Subpart 27.4 says known data requirements and delivery conditions should be specified.

[Maya Chen]

Community reply

Should the data dictionary include historical fields that are no longer visible in the application?

[Author]

Posts