[2] These reusable services are designed so that their solution logic is independent of any particular business process or technology.
However, little is done in designing the service logic in a manner that it could be reused to automate multiple business processes.
Contrary to this, the actual reuse relates to when the service is used to automate multiple business processes.
The service reusability principle addresses these misconceptions by providing a set of guidelines that help to design services containing logic which is not linked to any particular business process and hence could be reused across the enterprise for automating multiple business processes.
In order to concentrate on the quality of the logic, the service reusability requires exploring the business domain as well as the current technologies in use.
The application of this principle before the finalisation of service capabilities provides an opportunity for fine tuning and refactoring the logic in support of making it reusable.
The application of this design principle requires performing a top-down service-oriented analysis process[7] in order to arrive at a complete set of candidate services.