Overall Implementation Guide Overview

From MIKE2.0 Methodology

Mike2 content model oig.jpg

The Overall Implementation Guide collates all of the content contained within MIKE2.0 framework. In a nutshell, the guide is the organizing framework for bringing everything together. The Overall Implementation Guide is comprised of the following:

• Overview and Key Concepts introduces users to a new set of enterprise models and the concept of Information Development. The latter is especially important, as it is used extensively throughout the MIKE2.0 Methodology. It helps users understand the benefits of superior information management.

• The section on Rationale details the development of the MIKE2.0 approach. It further details why the solution was created and a bit of the history on how it took its current form.

• The Overall Task List provides the overall set of Phases, Activities, and Tasks for MIKE2.0.
  
• The Usage Model provides some guidance on how these tasks are applied to different types of projects.

To better appreciate the activities and tasks of the Overall Implementation Guide, it is useful to describe the architecture framework and delivery model at a high level. This includes:

• SAFE (Strategic Architecture for the Federated Enterprise). This is the architecture framework that supports all aspects of the methodology. Understanding SAFE provides a rationale behind many of the architecture and design-centric tasks.

• Information Governance Solution Offering. This helps users understand the skills that will be required on the team, how tasks are to be structured, and some of the guiding principles around the MIKE2.0 delivery approach.

Note that the development of the methodology is a continuous process. To this end, MIKE2.0 has been constructed in a fashion that allows functionality to be added underneath the Overall Implementation Guide and governing architecture.

When undertaking a project, users of the MIKE2.0 Methodology are best served as follows: 

• start with this Overall Implementation Guide
• look at the MIKE2.0 Usage Model
• then use the more detailed assets