An exploratory survey on SOA knowledge, adoption and trend in the Italian industry (original) (raw)

A GENTLE INTRODUCTION OF SERVICE-ORIENTED ARCHITECTURE IN DEVELOPMENT OF LEADING TECHNOLOGIES

Foundation of Computer Applications, 2021

Service-Oriented Architecture is a technique which can be employed to unite various services over the operating systems, platforms and networks. Several organizations fail to completely use SOA and the reason behind this is underdeveloped adoption process. The author has conducted an exploratory study to explore the recent concerns and numerous practices related with SOA adoption along with assessing various maturity levels used, role of information technology in SOA adoption. The required information is gathered by conducting a literature survey that explored the previously done work on SOA adoption by surfing through the net, reading journals and papers. The paper focuses on various significant issues related with adoption of SOA in organizations.

Hype over Service Oriented Architecture Continues

Business and Information Systems Engineering the International Journal of Wirtschaftsinformatik, 2008

 Presentation of various SOA definitions  Collection of SOA-related blogs  List of EU-funded projects related to SOA Stichworte: SOA, service oriented architecture, service oriented computing, web services

Service Oriented Architecture Empirical Study

2007

Abstract Service Oriented Architecture (SOA) has been proposed as model for distributed software development that surpasses the traditional Distributed Object Architecture (DOA) practices in many areas. However, no empirical studies have been conducted to verify the claimed benefits. This study is a first attempt at presenting empirical evidence regarding the benefits of SOA. It is a comparison between traditional DOA and SOA. The two technologies were compared on the basis of code size and development time.

A Comparison of Service Oriented Architecture with other advances in Software Architectures

2007

ion SOA extends the concept of abstraction and encapsulation. Unlike in OO which hides internal details (data and methods), SOA aims at hiding all causes of integration problems. Stal (2002) lists the causes of heterogeneity as “network technologies, devices, and OSs; middleware solutions and communication paradigms; programming languages; services and interface technologies; domains and architectures; and data and document formats.” SOA encapsulates a specific set of discrepancies in its domain of application. By hiding these differences, services within the service oriented architecture can be accessed seamlessly. The differences are typically hidden by using a common set of standards. The differences may be in terms of data structures, communication protocols or platforms. For example, SOA’s that target the Internet as the mode of delivery, will require standards that hide heterogeneity in platforms, while a simple SOA that is part of an operating system such as accessing devices...

SOA Adoption in Practice-Findings from Early SOA Implementations

2007

Despite the wide range of advantages which many authors associate with the introduction of a service-oriented architecture (SOA), comprehensive SOA implementations continue to be scarce in practice. Consequently, questions arise as to how the concept is adapted in practice. This paper compares the scientific view of SOA concepts with initial practical experience from first SOA implementations. Based on an SOA model which is derived from recent SOA publications it examines SOA realization in four case studies. From the cross-case analysis, the authors derive three focus areas of SOA adoption, a prioritization of SOA design principles as well as typical steps towards SOA implementation in practice.

32 A Comparison of Service Oriented Architecture with other Advances in Software Architectures

Service Oriented Architecture (SOA) allows software systems to possess desirable architecture attributes such as loose coupling, platform independence, inter-operability, reusability, agility and so on. Despite its wide adoption in the form of Web services, many stakeholders both from academia and industry have limited understanding of its underlying principles. This has led to faulty implementations of SOA and in some cases, it has been implemented in places where it is not suitable. In this paper, we investigate and show the relationship between SOA and other advances in software architecture. The paper relates SOA to Architecture Patterns, Components and Connectors. We advance the view that SOA's uniqueness and strength does not lie in its computational elements but in the way it enables and handles their interaction. In this way, we facilitate the understanding of SOA in terms of other advances in software architectures that are already well understood. We believe that a good understanding of SOAs in terms of other advances in software architectures will help to reap its enormous benefits.

The (Lacking) Business Perspective on SOA - Critical Themes in SOA Research

2009

Service-oriented architecture (SOA) has gained much popularity lately, in both practice and academia. Since SOA concepts and technology are maturing, companies have started to engage in projects that will fundamentally transform IS landscapes over the next decade. While the growing body of SOA research is mostly technology-oriented, there is a need to review the current state of research in light of the strategic, organizational, and managerial issues associated with SOA implementation. This paper profiles SOA and Web services research since 2000 with a focus on practices, adoption, and impact. Drawing on a sample of 175 papers in academic journals and conference proceedings, we establish transparency of the current state of SOA research. Our analysis finds that the science base for SOA research from an IS perspective is still under construction thereby reflecting the novelty of the underlying technologies. We conclude that business aspects remain underserved and derive a number of recommendations for the IS community on how to proceed with SOA research.

Service Oriented Architecture: Potential Benefits and Challenges

2007

Globalisation, tighter economies, business process outsourcing, ever increasing regulatory environments and knowledgeable consumers are forcing the large enterprises to transform the way they provide their business and services. Businesses are required to be agile and flexible and IT managers are being asked to deliver improved functionality while leveraging existing IT investment. In this climate, Service Oriented Architecture (SOA) is proving to be an attractive approach to Enterprise Application Integration and other solutions that they seek. SOA promises better alignment of IT with business, effective reuse, interoperability and reduced costs of development. However, like any approach, it has its limitations and therefore posses a number of challenges. In this paper, we introduce the SOA approach, present the benefits it offers and discuss the inherent issues and challenges. The objective is to provide enough background information that enterprises wishing to embark on the road to SOA have a better understanding of this approach.

An Exploratory Study for Investigating the Issues and Current Practices of Service-Oriented Architecture Adoption

Journal of Information and Communication Technology

Service-Oriented Architecture (SOA) is an approach that can be used to integrate different services across operating systems, platforms, languages, and networks which offer some benefits. However, many organizations fail to fully utilize SOA because the adoption processes are still immature. Therefore, an exploratory study was conducted to investigate current issues and practices of SOA adoption, the use of maturity levels for assessing SOA adoption, and the importance of information technology (IT) and business benefits in SOA adoption. Thus, the Grounded Theory approach was adapted in this study which involved seven software development companies in Malaysia. In this study, 14 SOA practitioners with at least three years of experience in SOA development were interviewed. The collected data was analyzed through three main coding stages: open, axial and selective coding. The theory which emerged from this study revealed SOA adoption issues, current practices, maturity levels,