Aligning adequately business requirements and software functionality as well as achieving 'loose coupling' for service functionalities, are identified challenges relevant to service-oriented software design. Furthering previous related work, we propose in this paper an application design process that, taking the above challenges into account, addresses systematically and separately business requirements, the identification of (desirable) service functionalities, and their mapping onto technology platforms. With respect to service modeling, a communication pattern has been identified that is relevant and useful. As for the enforcement of social restrictions in the application functionality, semiotic norms are helpfully applied. And finally, 'loose coupling' is achieved in an orchestration-driven way.
['Boris Shishkov', 'M.J. van Sinderen', 'Bedir Tekinerdogan']
Model-Driven Specification of Software Services