QoS monitor as a service
- PDF / 1,318,088 Bytes
- 23 Pages / 439.642 x 666.49 pts Page_size
- 7 Downloads / 208 Views
QoS monitor as a service Taycir Bouasker1 · Mahjoub Langar2 · Riadh Robbana3
© Springer Science+Business Media, LLC, part of Springer Nature 2020
Abstract Quality of web service becomes more and more interesting as a distinguishing criterion to select a unique web service from all candidate ones. The quality assessment issue, especially regarding the volatility of the web services environment, is one among the main challenges in this context. In this paper, we propose a service-based system for web services monitoring. Compared with other efforts in this concern, our proposal is closer to the client’s non-functional requirements, more accurate and extensible to support new quality attributes. Keywords Quality of service · Monitor · Web service · Requirements · User preferences
1 Introduction Many companies have recognized the power of prepackaged services on the web. These components are seen as a good solution for rapid system development and heterogeneous systems interoperability challenges. Thus, the web service (WS) technology use had a trajectory of steady growth and it was hugely adopted by IT enterprises. They may utilize it to share and expose their own functionalities over the network as service providers (publishers) and/or reuse and consume some already published ones as service consumers (requesters). The extensive adoption of web services technology results on a large-scale of services accessible on the internet. This great number gives rise to offer proliferation, so a distinguishing criterion is necessary to choose one among all published proposals. This defines the Web Service Selection (WSS) process.
Taycir Bouasker
[email protected] Mahjoub Langar [email protected] Riadh Robbana [email protected] 1
Ecole Polytechnique de Tunisie, Monji Slim, Hammamet, Tunisia
2
Ecole Nationale des Ing´enieurs de Tunis, Ezzahra, Tunisia
3
Ecole Polytechnique de Tunisie, La Marsa, Tunisia
Software Quality Journal
Previously, the selection was based on functional properties. In other words, web service importance and interest were only judged according to its supplied function. However, with the unbroken increase of available web services in an exponential curve, there might obviously have functionally similar WSs. For that reason, functional properties defining “what” the service should do are no more sufficient to differentiate similar services offered by different providers. We have to rather focus on “how” the service should behave, which present non-functional properties. That is why we focus on the quality of service (QoS) which takes greater importance as a distinguishing criterion of functionally similar web services. Therewith, quality-related information are required and useful for both parties alike: web service provider and consumer. On the one hand, the provider will need to evaluate his web service to: – – – –
Position its service compared with others that may provide the same function. Highlight and prove to his clients the ability and performance of his web service
Data Loading...
