Service specification begins with an initial list of candidate
services, which is developed by, for example, Practice: Service Identification. The Task: Apply Service Litmus Test is performed to determine which of the
candidate services will be taken through the full service specification process
and finally exposed.
After this initial list of services to be exposed is defined, Task: Specify Service-Oriented Solutions is performed to specify the services,
the Participants
that provide and use them, the schemes for assembling the Participants
into a solution for the given business problem, and the behavioral contracts
that govern interaction between service providers and consumers.
The tie between the business realm and the IT solution is strengthened by
executing Task: Perform Subsystem Analysis. This task results in a mapping between the Functional
Areas of the business that are impacted by the business problem and Service
Components that are selected to realize the services that collectively provide
the solution.
The realizations of the service components, specifically, are specified in
Task: Perform Component Specification. This is an application of conventional
component-based design principals.
The four core tasks are supported by Task: Document Service Non-functional Requirements and by Task: Refactor the Service Model. The first task ensures that nonfunctional requirements,
such as performance, scalability, and security concerns are not neglected during service
specification. The second task is performed to improve the maintainability and
extensibility of the defined solution. |