초록

‘Customized-SOA services are loosely coupled’; this should not be a slogan but be physically present. For adopting such features, code for each service should be independent. Common coupling, external coupling, control coupling can be eliminated but data coupling and content coupling may not be removed. But these two coupling types can be handled in such a way that code for each CSOA-service can be treated as a single unit. Here author proposed a strategy to design a code for Customized-SOA service with handling data coupling and content coupling. Such type of code for a CSOA-service will be very useful for reusing service in another CSOA-application. And also such code can be easily changed according to needs of users.