Abstract

With the proliferation of web services, the selection process, especially the one based on the non-functional properties (e.g. Quality of Service – QoS attributes) has become a more and more important step to help requestors locate a desired service. There have been many research works proposing various QoS description languages and selection models. However, the end user is not generally the focal point of their designs and the user support is either missing or lacking in these systems. The QoS language sometimes is not flexible enough to accommodate users’ various requirements and is too complex so that it puts extra burden on users. In order to solve this problem, in this thesis we design a more expressive and flexible QoS query language (QQL) targeted for non-expert users, together with the user support on formulating queries and understanding services in the registry. An enhanced selection model based on Mixed Integer Programming (MIP) is also proposed to handle the QQL queries. We performed experiments with a real QoS dataset to show the effectiveness of our framework.

Highlights

  • We propose an enhanced selection model based on Mixed Integer Programming (MIP) [2]

  • We started our thesis by reviewing various researches on QoS query language descriptions and selection models

  • We proposed our new QoS query language and selection model to support the solution for these problems, and we specially emphasized on the support for the user-centric selection process

Read more

Summary

Introduction

“A Web Service supports direct interactions with other software agents using XML-based messages exchanged via Internet-based protocols.” [1] This description emphasizes that a web service needs to be defined by its provider, advertised by its provider or a third party, and afterwards discovered by clients, in addition a web service has the capability to be combined and interacted with other web services to function as a new composite web service, in an Internet standard environment. Each provider describes its web service functionality in a WSDL (Web Service Description Language) standard file and publishes it on UDDI (Universal Description, Discovery and Integration) repository. The discovery process, based on functional requirements, won’t be completely accurate without nonfunctional features (such as availability, response time, etc). There should be QoS (Quality of Service) or non-functional matching in addition to the functional matching

Objectives
Results
Conclusion

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.