Existing services could be reused as if or it could be necessary to implement intermediary services for reusing other
services that are not completely suited to the application, which is preferable than implement them again from scratch.
To keep track of the services, their contracts and associated software systems (implementation) are register in a
central Services Catalogue of services. In the SoaML component diagram an adapter or wrapper has to be defined to relate the design service to
its existing implementation, which will then be linked in Activity D4. If the service can be used as it is, then the
functionality of the adapter will be solely to call the existing component that implements the service; if it is
similar then the adapter will add or modify the existing functionality to suite the new requirements for the
service.
Example of wrapper definition taken from the SoaML standard:
|