Ws-Contract Establishment With Qos: An Approach Based on Feature Modeling

Abstract

Electronic contracts describe inter-organizational business processes in terms of supply and consumption of electronic services (commonly Web services). The establishment of e-contracts in a particular business domain usually involves a set of well-defined common and variable properties. These properties are not fully exploited by the existing e-contract establishment approaches. Feature modeling is a software engineering technique that has been widely used for capturing and managing commonalities and variabilities of product families in the context of software product line. This paper presents a feature-based approach to support Web services e-contract (WS-contract) establishment. The approach aims at improving the information structure and reuse of WS-contracts, including the QoS attributes. Features are used to represent possible WS-contract elements in order to drive WS-contract template instantiation, thus acting as a configuration space manager. A toolkit named FeatureContract was developed to automatically support the proposed approach. A case study was carried out within the telecom context to show the approach feasibility.

Feature Model as a Design-pattern-based Service Contract for the Service Provider in the Service Oriented Architecture

“…As illustrated in the introduction (see Problems P.1, P.2, P.3, P.4, P.5, P. 6 and P.7), the SP feature modeling approaches that have been proposed in the literature [5], [6], [7], [8], [9], [10], [11], [12], [13], [14], [15], [16] notably the SOA traditional service contracts WSDL [5] and WADL [6] suffer from several problems to develop SPs. This prevents to efficiently realize IAD Requirement.…”

“…In the literature, many works have been proposed to model the features and variability of SP and DPs [5], [6], [7], [8], [9], [10], [11], [12], [13], [14]. In Table 3, we present these works and compare them with our approach notably with our F M SP (see Fig.…”

“…As an instance, the HTTP methods (post, get, put and delete) that can be used by REST and the versions of SOAP are not modeled. Fantinato et al [9] elaborate a FM that models the features of the communication technology SOAP. These two FMs [8], [9], as reported by their authors, need to be extended with the features (e.g., input and output data) of capabilities and services of SP so they can generate fully functional SPs.…”

“…In the literature, many SP feature modeling approaches have been proposed [5], [6], [7], [8], [9], [10], [11], [12], [13], [14], [15], [16] notably the two widely used service contracts: Web Services Description Language (WSDL) [5] and Web Application Description Language (WADL) [6]. These service contracts are represented with XML documents, with different notations, through which the features of the communication technologies SOAP and REST are modeled, respectively.…”

Using contract and ontology for privacy protection in Service-Oriented Architecture

“…Contracts follow an approach based on feature modeling [5]. In addition, contracts use a base ontology for e-services, which provides a vocabulary for the establishment of privacy contracts between service consumers and providers.…”