Task: Document Service Realization Decisions
Decide how each service component is to be realized, to satisfy the service specification's functional and non-functional requirements.
Purpose

To provide a component model that specifies how each service component is to be realized.

Relationships
Main Description

This task leverages the Service Model and Asset Fit Gap Analysis to make definitive decisions regarding how the services will be realized to satisfy their requirements.  These decisions can be documented either by adding more detail to the Component Model, or by capturing this information as part of Architectural Decisions.  Example: Rent-a-Car Realization Matrix provides a simple tabular structure that can be used to document the decisions.

Refer to Guideline: Making Realization Decisions for details and commentary for each of the task steps. 

Steps
Determine Sourcing Approach

Use the Service Model, Software Architecture Document, and the Asset Fit Gap Analysis to determine the best approach for realizing each Service Component that is described in the Component Model. Use the SOA architect to guide and inform your decisions. Document the approach by adding more detail either to the Component Model or to the Architectural Decisions artifact. 

Example: Rent-a-Car Realization Matrix illustrates one format that can be used to document the realization decisions textually within the Architectural Decisions document.

Determine Development Approach
Once the scheme for realizing each service component has been defined, decide how the realization will be implemented.  Guideline: Making Realization Decisions provides advice regarding this decision.  This decision can be documented in the Architectural Decisions document or a textual adjunct to the Component Model.
Perform Fine-Grained Mapping of Existing Assets
In cases where existing assets provide the service component realizations, decide how each asset will be service-enabled.  Options are presented in Guideline: Making Realization Decisions. Once the decision has been made, document it either in the Component Model or in the Architectural Decisions document.
Properties
Multiple Occurrences
Event Driven
Ongoing
Optional
Planned
Repeatable