Using Finite State Models for Quality Evaluation at Web Service Development Steps

Abstract

This paper presents a short study on evaluating the web service quality based on finite state models using the wellknown metrics of Quality of Service (QoS) and Quality of Experience (QoE). These metrics represent objective and subjective assessments. The development of any web service involves several steps and the final values of the service QoS and QoE can be essentially improved/deteriorated based on the quality reached at each development step. In this paper, five service development steps are considered: those are requirements specification, provisioning, composition, implementation, and usage and management. At each step different finite state models for refining the service quality estimation are utilized. A running example of a vacation planner service illustrates the application of finite state models to improve the accuracy of the QoS and QoE evaluation. Keywords: web service; quality of service (QoS); quality of experience (QoE); finite state models; attribute/parameter; composite service quality.

Toward a contextual quality of service evaluation approach

“…The evaluation process helps in answering specific questions raised by decision makers and defines basic user concerns with the quality of web services. Hence, an efficient evaluation or measurement of user satisfaction or experience can mostly be achieved when taking into account both QoS and QoE of a web service (Kondratyeva et al, 2013). There are other approaches that try to address different methods for web service QoS using the algorithms to modify QoS attributes weight dynamically, automatically and objectively (Lin et al, 2014).…”

Mobile hosting and sensor eco-system for radiation detection

“…In Kondratyeva et al [3], the authors emp techniques to perform services composition Service composition involves the aggregat service end-points (e.g., multiple web-based form a single workflow. The authors adopte composition flow patterns as shown in Figu conditional, parallel, synchronization, concurre [3] The sequential flow enables the invocatio S 1 , after service S 0 has ended.…”

“…The authors adopte composition flow patterns as shown in Figu conditional, parallel, synchronization, concurre [3] The sequential flow enables the invocatio S 1 , after service S 0 has ended. The conditiona service S 0 can only invoke one service betwee S k .…”