Abstract—Service orientation has become an attractive solution to many software development and integration problems. To fully adopt the service orientation concept, business organizations need to learn about a new methodology for service architecture and employ it to their existing software systems. Such an effort is likely to pay off later when the service-based systems can accommodate changes in a more flexible way. However, since the benefits are not seen right away, this could deter business organizations, especially smaller enterprises, from service adoption. This paper presents an experiment to determine agility to change of a service-based system in comparison with that of a non-service-based one to check if the service-based version is more agile to change. The two experimental systems are in the context of an E-Leave application of a small software company in Thailand. The model we use to measure agility extends an existing software agility metric by bringing code complexity into the model. The experimental results show that the service-based system is more agile to change than its counterpart, while code complexity can help give a better view of change complexity that affects agility.We also note that agility of the service-based system can be improved if the services are well-designed.

Index Terms—Agility, service orientation, measurement.

Kongsawas Potipanom is with the Department of Computer Engineering,Faculty of Engineering Chulalongkorn University, Bangkok, Thailand(e-mail: kongsawas.p@student.chula.ac.th).
Twittie Senivongse is with the Department of Computer Engineering,Faculty of Engineering, Chulalongkorn University, Bangkok, Thailand and also the corresponding author (Tel.: +66 2 2186996; fax: +66 2 2186955;e-mail: twittie.s@chula.ac.th).

Cite: Kongsawas Potipanom and Twittie Senivongse, "Measurement of Agility to Change for Service-Based Systems," International Journal of Computer and Communication Engineering vol. 1, no. 2, pp. 124-128 , 2012.