4 thoughts on “Business glossary and data dictionary: Pieces of the same puzzle

  1. This is a good read, thank you Gary.
    I am wondering though how you feel about including synonyms in the glossary.
    Also, would you for example include First Name, Beneficiary and Beneficiary First Name in your glossary?

    1. Hi Jaunine. Yes, I would certainly include synonyms that are in common use in my business. I would suggest creating the primary term e.g First Name that would be most preferrred and do my definitions at this level only. Synonyms woulb be linked to this term

  2. When the focus on a particular project is on Java /JS/ Web application with an internal SQL database, we can generate the DB model from Eclipse, but it does not contain the range values of the column types. In such a context, it should be OK to list Table Names, the UML Table class definitions, and Table creation DB Schema as DDL statements. This can be called the Java web style of data dictionary, as this DB API is internal, not to be called by users who call the REST API of the Web Application. And all the range and value checks will be caught in realtime at the GUI front end part of the Web application.

    Any comments?

    1. HI Sushil – thanks for your question. I would suggest that you would want to capture the range / allowed values for each column as rules linked to your glossary. Fundamentally the metadata is documentation that allows any stake holder to quickly and easily understand the data they are looking for. You may think of this as your Business Requirements Definition that your programmer would use to define the real time checks.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.