From MIKE2 Methodology
|
| 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.
|
Overview
Data Management Services are reusable aspects of the Data Re-Engineering process that are implemented as part of the Services Oriented Architecture. It should be known during the Roadmap whether some of these processes may eventually be turned into run-time components. In that case, the design should take into consideration the potential reusable aspects of the Data Re-Engineering process to standardise, correct, cleanse or enrich data. Data Re-Engineering services are invoked by other services, oftentimes as part of a set of transformations within either the Interface Service or Mediator Service.
Example 1 - Data Management Services example
Introduction