Abstract
Determining the size, effort and cost of Service-oriented Architecture (SOA) systems is important to facilitate project planning and eventually successful implementation of a software project. SOA approach is one of the recent software architectures that allow integration of applications within and outside the organization regardless of heterogeneous technology over a distributed network. A number of research studies have been done to measure SOA size.However, these studies are not based on software metrics rendering them to be ineffective in their estimation. This study defined a set of SOA size metrics based on Unified Modelling Language (UML). The study employed Briand’s theoretical validation to test the validity of the designed SOA size metrics. Findings from this study will provide metrics to measure SOA size more accurately and form a basis for future software engineering researchers to develop more effective and more accurate size metrics and effort estimation methods.
Highlights
The ability to measure size and estimate software effort precisely contributes to better management of IT projects and more so software systems
This paper seeks to define a suite of size metrics that will be used to measure the size attributes of Service-oriented Architecture (SOA) software based on Unified Modelling Language (UML) interface and sequence diagrams
This study considers SOA internal structure, data movement, interaction and relationship among services as key attributes for defining SOA size metrics[20][21]
Summary
The ability to measure size and estimate software effort precisely contributes to better management of IT projects and more so software systems. Service-oriented Architecture (SOA) is an example of a popular paradigm for developing distributed systems that provides a challenge to existing software size metrics. Some of the most frequently used software size metrics in use since 1980’s includes Source Line of Code (SLOC) and Function Point [6] These metrics are challenged when dealing with SOA characteristics such as loose coupling, SOA internal structure, service composition and messaging. This paper seeks to define a suite of size metrics that will be used to measure the size attributes of SOA software based on UML interface and sequence diagrams It provides an analysis of existing software size metrics and use a case example to illustrate the defined metrics.Lastly, theoretical validation of the proposed metrics isbased on Briand’s size properties framework
Sign-in/Register to view highlights & summary 
Published Version (
Free)
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 callMore From: International Journal of Software Engineering & Applications
Disclaimer: 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.
