Portals eNewsletters Web Seminars dataWarehouse.com DM Review Magazine
DM Review | Covering Business Intelligence, Integration & Analytics
   Covering Business Intelligence, Integration & Analytics Advanced Search

View all Portals

Scheduled Events

White Paper Library
Research Papers

View Job Listings
Post a job


DM Review Home
Current Magazine Issue
Magazine Archives
Online Columnists
Ask the Experts
Industry News
Search DM Review

Buyer's Guide
Industry Events Calendar
Monthly Product Guides
Software Demo Lab
Vendor Listings

About Us
Press Releases
Advertising/Media Kit
Magazine Subscriptions
Editorial Calendar
Contact Us
Customer Service

Meta Data and Data Administration:
Meta Data Repository Project Plan: Part 1 of the Design Phase

  Column published in DM Review Magazine
March 2001 Issue
  By David Marco

This column is the third installment in a walk-through of the key tasks in each of the five fundamental phases of a project plan to build a meta data repository: orientation, feasibility, design, construction and rollout. This month we will target the first two key deliverables of the design phase (see Figure 1): meta data tool evaluation and selection, and constructing the integration architecture document. Next month's column will cover creating detailed design documents and training development staff.

The purpose of the design phase is to document the specific processing and reporting requirements of the meta data repository project. The key deliverables in this phase are an evaluation of meta data tools, construction of the integration architecture document and detailed program design specifications.

Evaluate and Select. One of the primary activities of the design phase is evaluating and selecting appropriate meta data tools - both access and integration tools. Although all meta data tools have some drawbacks, I believe that such tools are beneficial for most meta data repository implementation projects and generally advise my larger clients to purchase these tools and incorporate them in their meta data architecture. On the other hand, if the company is relatively small and/or has a limited IT budget, it may not be practical to purchase these tools and then spend the necessary time and effort to learn to use them effectively. In these situations, some companies may find it beneficial to manually integrate all of the meta data sources and build their own custom reports (see December 2000 column).

Task IDTask NameDurationDependencyResource Names
3Design Phase36 days2 
3.1Meta Data Tool Evaluation and Selection26 days  
3.1.1Meta Data Integration Tool26 days Data Acquisition Developers, Repository Architect (0.25), Project Manager (0.25), Data Modeler
3.1.2Meta Data Access Tool26 days Business Analyst, Data Delivery Developers, Repository Architect (0.25), Project Manager (0.25)
3.2Construct Integration Architecture Document10 days  
3.2.1Identify sources of meta data to be integrated3 days Repository Architect (.5), Project Manager (0.5)
3.2.2Identify meta data needs each source shall provide2 days3.2.1Repository Architect (0.5), Project Manager (0.5)
3.2.3Detail the specific integration method each source of meta data will need3 days3.2.2Repository Architect (0.5), Project Manager (0.5)
3.2.4Map out hardware/software architecture2 days3.2.3Repository Architect (0.5), Project Manager (0.5)
Figure 1: Design Phase Tasks

Create Information Architecture Document. The repository architect is responsible for creating the integration architecture document which provides a detailed technical outline of the repository architecture. Because meta data tools play an important role in the repository architecture, this document should be created in concert with the tool evaluation. The major sections of the integration architecture document are nearly identical to those of the project scope document, with the exception of the first two sections. The major sections of the information architecture document are:

  • Meta data integration architecture
  • Future meta data repository releases
  • Critical success factors
  • Risk factors
  • Assumptions
  • Issues
  • Sign- off sheet

The meta data integration architecture section is the key portion of this document. It presents the technical meta data architecture along with detailed descriptions of the various sources of meta data and how they will be technically integrated.

This section walks through each of the meta data sources and specifically explains what meta data is being brought into the repository, how the meta data will be integrated and how often the meta data will be updated in the repository. Let's use a custom data dictionary as an example. In the meta data integration architecture section, I would state: "The custom data dictionary contains business field definitions that are embedded in a third-party packaged application which uses a non-open database structure and is located on an IBM mainframe. The meta data repository team will use COBOL (common business oriented language) and JCL (job control language) to extract the data. They will use FTP (file transfer protocol) to transfer the information to the Windows NT directory where we will integrate it into the meta data repository."

Any meta data tools that are being used will be presented in this section. With this presentation, it is important to list the strengths and shortcomings of the tool(s) and why the tool was chosen. This is done to officially document the reasons for the decision. All too often, tools are selected and then the technical environment changes. Consequently, the tool is no longer as useful, and one begins to question why the specific tool was selected. This section clearly documents the process and reasoning behind the selection.

Future Meta Data Architecture. Because the first release of a meta data repository project does not usually implement all of the desired functionality, it is necessary to document the plan for handling the remaining requirements in future project releases. This section provides a picture of the future meta data repository.

While this section does not have to include a detailed discussion of each projected meta data source, it is vital to highlight any anticipated changes to the current architecture. These changes may include moving from the current front end to a corporate portal concept or technically integrating new sources of meta data into the repository. This section is intended to keep the focus on the future of the repository and to reduce "throw-away" efforts. Keep in mind that this intended architecture could change during the next release of the repository. However, it is critical not to skip this step to insure that the repository's architecture meets the architectural needs of the future releases.

The critical success factors, risk factors, issues and sign-off sections are familiar to most IT professionals, so I will skip these sections with the exception of one note. The sign-off section for this document differs somewhat from the project scope document sign-off. In this case, the sign-off should be limited to the project champion, the project manager and the repository architect.

Next month, we will complete the design phase.

This column is adapted from my book Building and Managing the Meta Data Repository (Wiley, 2000). The complete project plan is available on the accompanying CD-ROM.


For more information on related topics visit the following related portals...
DW Design, Methodology.

David Marco is an internationally recognized expert in the fields of enterprise architecture, data warehousing and business intelligence and is the world's foremost authority on meta data. He is the author of Universal Meta Data Models (Wiley, 2004) and Building and Managing the Meta Data Repository: A Full Life-Cycle Guide (Wiley, 2000). Marco has taught at the University of Chicago and DePaul University, and in 2004 he was selected to the prestigious Crain's Chicago Business "Top 40 Under 40."  He is the founder and president of Enterprise Warehousing Solutions, Inc., a GSA schedule and Chicago-headquartered strategic partner and systems integrator dedicated to providing companies and large government agencies with best-in-class business intelligence solutions using data warehousing and meta data repository technologies. He may be reached at (866) EWS-1100 or via e-mail at DMarco@EWSolutions.com.

Solutions Marketplace
Provided by IndustryBrains

Data Validation Tools: FREE Trial
Protect against fraud, waste and excess marketing costs by cleaning your customer database of inaccurate, incomplete or undeliverable addresses. Add on phone check, name parsing and geo-coding as needed. FREE trial of Data Quality dev tools here.

Backup SQL Server or Exchange Continuously
FREE WHITE PAPER. Recover SQL Server, Exchange or NTFS data within minutes with TimeSpring?s continuous data protection (CDP) software. No protection gaps, no scheduling requirements, no backup related slowdowns and no backup windows to manage.

Manage Data Center from Virtually Anywhere!
Learn how SecureLinx remote IT management products can quickly and easily give you the ability to securely manage data center equipment (servers, switches, routers, telecom equipment) from anywhere, at any time... even if the network is down.

Design Databases with ER/Studio: Free Trial
ER/Studio delivers next-generation data modeling. Multiple, distinct physical models based on a single logical model give you the tools you need to manage complex database environments and critical metadata in an intuitive user interface.

Free EII Buyer's Guide
Understand EII - Trends. Tech. Apps. Calculate ROI. Download Now.

Click here to advertise in this space

View Full Issue View Full Magazine Issue
E-mail This Column E-Mail This Column
Printer Friendly Version Printer-Friendly Version
Related Content Related Content
Request Reprints Request Reprints
Site Map Terms of Use Privacy Policy
SourceMedia (c) 2006 DM Review and SourceMedia, Inc. All rights reserved.
SourceMedia is an Investcorp company.
Use, duplication, or sale of this service, or data contained herein, is strictly prohibited.