Software Service Evolution: A Requirements Perspective

Abstract

Abstract-Software service has to adapt to constant changes of requirements and environment, which would give rise to the concentration on service evolution. Among the many reasons for evolution, requirements are regarded as the major driving factor. However, most current work on service evolution focuses on different kinds of tactics to keep the compatibility between services and client applications, few of them treat requirements in priority. In this paper, we thoroughly survey the state-of-the-art studies on service evolution, including basic concepts, types, challenges and approaches; then analyze service evolution from four dissimilar dimensions, and for each one we identify the open problems and inadequacies. Based on our analysis and discovery, we argue that requirements driven service evolution would become an essential and promising research direction.

Design of Intelligent Public Transportation Vehicle Terminal Based on S5PV210

“…The software employed the Linux system as the operating system. And the Linux system has these advantages: (1)The sound codes of the inner core are totally open, and it has favorable tailing capability and customizability. (2)The Linux system can support the microprocessor broadly.…”

“…But when the signal of the GPS is weak, the terminal won't work well. And also in the area where the wireless communication signals are weak or not available, the terminal will not be able to transmit the information to the center, and the control center can't control and dispatch the vehicles [1]. In order to solve this problem, we designed an intelligence terminal in motorbus which employed the GPS combined with BD2.…”

Requirements-Driven Software Service Evolution

“…In software service evolution, the well-known challenge is to keep the compatibility between evolved service and existing client applications at either structural [7] or behavior level [8] [9]. Through our extensive survey [10], we found that starting from the definition of service evolution given by M. Papazoglou [9], many efforts have committed themselves to solve the problem by using kinds of tactics, such as versioning, design pattern/adaptor, model and theory [7], but few of them paid enough attention to the change propagation from requirements to services, one of the fundamental problem of evolution.…”