1 / 3

DATA DICTIONARY

A data dictionary is often owned and maintained by IT<br>departments, with relevant information collected from<br>business users. For more info:- http://vyakar.com

traceygturk23
Télécharger la présentation

DATA DICTIONARY

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WHITE PAPER DATA DICTIONARY DEFINING AND USING A COMMON LANGUAGE

  2. WHITE PAPER DATA DICTIONARIES TABLE OF CONTENTS INTRODUCTION 3 OWNERSHIP 3 AVAILIBILITY 3 2

  3. WHITE PAPER DATA DICTIONARIES AVAILIBILITY INTRODUCTION Many companies are trying to build a robust data dictionary on business functions across organizations, aligning processes around it. Large enterprises have a dedicated data steward, while small and medium enterprises often rely on a data champion. Whatever the size of an organization, data stewardship requires cooperation across business functions. However, in this interplay between business organization, operations, and IT, priorities are often misaligned, delaying implementation. Sometimes projects are so delayed that implementation does not yield meaningful results. On the other hand, data dictionaries are changed too frequently along with changes in business strategy. Despite delays in updating backend IT systems, managing impact on business processes becomes difficult if all dependencies are not well documented. Furthermore, a mismanaged data dictionary inevitably creates confusion across functions, leading to an operational and reporting nightmare. OWNERSHIP Ideally, data dictionaries should be defined and deployed at the data source, and made available to other parts of the system using Application Program Interface (API) integration. This ensures that no two definition of the same term exists, and all operational and reporting tools refer to the same definition. Businesses possessing the ability to quickly access definitions modify them on short notice have tremendous operational agility. A data dictionary is often owned and maintained by IT departments, with relevant information collected from business users. The process of defining and validating data dictionary takes weeks if not months. Because most applications are now directly accessible to business users thanks to SaaS and Cloud, ownership of relevant data dictionaries are better off with businesses. Ultimately, a group of business affiliated Ops team, or the business itself can do much better governance than a layered team. 4701 Patrick Henry Drive| Building 25 | Santa Clara, CA 95054 Telephone: 1.844.321-LEAD (5323) | info@vyakar.com www.vyakar.com 3

More Related