Business Glossary

A business glossary records the meanings of terms used in an organization. An entry can include a definition, scope, examples, owner, and approval status. Its purpose is shared interpretation, not merely an alphabetical list of words.

Similar names can answer different questions

Created orders and paid orders describe different sets. Calling both orders hides the distinction. A useful entry explains whether canceled or refunded orders count and which reporting period and cutoff apply. Examples expose ambiguities that a short label can conceal.

When teams legitimately need different measures, name them distinctly rather than forcing one definition onto every decision. Record the relationship so users know when comparisons are appropriate.

A definition must reach the calculation

A glossary describes meaning; it does not automatically change every query. Link the approved entry to relevant datasets, implementations, and tests. A column with the same name can still implement an older rule.

A technical data dictionary typically describes fields and structures, while a business glossary emphasizes meaning. The two can be connected within a catalog. Review both the definition and its implementations when a source or business rule changes.

Reference: UK Government: Data Quality Framework.