Business Innovation and Service Oriented Architecture

Author(s):  
Bendik Bygstad ◽  
Tor-Morten Grønli ◽  
Helge Bergh ◽  
Gheorghita Ghinea

Recent research suggests that a strong link exists between business innovation and service oriented IT architectures: modern IT architecture enables business to quickly create new services. However, the relationship between IT capabilities and business performance is not always straightforward. How does SOA support fast innovation in practice, and under which conditions is it effective? In this paper, the authors investigate these issues and ask: How can a SOA architecture like the Enterprise Service Bus support business innovation? This paper investigates this question through a case study at an airline company. Analyzing the relationship between innovation and IT architecture in the company over time, the authors offer the following conclusion: ESB gives strong support to business innovation, under two conditions. First, the implementation of ESB has to be comprehensive, that is, it should include the core processes of the business. Second, the top management (and partners) need to understand the principles of ESB.

Author(s):  
Bendik Bygstad ◽  
Tor-Morten Grønli ◽  
Helge Bergh ◽  
Gheorghita Ghinea

Recent research suggests that a strong link exists between business innovation and service oriented IT architectures: modern IT architecture enables business to quickly create new services. However, the relationship between IT capabilities and business performance is not always straightforward. How does SOA support fast innovation in practice, and under which conditions is it effective? In this paper, the authors investigate these issues and ask: How can a SOA architecture like the Enterprise Service Bus support business innovation? This paper investigates this question through a case study at an airline company. Analyzing the relationship between innovation and IT architecture in the company over time, the authors offer the following conclusion: ESB gives strong support to business innovation, under two conditions. First, the implementation of ESB has to be comprehensive, that is, it should include the core processes of the business. Second, the top management (and partners) need to understand the principles of ESB.


Author(s):  
Vinay Raj ◽  
Ravichandra Sadam

Service oriented architecture (SOA) has been widely used in the design of enterprise applications over the last two decades. Though SOA has become popular in the integration of multiple applications using the enterprise service bus, there are few challenges related to delivery, deployment, governance, and interoperability of services. To overcome the design and maintenance challenges in SOA, a new architecture of microservices has emerged with loose coupling, independent deployment, and scalability as its key features. With the advent of microservices, software architects have started to migrate legacy systems to microservice architecture. However, many challenges arise during the migration of SOA to microservices, including the decomposition of SOA to microservice, the testing of microservices designed using different programming languages, and the monitoring the microservices. In this paper, we aim to provide patterns for the most recurring problems highlighted in the literature i.e, the decomposition of SOA services, the size of each microservice, and the detection of anomalies in microservices. The suggested patterns are combined with our experience in the migration of SOA-based applications to the microservices architecture, and we have also used these patterns in the migration of other SOA applications. We evaluated these patterns with the help of a standard web-based application.


Author(s):  
Masahide Nakamur ◽  
Hiroshi Igaki ◽  
Takahiro Kimura ◽  
Kenichi Matsumoto

In order to support legacy migration to the service-oriented architecture (SOA), this paper presents a pragmatic method that derives candidates of services from procedural programs. In the SOA, every service is supposed to be a process (procedure) with (1) open interface, (2) self-containedness, and (3) coarse granularity for business. Such services are identified from the source code and its data flow diagram (DFD), by analyzing data and control dependencies among processes. Specifically, first the DFD must be obtained with reverse-engineering techniques. For each layer of the DFD, every data flow is classified into three categories. Using the data category and control among procedures, four types of dependency are categorized. Finally, six rules are applied that aggregate mutually dependent processes and extract them as a service. A case study with a liquor shop inventory control system extracts service candidates with various granularities.


Author(s):  
Samuel Otero Schmidt ◽  
Edmir Parada Vasques Prado

Organizations are currently investing more in information technology to store and process a vast amount of information. Generally, this information does not comply with any standard, which hinders the decision-making process. The cause of the difficulties can be attributed to Information Quality (IQ), which has technical characteristics related to the architecture used in Data Warehouse (DW) and Business Intelligence (BI) environments. On the basis of the relevant literature in IQ, DW, and BI, a research model was created to identify the relations between components of DW/BI architecture and IQ dimensions. This research model was applied in a real case study (Big Financial Company in Brazil). This case study involved semi-structured interviews with managers and analysts. This chapter attempts to provide a better understanding of the relations between IT architecture and IQ in DW and BI environments. The authors hope to motivate the discussion around the development of IQ-oriented architectures for BI and the relationship between these concepts.


Author(s):  
Tony Clark ◽  
Balbir S. Barn ◽  
Vinay Kulkarni

Component-based approaches generalize basic object-oriented implementations by allowing large collections of objects to be grouped together and externalized in terms of public interfaces. A typical component-based system will include a large number of interacting components. Service-Oriented Architecture (SOA) organizes a system in terms of components that communicate via services. Components publish services that they implement as business processes. Consequently, a change to a single component can have a ripple effect on the service-driven system. Component reconfiguration is motivated by the need to evolve the component architecture and can take a number of forms. The authors define a dynamic architecture as one that supports changing the behavior and topology of existing components without stopping, updating, and redeploying the system. This chapter addresses the problem of dynamic reconfiguration of component-based architectures. It proposes a reification approach that represents key features of a language in data, so that a system can reason and dynamically modify aspects of it. The approach is described in terms of a new language called µLEAP and validated by implementing a simple case study.


Author(s):  
Dinesh Sharma ◽  
Devendra Kumar Mishra

Present is the era of fast processing industries or organization gives more emphasis for planning of business processes. This planning may differ from industry to industry. Service oriented architecture provides extensible and simple architecture for industry problem solutions. Web services are a standardized way for developing interoperable applications. Web services use open standards and protocols like http, xml and soap. This chapter provides a role of enterprise service bus in building web services.


Author(s):  
Hany F. EL Yamany ◽  
David S. Allison ◽  
Miriam A.M. Capretz

Security is one of the largest challenges facing the development of a Service-Oriented Architecture (SOA). This is due to the fact that SOA security is the responsibility of both the service consumer and service provider. In recent years, many solutions have been implemented, such as the Web Services Security Standards, including WS-Security and WS-SecurityPolicy. However, those standards are insufficient for the promising new generations of Web 2.0 applications. In this research, we describe an Intelligent SOA Security (ISOAS) framework and introduce four of its services: Authentication and Security Service (NSS), the Authorization Service (AS), the Privacy Service (PS) and the Service of Quality of Security Service (SQoSS). Furthermore, a case study is presented to examine the behavior of the described security services inside a market SOA environment.


Sign in / Sign up

Export Citation Format

Share Document