WSMoD: A Methodology for Qos-Based Web Services Design

WSMoD: A Methodology for Qos-Based Web Services Design

M. Comerio (Università di Milano Bicocca, Italy), F. De Paoli (Università di Milano Bicocca, Italy), S. Grega (Università di Milano Bicocca, Italy), A. Maurino (Università di Milano Bicocca, Italy) and Carlo Batini (Università di Milano Bicocca, Italy)
DOI: 10.4018/978-1-61520-684-1.ch002
OnDemand PDF Download:
$37.50

Abstract

Web services are increasingly used as an effective means to create and streamline processes and collaborations among governments, businesses, and citizens. As the number of available web services is steadily increasing, there is a growing interest in providing methodologies that address the design of web services according to specific qualities of service (QoS) rather than functional descriptions only. This chapter presents WSMoD (Web Services MOdeling Design), a methodology that explicitly addresses this issue. Furthermore, it exploits general knowledge available on services, expressed by ontologies describing services, their qualities, and the context of use, to help the designer in expressing service requirements in terms of design artifacts. Ontologies are used to acquire and specialize common knowledge among the entities involved in service design, and to check the consistency of the web service model with constraints defined by provider and customer requirements. To improve the effectiveness of the process, the authors propose a Platform Independent Model that includes the description of specific context of service provision, without considering implementation details. The discussion of a QoS-based web service design within a real case study bears evidence of the potentials of WSMoD.
Chapter Preview
Top

Introduction

Web services provide added value e-services over the Internet by overcoming the limitations of existing component models. Web services take advantages from the Universal Resource Identifier (URI) model to support open naming and addressing systems. They exploit XML features to supply rich descriptions of involved concepts, such as WSDL descriptions to service interfaces, UDDI to service lookup, SOAP to service interoperability, and Ws-BPEL to service orchestration.

Web services are the building blocks of the Service Oriented Architecture (SOA) a paradigm focused on the composition of loosely coupled systems. In this architecture, a service provider publishes its web services in a registry that can be searched by a consumer who can then access to a service, which has been found directly by means of XML-based messages. The increasing availability of web services offering similar functionalities (for example in bookselling or hotel reservation domains) creates new opportunities in discovery and selection activities. In fact, the selection of a web service can not only be related to what operations are offered, but also to how those operations are provided. Consequently, Quality of Services is becoming a crucial issue for the selection of web services that fulfill customer requests better.

In this novel scenario, business requirements support the discovery of web services and the development of new ones. In fact, web service design should start from business needs and business processes, instead of starting from application features as in traditional software design. Such business requirements should drive the identification of the needed features, potential suppliers, technological, organizational, and social constraints. Therefore, the development process requires a change in the overall approach.

In this paper we present WSMoD a Web Service Modeling Design methodology for quality of service (QoS)-based Web Services. The approach of the methodology consists in considering non-functional aspects derived from business requirements, as well as functional requirements, and incorporating and refining them throughout the design process. In this paper we use the term functional, to mean the operations that a service is expected to provide, and the term non-functional (or sometimes with the general term quality) to collect all the other characteristics associated with a service, related to QoS, user profiles, and delivery channels. The advantage of managing qualities, users and channels along the design process is twofold: achieving at the end of the process, a ready-to-implement specification, and reducing the risk of delivering unsatisfactory services. In fact, the knowledge of the technical, organizational and social characteristics of the environment in which the service will be deployed allows the designer to effectively evaluate and customize the design of the service.

WSMoD extends the Model Driven Architecture (MDA) proposed by (OMG, 2004), whose development process is divided into three steps: (i) first, a Platform Independent Model (PIM) is created, expressed in UML; this model describes business rules and functionalities of the application, and exhibits a high degree of platform independence; (ii) then, a Platform Specific Model (PSM) is produced, mapping the PIM into a specific platform; (iii) finally, the application is generated. The proposed extension is in two directions. The first one, according to the well-known software engineering principle “divide et impera”, adds in the definition of the platform independent model a specific methodological step for the definition of the non-functional requirements. Users and channels, which support the interaction between web services and users, should be considered first-class concepts in the analysis and design of new services. The second extension concerns the platform independent model to represent quality aspects and the specific context related to user profile and channel constraints. This kind of context is still independent from a specific deployment platform, so that it can be adapted to different providers offering new web services. The goal of this extension of Platform Independent Model is to improve the design of software applications by avoiding modelling choices that are not deployable in real provisioning environments.

Complete Chapter List

Search this Book:
Reset