MIKE2:Extensions

From MIKE2.0 Methodology

This article is a key aspect of the Open Methodology Framework and has therefore been protected. Propose changes to this article on its corresponding discussion page.

An Extension to MIKE2 is a proposed addition to the Core MIKE2.0 Methodology that has the impact of adding or changing existing Activities or Tasks that make up the Overall Implementation Guide. Extensions to MIKE2.0 may also have the impact of changing MIKE2.0 Solutions that are part of the core approach.

Extensions are typically brought in as Supporting Assets. Extensions can be proposed at any time, but are only incorporated as part of a Release Cycle.

Criteria for Making an Extension

Extensions have the following properties:

• Is of high general value for many different types of projects
• Is of very high quality
• Aligns well with the overall approach to Information Development
• Has gone through an extensive Peer Review process, including a review by the DGMC

Criteria for Recommending an Extension

Supporting Assets with the following properties are generally thought of as inappropriate to consider as an extension to the core approach:

• A vendor-specific approach that applies only to that vendor
• Focused only on a niche technology area
• Techniques are under significant debate

Peer Review Process

Recommending an Extension is similar to the process for a Peer Review in that the discussion related to its inclusion into the Overall Implementation Guide is done through Talk Pages.

To identify an article as a Extension to MIKE2.0 for DGMC Review, place the Extensions to MIKE2 Template in the Talk Pages of the article by adding the following text to the top of the page: [[{Extensions to MIKE2}]]

Within the Talk Page of the article, the authors should propose the rationale behind the extension

Examples of Recommended Extensions

The complete inventory can be found here