This is a "project-scope" workflow; the assumption is that the project continues with Service Specification
activities. If a project is being executed where service identification results are the end products, consider
performing the "Service Litmus Testing" activity from the Rational SOMA Service Specification practice as the terminal
activity in the workflow. Doing so provides you with a ready list of services to be defined and implemented
during future endeavors.
The workflow begins with goal-service modeling, to help emphasize the importance of ensuring that the SOA ties back to
the business strategy. If you are beginning with an empty candidate service portfolio, it might be difficult to
describe meaningful, goal-fulfilling candidates that also fit well with candidates discovered during the other
activities, such as Business Model Analysis. You can address this issue in a number of ways, including:
-
Pay particular attention during refactoring activities to the need to reconcile the services discovered during
goal-service modeling with the services discovered during other activities; or
-
Delay goal-service modeling. In some cases, it can be useful to dispense with the initial Goal-Service
Modeling activity entirely, and focus on using the second instance, which ends the illustrated workflow, as a
"catcher" activity to ensure that each goal is served by a candidate service.
|