Open Framework, Information Management Strategy & Collaborative Governance | Data & Social Methodology - MIKE2.0 Methodology
Wiki Home
Collapse Expand Close

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.

Identify Common Services Deliverable Template

From MIKE2.0 Methodology

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.


In the Identify Common Services task, candidate services are identified where building reusable integration and data management capabilities would be of particular value and inline with the overall architectural approach. The inventory of existing services should also be checked as part of this process to determine if existing services have already been built to provide required functionality. A centralised container provides the repository of existing services; different technologies use different types of service containers (e.g. UDDI for Web Services).

Example 1 - Common services indentified for a SOA solution

Wiki Contributors
Collapse Expand Close