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.

Information Development Logical Architecture Deliverable Template

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
Under construction.png
This article is currently Under Construction. It is undergoing major changes as it is in the early stages of development. Users should help contribute to this article to get it to the point where is ready for a Peer Review.
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 Information Development Logical Architecture task defines the current state information management architecture at the logical architecture level. Interviews should be conducted with technology staff members to define the current systems, noting any currently planned changes including any constraints that may exist.

Contents

Example for an Information Development Architecture

Information Architecture Overview

The information architecture is intended to provide a common

  • Semantic representation of data objects and their related services to support the process flow;
  • Definition of stored information to support operational and MIS needs.
  • The architecture consists of 3 parts: the operational data, MIS/reporting and the services model.

Operational Information Architecture

The operational information architecture consists of a:

  • Data component model that is derived from programme information and process requirements. It provides a common semantic representation of data and related services required to support the tier and layer architecture of the solution.
  • A services model representation that also applies to the XML messaging between the different systems in the architecture.
  • Object model that is derived from solution information needs. It will be the basis for the physical database required to store operational information.
  • All unstructured data will be stored in the Content Engine.

Analytical Information Architecture

The Analytical information architecture consists of:

  • Data sources to support the query, reporting and analytical requirements of GK
  • Data models (multi-dimensional) to support the analytics
  • System components required to support the MIS reports, query and analytics

Services Information Architecture

  • The Business Object Model (BOM) defines the information requirements and their relation to an application component functionality
  • It will then be transformed into a data component model supporting the tier and layer architecture; and a relational data model supporting the persistency of operational information
  • Similarly, analytical data model is built based on MIS requirements, the BOM and input from Business Analyst
  • It will then be transformed into a relational and multi-dimensional data model supporting MIS reporting and analytical needs
Wiki Contributors
Collapse Expand Close