Roadmap: How to Adopt the Service Realization Practice
This roadmap describes how to adopt the Service Realization practice.
Main Description

Start by reviewing the following key concepts and tasks:

These will introduce you to the basics of what you need to know about service realization.

After reviewing those topics, you can review the tasks, concepts, guidelines, and work products associated with the practice.

If you are primarily interested in realizing information services, focus on this task:

If you are mainly interested in understanding how to realize the Service Components layer, focus on this task:

Common pitfalls

Successful execution of this practice is made more difficult if organizations service-enable existing assets without due consideration of the service interfaces that are needed to support the business. 

It is easy to focus on service function and neglect nonfunctional aspects of the service specification, such as performance and scalability. The Perform Detailed Technical Feasibility Exploration task is provided to mitigate this risk.

With respect to information services, a common pitfall is to establish one-to-one correspondence between data management services and data elements (for example, mapping each service to a single table in a relational database). This often results in excess data access operations. It is often better to have each service mapped a multiple data elements that have strong affinity with each other.

Measures of success

  • A realization strategy has been defined and documented for each service component.
  • Each realization meets or exceeds the nonfunctional requirements for the service component that it realizes.
  • Each component involved in realizing each service has been allocated to an appropriate architectural layer.