Design Web Services: Towards Service Reuse at the Design Level

Abstract

<p class="MsoNormal" style="text-align: left; margin: 0cm 0cm 0pt; layout-grid-mode: char;" align="left"><span class="text"><span style="font-family: ";Arial";,";sans-serif";; font-size: 9pt;">Service oriented software development has gained more and more importance in the area of e-business. Most researchers focus on the semantic description of Web services and automated composition but pay little attention to how to design Web services for supporting service reuse effectively, thus a substantial amount of modeling and programming is still required. In this paper, a pattern oriented service design method is presented by which all components of different abstraction levels are uniform in regard to their specifications and composition mechanism. Pattern oriented service design model provides a traceable and explicit link from business components to software components so that the top-down service reuse at design level is supported, and the service maintainer profits from the traceability because the impact of requirement or design modifications can be better assessed. The semantic information of component specification can support semantics based component reuse. The pattern oriented service design model can improve development productivity by offering a better chance of reuse through better modularity.</span></span><span style="font-family: ";Arial";,";sans-serif";; font-size: 9pt;"></span></p&gt

Towards a Supporting Framework for Public Web Service Efficient Reuse: A Model Based on Social and Collective Usage Experience

“…The existing works on reusable Web services are mostly focused on service providers rather than considering end-user perceptions on services. In Dan et al (2008), reusing Web services refers to good governance in SOA lifecycle. The proposal is very enterprise oriented and consists of using a common language with consistent business term to describe services, governing new service creation and discovery of existing services, providing assurance to both service users and owners and supporting new requirements against existing services.…”

“…The proposal is very enterprise oriented and consists of using a common language with consistent business term to describe services, governing new service creation and discovery of existing services, providing assurance to both service users and owners and supporting new requirements against existing services. Following the same idea, the proposal in Chu and Qian (2009) considers designing reuse-oriented Web service through a top-down process by modelling business requirement as business processes, breaking them down and identifying fine-grained requirement before the real service design. These two solutions may be applied efficiently in supervised and inter/intra-corporate environment where business terms can be controlled by internal glossary or domain ontology; business processes are predefined, imposed and slightly evolving, and expertise in SOA governance is present.…”