Create or refine the model of the service in Project SAVARA modeling tool and or Service Repository. Provide meta-data to define the high level properties of the service, and the link(s) to relevant artifacts that can be used to infer the service interface. For example, WSDL can be used to define the static interface, or a BPMN2 process model can be used to derive a behavioral service interface.
A candidate service was defined as part of Service Oriented Analysis. As part of Service Oriented Design we want to review the Service to make certain that it is still required.
Where existing services have been associated with a service candidate (i.e. the skeleton service model), but that don't provide the exact requirements of the service candidate, then this phase will determine what additional work is required to deliver the required service – whether this involves modification to the existing service, or the development of a new service that may leverage the existing service(s).
Repo: Promote service lifecycle to Service-Oriented Design stage. Establish dependency between service model and choreography containing behaviour of service, if this does not already exist. Add additional metadata about the service, such as security policies and SLAs.
Input: Service candidate, choreographies containing service
Output: Service model with additional metadata.