Usage Model for Information Strategy, Architecture and Governance

From MIKE2.0 Methodology

Listed below are the activities required for Information Strategy, Architecture and Governance. Refer the corresponding Solution Offering for the context in which these offerings are used as well as any gaps in the overall model.

Activity Indicators

The indicators below define the typical level of applicability of MIKE2.0 Activities for different types of projects. This model is a high-level starting point to provide a guide as opposed an exact mapping of required activities. If in doubt, it is better to assume that the Activity is in scope as a starting point. It can always be skipped later in the project.

Activity Indicators for MIKE2.0 Not Rated Yet Not Performed Typically not Performed May be Performed Should be Performed Definitely Performed

Potential Changes to Ratings within this Group

There are a number of examples where the ratings for this offering group may change. Examples include:

• The SOA, EII and Model Driven Architecture Solution Offering only goes to the architectural level. It may be better to have this offering go through the design and build as well.

• There are large degrees of overlap between the offerings and some are inclusive within others. It would be useful to find a way to make this more clear within the Usage Model

• The "top down" strategies should be balanced by more bottom-up models.

• Product selection should be to focus just on products - these change quickly - it should focus on standards, architecture and required capabilities. Therefore a IM Strategy and Architecture model that is a bit more dynamic may be valuable.

• Might create an Enterprise Information Management Strategy Solution Offering that combines Data and Content Management in an integrated fashion.

Activities Required from the Overall Implementation Guide

The rows down the left-hand side show the Activities of the Overall Implementation Guide. Columns are represented by typical projects to which the MIKE2.0 Methodology is applied. Clicking on the project users to appropriate MIKE2.0 Solutions that can also be used for these types of projects.

A number of new activities may be added to the Overall Implementation Guide to support Information Management Strategy, Architecture and Governance.

MIKE2.0 Methodology Usage Model Phases Activites and Tasks Typical Projects where MIKE2.0 can be applied Information Governance SOA, EII & MDA EDM Strategy (Top Down) ECM Strategy Enterprise Info Assessment IM Center of Excellence Phase 1 - Business Assessment and Strategy Definition Blueprint Activity 1.1 Strategic Mobilisation Activity 1.2 Enterprise Information Management Awareness Activity 1.3 Overall Business Strategy for Information Development Activity 1.4 Organisational QuickScan for Information Development Activity 1.5 Future State Vision for Information Management Activity 1.6 Data Governance Sponsorship and Scope Activity 1.7 Initial Data Governance Organisation Activity 1.8 ROI of Information Assets Activity 1.9 Business Blueprint Completion Activity 1.10 Programme Review Phase 2 - Technology Assessment and Selection Blueprint Activity 2.1 Strategic Requirements for BI Application Development Activity 2.2 Strategic Requirements for Technology Backplane Development Activity 2.3 Strategic Non-Functional Requirements Activity 2.4 Current-State Logical Architecture Activity 2.5 Future-State Logical Architecture and Gap Analysis Activity 2.6 Future-State Physical Architecture and Vendor Selection Activity 2.7 Data Governance Policies Activity 2.8 Data Standards Activity 2.9 Software Development Lifecycle Preparation Activity 2.10 Metadata Driven Architecture Activity 2.11 Technology Blueprint Completion Phase 3 - Information Management Roadmap and Foundation Activities Activity 3.1 Information Management Roadmap Overview Activity 3.2 Testing and Deployment Plan Activity 3.3 Software Development Readiness Activity 3.4 Detailed Business Requirements Activity 3.5 Business Scope for Improved Data Governance Activity 3.6 Enterprise Information Architecture Activity 3.7 Root Cause Analysis of Data Governance Issues Activity 3.8 Data Governance Metrics Activity 3.9 Database Design Activity 3.10 Taxonomy Design Activity 3.11 Message Modelling Activity 3.12 Metadata Development Activity 3.13 Data Profiling Activity 3.14 Data Re-Engineering Activity 3.15 Business Intelligence Initial Design and Prototype Activity 3.16 Solution Architecture Definition/Revision Activity 3.17 Prototype the Solution Architecture Phase 4 - Design Increment Activity 4.1 User Support & Operational Procedures Design Activity 4.2 Business Intelligence Design Activity 4.3 Information Security Design Activity 4.4 Infrastructure Management Process Design Activity 4.5 ETL Logical Design Activity 4.6 ETL Physical Design Activity 4.7 User Collaboration Design Activity 4.8 User Interface Design Activity 4.9 Services Oriented Architecture Design Activity 4.10 Test Design Phase 5 - Incremental Development, Testing, Deployment and Improvement Activity 5.1 User Support & Operational Procedure Guides Activity 5.2 Technology Backplane Development Activity 5.3 BI Application Development Activity 5.4 Functional Testing Activity 5.5 System Integration Testing Activity 5.6 End-to End Testing Activity 5.7 Stress and Volume Testing Activity 5.8 User & Operations Training Activity 5.9 Production Deployment Activity 5.10 Evaluation and Launch Activity 5.11 Continuous Improvement - Compliance Auditing Activity 5.12 Continuous Improvement - Standards, Policies and Processes Activity 5.13 Continuous Improvement - Data Quality Activity 5.14 Continuous Improvement - Infrastructure Activity 5.15 Continuous Improvement - Information Development Organisation Activity 5.16 Project Closeout