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.

Overview and Key Concepts

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search

Overview and Key Concepts introduces the governing model for the MIKE2.0 Methodology. It introduces the scope of the approach and why it is necessary to meet the changing technology environments in many of today's organisations. MIKE2.0 encompasses a comprehensive approach to Enterprise Information Management (EIM), which is defined and applied in the following manner:

  • To meet the needs of today's rapidly changing business and technology needs, many organisations may need to move to a new model. The scope of the model is defined through a Conceptual Architecture and Enterprise Views. The Conceptual Architecture is focused on defining scope along solution capabilities. For their part, Enterprise Views apply to People, Process, Organisation, Technology and Strategy across the domains of Applications, Infrastructure, and Information, represented as follows:
Enterprise Views and Domains

At any point in methodology, we can trace back to the Conceptual Architecture or Enterprise Views.

  • There are many reasons for moving to this new model. Rationale provides some of the history and thought-process undergone by BearingPoint in this proposed model of Enterprise Views. It also helps explain some of the motivations behind MIKE2.0.
  • The crux of the MIKE2.0 Methodology is stored in distributed documents, tools, articles, and web content. In order to make this content flow together for the end user, MIKE2.0 provides a model that organises the content and its relationships through the overall set of tasks and components in the architecture. The Content Model for MIKE2.0 describes the different types of content and their relationships.
  • All MIKE2.0 content is housed within a collaboration framework. It's important to note that the framework enables moving the methodology to a more effective model for sharing, building, and improving content.

In summary, Overview and Key Concepts (OKC) helps define the scope of the MIKE2.0 methodology. It provides the following: 

Wiki Contributors
Collapse Expand Close

View more contributors