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.

Services Oriented Architecture Design

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search

Activities in Phase 4
Phase 4 - Design Increment
Content Model Relationship

Contents

Activity:

Objective

If the Solution Architecture defines an approach for using a Services Oriented Architecture, this activity should be followed as part of the design process. It will align closely with many other aspects of design, especially related to the modelling of messages and the integration layer.

As with the ETL Logical Design, these tasks can be performed in parallel. Their definitions here are to illustrate key aspects of the solution more than a step-wise set of tasks to follow.

Major Deliverables

  • Interface Services
  • Business Services
  • Data Management Services

Tasks

Identify Common Services

Objective: In this 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).

Input:

This is a modification to the ETL design process. It should be done as part of the ETL logical and physical design and can be done in parallel with the other processes.

Output:

Identify and Design Interface Services

Objective:

Interface Services are built to provide an abstracted interface of an application into the integration environment. The logical and physical design process for ETL that applies to the application or database interface should be applied in this area and interface services should represent discrete sets of business functionality. Interface Services transform data into the Common Messaging Model.


Input:

This is a modification to the ETL design process. It should be done as part of the ETL logical and physical design and can be done in parallel with the other processes.


Output:

Identify and Design Business Services

Objective:

Business Services represent the process flow of information between different systems and are also sometimes referred to as Mediation Services. The logical and physical design process for ETL that applies to the flow of information from source to target should be applied in this area. Business Services and Interface Services interact through the Common Messaging Model; Business Services also transform data into the Common Messaging Model.


Input:

This is a modification to the ETL design process. It should be done as part of the ETL logical and physical design and can be done in parallel with the other processes.


Output:

Identify and Design Data Management Services

Objective:

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.


Input:

This is a modification to the ETL design process. It should be done as part of the ETL logical and physical design and can be done in parallel with the other processes.


Output:

Core Supporting Assets

Yellow Flags

  • Do not have a repository model for defining, modelling and sharing services
  • Reuse criteria not established

Key Resource Requirements

Wiki Contributors
Collapse Expand Close

View more contributors