Services are offered by tailoring it according to the requirement of customer, so it is nothing like we can use the service created for one customer in the other customer's scenario. If in case we need to use the same service in other scenario, then we will tailor it to be used in the different system landscape.
In other way, it is not a single service which satisfy the complete requirement but it is a set of services which work together to meet the requirement. If we are using same service in two different scenarios the the system landscape or the set of different services for different functionality will make this unique.
You can re-use a complete service, or u can re-use a atomic service which is part of a composite service. If you really wanted to enforce re-usability you have to first build a service taxonomy relevant to service context and start making service consumer to think in terms of services instead of functions.
We have developed a good service taxonomy approach ad detailed below which will help you to put all of your services in an enterprise level into different group. This will lead us to build a catelog and catelog promot people to look for service usability.
Infrastructure services
Set of services that are part of the supporting distributed computing infrastructure
Infrastrucure services are further divided into
Communication Services: Provide message-transfer facilities such as message-routing and publish-subscribe.
Utility Services: Provide capabilities unrelated to message transfer such as service-discovery and identity federation.
Application service is another major group
Application Services:Set of services that are part of the composite application which is running in distributed computing infrastructure
Application Services are further divided into
Entity Services Expose and allow the manipulation of business entities.
Capability Services Implement the functional building blocks of the application (sometimes referred to as components or modules), also referred as TASK centric. Capability is plural in context with the meaning of ability to perform actions and in technical context it mean a composite service of TASKS)
Activity Services Implement the functional building blocks of the application (sometimes referred to as components or modules), also referred as TASK centric. Activity is singular in context mean it mean an atomic service task orientation.
Process Services Compose and orchestrate entity, capability, and Activity Services to implement business processes
If you can build service taxonomy like this in horizontal approach you can get re-usabilty just like a commercial catelog company make people to buy the products from the catelog.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.