The Impact of Software Development Strategies on Project and Structural Software Attributes in SOA

Abstract

Abstract. Service-Oriented Architecture (SOA) is a promising approach for developing integrated enterprise applications. Although the architectural aspects of SOA have been investigated in research and industry literature, the actual process of designing and implementing services in SOA is not well understood. The goal of this paper is to identify tasks needed for successful design and implementation of services, and investigate their effect on the project and structural software attributes in the context of SOA. This facilitates the specification of guidelines for decreasing the required development effort and capital cost of the SOA projects, and improving the structural software attributes of service implementations. The tasks are identified in the context of top-down, bottom-up and meet-in-the-middle software development strategies.

A Metrics Framework for Evaluating SOA Service Granularity

“…Service granularity influences a number of different internal and external structural software attributes [12]. In this paper, we analyse the internal structural software attributes of complexity, cohesion, and coupling that are influenced by service granularity.…”

Assessing Internal Software Quality Attributes of the Object-Oriented and Service-Oriented Software Development Paradigms: A Comparative Study

“…Another study by Perepletchikov [15] investigated the impact of several development strategies; top-down, bottom-up and meet-in-the middle of SOA on the project (Capital Cost and Development Effort) and structural software attributes involving Complexity, Coupling, and Cohesion. The authors provide guidelines for each development strategy when building SOA software systems.…”

ASSESSING THE QUALITY OF ENTERPRISE SERVICES - A Model for Supporting Service Oriented Architecture Design

“…In essence there are three main strategies for developing SOA-based enterprise applications: topdown, bottom-up, and meet-in-the-middle (Perepletchikov, 2005;Arsanjani, 2004). It is a key decision whether service creation should begin from the bottom-up or top-down.…”