What is different in quality management for SOA?

7Citations
Citations of this article
20Readers
Mendeley users who have this article in their library.
Get full text

Abstract

With the service-oriented paradigm, some established ways of thinking about software quality and its assurance seem to change. But things do not necessarily become more difficult. Some considerable advancements to traditional ways of quality management can be introduced through the use of service-based systems, leading to largely reduced efforts and increased quality. In this article we identify the main challenges and opportunities for software development that evolve out of the transition to service-based systems, derived from both theory and the documented experience gained within a large-scale SOA application development scenario. Our research shows that there are significant benefits with respect to interoperability and changeability, while other quality attributes such as performance raise concerns. Within a third group of attributes, including security and testability, we see contradictory evidence. Especially regarding testing our field work reveals considerable advancements whereas literature reports concerns. Some of the challenges we identified, however, may be temporary as tools and methodologies are evolving. © 2010 IEEE.

Author supplied keywords

Cite

CITATION STYLE

APA

Voelz, D., & Goeb, A. (2010). What is different in quality management for SOA? In Proceedings - IEEE International Enterprise Distributed Object Computing Workshop, EDOC (pp. 47–56). https://doi.org/10.1109/EDOC.2010.27

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free