Reference Hub

This research has been cited in:

Conference
Keeping Web Service interface complexity low using an OO metric-based early approach2016 XLII Latin American Computing Conference (CLEI)10.1109/CLEI.2016.7833366
Conference
Measuring Change Impact Based on Usage Profiles2012 IEEE 19th International Conference on Web Services10.1109/ICWS.2012.35
Article
A Subsumption Hierarchy of Test Case Prioritization for Composite ServicesIEEE Transactions on Services Computing10.1109/TSC.2014.2331683
Article
Cloud managementJournal of Internet Services and Applications10.1007/s13174-011-0053-8
Article
Automatic run-time versioning for BPEL processesService Oriented Computing and Applications10.1007/s11761-017-0211-3
Conference
A Lightweight Solution to Version Incompatibility in Service-Oriented Revision Control SystemsProceedings of the ASWEC 2015 24th Australasian Software Engineering Conference10.1145/2811681.2811693
Conference
Compatibility in Service-Oriented Revision Control Systems2014 IEEE 11th Intl Conf on Ubiquitous Intelligence and Computing and 2014 IEEE 11th Intl Conf on Autonomic and Trusted Computing and 2014 IEEE 14th Intl Conf on Scalable Computing and Communications and Its Associated Workshops10.1109/UIC-ATC-ScalCom.2014.24
Conference
T-DSCM: A Three-Dimensional Framework for Service Change Management in SOA Environments2018 9th International Symposium on Telecommunications (IST)10.1109/ISTEL.2018.8661154
Article
Preemptive Regression Testingof Workflow-Based Web ServicesIEEE Transactions on Services Computing10.1109/TSC.2014.2322621
Conference
Detecting Incompatibilities Concealed in Duplicated Software Libraries2015 41st Euromicro Conference on Software Engineering and Advanced Applications10.1109/SEAA.2015.17
Article
A Stitch in Time Saves Nine: Early Improving Code-First Web Services DiscoverabilityInternational Journal of Cooperative Information Systems10.1142/S0218843015500045
Article
Usage ProfilesInternational Journal of Web Services Research10.4018/jwsr.2013010101
Article
Test Pair Selection for Test Case Prioritization in Regression Testing for WS-BPEL ProgramsInternational Journal of Web Services Research10.4018/jwsr.2013010104
Chapter
Research Challenges in the Maintenance and Evolution of Service-Oriented SystemsMigrating Legacy Applications10.4018/978-1-4666-2488-7.ch002

Automatic Determination of Compatibility in Evolving Services

Karin Becker, Jim Pruyne, Sharad Singhal, Andre Lopes, Dejan Milojicic

Source Title: International Journal of Web Services Research (IJWSR)8(1)

ISSN: 1545-7362|EISSN: 1546-5004|EISBN13: 9781613509715|DOI: 10.4018/jwsr.2011010102

Cite Article Cite Article

MLA

Becker, Karin, et al. "Automatic Determination of Compatibility in Evolving Services." IJWSR vol.8, no.1 2011: pp.21-40. http://doi.org/10.4018/jwsr.2011010102

APA

Becker, K., Pruyne, J., Singhal, S., Lopes, A., & Milojicic, D. (2011). Automatic Determination of Compatibility in Evolving Services. International Journal of Web Services Research (IJWSR), 8(1), 21-40. http://doi.org/10.4018/jwsr.2011010102

Chicago

Becker, Karin, et al. "Automatic Determination of Compatibility in Evolving Services," International Journal of Web Services Research (IJWSR) 8, no.1: 21-40. http://doi.org/10.4018/jwsr.2011010102

Export Reference

Favorite Full-Issue Download

View Full Text HTML

View Full Text PDF

Abstract

A major advantage of Service-Oriented Architectures (SOA) is composition and coordination of loosely coupled services. Because the development lifecycles of services and clients are de-coupled, multiple service versions must be maintained to support older clients. Typically versions are managed within the SOA by updating service descriptions using conventions on version numbers and namespaces. In all cases, the compatibility among services descriptions must be evaluated, which can be hard, error-prone and costly if performed manually, particularly for complex descriptions. In this paper, the authors describe a method to automatically determine when two service descriptions are backward compatible. The authors describe a case study to illustrate version compatibility information in a SOA environment and present initial performance overheads. By automatically exploring compatibility information, a) service developers can assess the impact of proposed changes; b) proper versioning requirements can be put in client implementations guaranteeing that incompatibilities will not occur during run-time; and c) messages exchanged in the SOA can be validated to ensure that only expected messages or compatible ones are exchanged.

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.

Username or email: *

Password: *

Forgot individual login password?

Create individual account

Automatic Determination of Compatibility in Evolving Services

MLA

APA

Chicago

Export Reference

Abstract

Request Access