Why You Should Have a Data Dictionary (and What You Should Include in It)

Description

• Would your life be easier if your organization had a high quality data dictionary?
• Would having a high quality data dictionary save time in requirements elicitation?
• Would your requirements be both more concise and precise if they could reference your high quality data dictionary?
• Would your software developers save considerable time if your requirements referenced your high quality data dictionary?
• Would your business intelligence staff save considerable time and effort if you had a high quality data dictionary?
• Would your stakeholders have fewer questions and create higher quality data requests if they had a high quality data dictionary available?

But does this conjure up thoughts of how difficult it will be and how long it will take? Then this presentation is for you! You learn where to start and what to focus on first, how to obtain the relevant technical details quickly and simply, and best practices on definitions.

Audience

business analysts, data analyst managers, business intelligence managers

Goals

Attendees will be able to understand appropriate items to include in a business data dictionary and how technical details can be associated with the business data elements.

After the session, you should be able to:

• know what you should put into your business data dictionary
• understand how your technical team can very simply and quickly gather the technical details
• recognize high quality data element definitions
• recognize that associating the technical details to the business data dictionary might be challenging and how you can make that process easier.

Prerequisites

An interest in or recognized need for a data dictionary is optional.