Abstract
Service-Oriented Architecture (SOA) is becoming the dominant approach for developing and organizing distributed enterprise-wide applications. Although the concepts of SOA have been extensively described in the literature and in-dustry, the effects of adopting SOA on software quality are still unclear. The aim of the paper is to analyze how adopt-ing SOA can affect software quality as opposed to the Object-Oriented (OO) paradigm and expose the differential implications of adopting both paradigms on software quality. The paper provides a brief introduction of the architectural differences between the Service-Oriented (SO) and OO paradigms and a description of internal software quality metrics used for the comparison. The effects and differences are exposed by providing a case study architected for both paradigms. The quantitative measure concluded in the paper showed that a software system developed using SOA approach provides higher reusability and lower coupling among software modules, but at the same time higher complexity than those of the OO approach. It was also found that some of the existing OO software quality metrics are inapplicable to SOA software systems. As a consequence, new metrics need to be developed specifically to SOA software systems.
Highlights
The large explosion of business demands and enterprisewide applications has created the need for different approaches to software development in order to facilitate business collaboration and growth
The paper provides a brief introduction of the architectural differences between the Service-Oriented (SO) and OO paradigms and a description of internal software quality metrics used for the comparison
The first section of this paper introduces the Service-Oriented Architecture (SOA) and the differences compared to the Object-Oriented Architecture (OOA)
Summary
The large explosion of business demands and enterprisewide applications has created the need for different approaches to software development in order to facilitate business collaboration and growth. This has led to the adoption of Service-Oriented Architecture (SOA) for building highly distributed and integrated enterprise-wide software systems that use web services as its building blocks. The purpose of the study is to provide an empirical comparison and evaluation of how encapsulating business logic and rules into web services can affect internal software quality attributes. Such attributes involve size, complexity, coupling, and cohesion. The study addresses the following three basic research questions: 1) Does a software system developed using the SOA approach requires new software quality metrics?
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
