Concepedia

TLDR

Service‑oriented architecture promises agility, interoperability, deployment flexibility, and reusability, yet its adoption requires significant investment and lacks a clear strategy for assessing business value amid industry‑wide diffusion complexities. This study uses a system‑dynamics approach to illuminate how organizations create value from SOA adoption. A calibrated and validated model of industry diffusion and organizational adoption is simulated under diverse conditions to evaluate SOA’s efficacy. Simulations reveal that SOA delivers clear benefits over monolithic ITs when conditions are appropriate, identify scenarios where it falls short, and provide a practical decision‑support tool for organizations.

Abstract

Service-oriented architecture (SOA) has been promoted as a technology that can enhance information systems agility, interoperability between applications, deployment flexibility, and reusability. As with any new information technology (IT), the decision to adopt SOA cannot be taken lightly, given the nontrivial investment in economic and personnel resources. The complexity associated with industry-wide diffusion, coupled with organization, industry, and environment factors, contributes to a lack of a clear strategy for assessing the business value that SOA provides an organization. This research attempts to shed light on this process of value creation for an organization, using a system dynamics approach. A detailed model of the industry diffusion coupled with organization adoption is presented. After suitable calibration and validation, a series of simulations using the model evaluate the efficacy of SOA under a variety of diverse conditions. The results of the simulations indicate clear benefits of SOA over monolithic ITs when employed under appropriate conditions. Situations where SOA fails to live up to expectations are also identified. The model and accompanying simulations can serve as a practical decision support tool for an organization to help make the strategic decisions of adopting and implementing SOA.

References

YearCitations

Page 1