Open Framework, Information Management Strategy & Collaborative Governance | Data & Social Methodology - MIKE2.0 Methodology
Wiki Home
Collapse Expand Close

Members
Collapse Expand Close

To join, please contact us.

Improve MIKE 2.0
Collapse Expand Close
Need somewhere to start? How about the most wanted pages; or the pages we know need more work; or even the stub that somebody else has started, but hasn't been able to finish. Or create a ticket for any issues you have found.

Metadata Management Conceptual Design Deliverable Template

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
Under review.png
This article is a stub. It is currently undergoing major changes as it is in the very early stages of development and is only a placeholder. Please help improve MIKE2.0 by adding to this article.
This deliverable template is used to describe a sample of the MIKE2.0 Methodology (typically at a task level). More templates are now being added to MIKE2.0 as this has been a frequently requested aspect of the methodology. Contributors are strongly encouraged to assist in this effort.
Deliverable templates are illustrative as opposed to fully representative. Please help add examples to this template that are representative of the proposed output.

The Metadata Management Conceptual Design task determines how metadata will be obtained, created and stored. It also determines who the users are; and, how and what metadata should be made available to them.

Since metadata usually resides in different places it will take effort to consolidate the different sources. The uses of the metadata will also influence the management strategy and the selection of tools that capture metadata.

The end users will need the following metadata categories of interest, which may include:

  • Business definition of the data
  • Physical data models
  • Common Messaging Model for data in motion
  • Sources to answer questions about the data
  • Data Re-Engineering metadata
  • Data Quality metadata
  • Algorithms or formulas used to derive data (in business terms)

Contents

Example Metadata Management Conceptual Design

The following section (Metadata Management Conceptual Design) provides a high-level overview to the various metadata management solution elements and standards that the approach adheres to.

Metadata Management Conceptual Design

Business Definition of Metadata

1. XYZ 2-0 metadata will describe the path attributes have taken through the solution, from their original source to final controlled target and any business rules applied along the way.

2. As shown in the diagram above, XYZ 2-0 metadata will commence with mapping from the BDS2, ODS2 and MDE tables in ABC.

3. XYZ 2-0 metadata will map data movement via ETL into the RDS database schema.

4. XYZ 2-0 metadata will also map data movement via Cognos Framework Manager to output as defined ABC reports, such as the Stock Item Analysis report.

6. The primary focus of defining metadata for XYZ 2-0 will not include the transition of data from source systems into the target environment.

Source-to-Target Metadata

7. The mapping and transformation information shall be captured during the requirements and design stage using the Metadata Management tool.

Metadata Management Solution Component XYZ Examples
Data Group Collection Database, Schema, BI Tool BDS2, ODS2, RDS, MDE
Data Group Table, View, File, Report, Screen Stock Item Activity, Item Details File, XYZ Variables Tool
Data Item Attribute, Field Stock Item Code, Supplier Name, Expenditure Year One

8. To preserve data lineage and enable reporting, each mapping is recorded as a separate transformation – even if the data movement is a direct mapping and there are no business rules applied.

9. This information will allow business users to identify where and how the requirements have been implemented. It also allows them to see the data models without access to the ABC database.

Solution Implementation Metadata

10. During the Development and Functional Testing phase, the business rules will be refined. Once the mappings are stable, development will commence and the Metadata Tool will be updated with technical details about how the solution was implemented

Solution Metadata Solution Component XYZ Examples
Run Suite ETL Sequence Job "SQ_IDS2_XYZ_ref"
Run Module ETL Parallel Job "ids2_ref_DuesIn", "ds_rds_XYZ_StockItem_load"

11. Transformation Rule Maintenance in Metadata Tool records the mappings from initial source to final target stage and these can be tagged to a single Run Module. If a derivation involves more than one discrete piece of code this is noted in the long description.

12. This information will allow technical users to identify the areas of code that need to be examined when queries about derivations are raised.

Wiki Contributors
Collapse Expand Close