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.

Advanced Capabilities for Information Development Deliverable Template

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
Under review.png
This article is a stub. It is currently undergoing major changes as it is in the very early stages of development and is only a placeholder. Please help improve MIKE2.0 by adding to this article.
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 Advanced Capabilities for Information Development task defines the need for more advanced capabilities in the area of Information Management. This includes both architectural implementations (e.g. reusable services) and more enabling technologies (e.g. modeling data in motion). In defining the future-state conceptual architecture, it is important to take note of the timeline when different capabilities will be deployed, as this should be represented in the final blueprint.

Examples

Mapping Business Requirements to Technology Requirements

The goal should not to be to provide an exhaustive list and spend too much time on analysis, but to ensure that the major business requirements map to the functional capabilities.

Foundation Capabilities for Information Development are separated from advanced capabilities MIKE2.0 to ensure there is coverage of the basics. The model shown to the right is an example capability list.

Requirements Mapping Model

A simple requirements mapping model can be defined as shown to the right although use of a tools-based approach is generally better than the approach shown in this model. This is particularly important to accommodate change control and many-to-many relationship for requirements mapping.

Factors Business Requirement Technology Capability Evaluation Against Requirement
Wiki Contributors
Collapse Expand Close