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 Driven Architecture

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
Content Model Relationship

Contents

Activity: Metadata Driven Architecture

Objective

Defining the Metadata Driven Architecture in the only activity in the Blueprint phase of MIKE2.0 that involves a more detailed level of software design and implementation. This is because MIKE2.0 aims to get metadata management practices in place from the onset. As Phase 2 involves strategic technology requirements and product selection, the implementation team may lack the tools with which they plan to strategically manage metadata and ideally move to a metadata-driven environment. Therefore, projects will often need to take a tactical approach in the early stages. Regardless of whether a product has been selected yet, some form of repository and base meta-model should be in place from the early stages of the project. MIKE2.0 provides a starter set model for metadata management that defines much of the core metadata that should be captured. During the Blueprint phase, this model can be used to collect information that historically would have done in documents or spreadsheets. In follow-on activities the bespoke model is typically replaced by an off-the-shelf product.

Major Deliverables

  • Initial Prototype Metadata Repository
  • Initial set of Metadata Management Standards

Tasks

Introduce Metadata Reference Model

Objective:

MIKE2.0 provides a core reference model for metadata management that can be used as a starting point for defining scope and familiarising users with basic concepts. Although less sophisticated than some reference models, it provides a simple starting point that is quite appropriate to use at this early stage of the programme.

If another metadata model is already available, it would be appropriate to use this model at this time. It can also be used in conjunction with the MIKE2.0 Reference Model.

Input:

  • Reference Model for Metadata Management
  • High Level Information Requirements
  • Strategic Requirements for Information Development

Output:

Define Scope for Initial Implementation

Objective:

Metadata is stored across all components in the architecture. For the first tactical implementation, this scope will focus on trying to capture only a subset of this information as proof of moving to a metadata-driven architecture. The strategic requirements for Information Development define the overall scope of how metadata will be managed.


Input:

  • Reference Model for Metadata Management
  • High Level Information Requirements
  • Strategic Requirements for Information Development


Output:

Define SDLC Process for Metadata Management

Objective:

Moving to a metadata-driven architecture means that an organisation will probably be implementing significant changes to their software development practices. Unlike more established data standards, metadata management standards are less mature and are not likely to be all defined form the onset. The team should define some initial standards for how metadata is to be managed and then trial implementation of these standards at this point. The team should expect to revise these standards at multiple points within the continuous implementation phases.

Input:

Output:

Populate Repository with Metadata Assets

Objective:

To input data into the metadata reference model and then analyse its contents, the reference model should be implemented as a physicalised model. It may be helpful to have an interface on the front-end as well as a reporting environment on the back end for analysing results.

Once again, metadata management products also provide this capability so if these already exist it would be appropriate to use the products as opposed to a bespoke solution.

Input:

Output:

Define Process to Transition to Metadata-Driven Architecture

Objective:

The approach to metadata management will mature through the course of implementing the MIKE2.0 Methodology. There are multiple tasks in the continuous implementation phases around metadata integration and continuus improvement of the metadata management architecture is one of the tasks in Phase 5. At this point, a very high-level process should be defined for how metadata management will move form the tactical implementation to the strategic approach. Not all of this work should be defined in Phase 2, all that is required is to establish an overall vision, an initial prototype and some checkpoints for continuous improvement. This process is an important part of the architecture in the overall Technology Blueprint.


Input:


Output:

Core Supporting Assets

Yellow Flags

  • Need to manage metadata is not recognised or seen as important
  • Strong resistance to using modelling tools, design being done only in word documents or excel

Key Resource Requirements

Wiki Contributors
Collapse Expand Close