A Model-Driven Architecture Approach to the Efficient Identification of Services on Service-oriented Enterprise Architecture

Service-Oriented Enterprise Architecture requires the efficient development of loosely-coupled and interoperable sets of services. Existing design approaches do not always take full advantage of the value and importance of the engineering invested in existing legacy systems. This paper proposes an approach to define the key services from such legacy systems effectively. The approach focuses on identifying these services based on a Model-Driven Architecture approach supported by guidelines over a wide range of possible service types

A matching approach to business services and software services

Recent studies have shown that service-oriented architecture (SOA) has the potential to revive enterprise legacy systems (Cai et al., 2011; Gaševic and Hatala, 2010; De Castro et al., 2011; Chengjun, 2008; Elgedawy, 2009; Tian et al., 2007; Chen et al., 2009; Zhang et al., 2006; Sindhgatta and Ponnalagu, 2008; Khadka, 2011), making their continued service in the corporate world viable. In the process of reengineering legacy systems to service-oriented architecture, some software services extracted in legacy system can be reused to implement business services in target systems. In order to achieve efficient reuse to software services, a matching approach is proposed to extract the software services related to specified business services, where service semantics and structure similarity measures are integrated to evaluate the similarity degree between business service and software services. Experiments indicate that the approach can efficiently map business services to relevant software services, and then legacy systems can be reused as much as possible

Factors Affecting Success in Migration of Legacy Systems to Service-Oriented Architecture (SOA) - Shared Experiences from Five Case Companies

Background: The term ‘legacy systems’ refers to existing Information Systems that have been deployed in the past and have been running critical business processes within an enterprise in its current IT architecture. Based on their important role, legacy systems are considered the heart of a company’s operating enterprise system and therefore are of significant business value to the company. Therefore IT architects have not neglected the value these existing assets can bring to the adoption of service-oriented architecture and have been studying different methods and factors to migrate the legacy investments into the new architecture and take advantage of their business value. However, not in all cases has the process of migrating legacy systems into SOA been successful. In fact, the level of success in adapting the legacy systems in a company with the new service-oriented architecture is dependant on some factors which vary from one legacy infrastructure and series of business processes to another. There is no quick fix to transforming the existing legacy assets which highlights the fact that considering the right factors to reach legacy system migration success in a specific company is of key value. Therefore, we hereby studied the factors influencing success of migrating these legacy investments into SOA in five different companies which include a Large European Bank, SAS, a Large globally-known Company in Sweden, Sandvik AB and a large UK Bank. Purpose: To identify factors affecting successful migration of legacy systems into SOA in five companies. Method: The main adopted research method in this study has been interviews for different case studies. Through separate interviews, critical success factors of migrating legacy systems into SOA have been collected and identified in each case. Finally collected results are analyzed and presented as the recognized factors affecting successful migration of legacy assets into SOA in five different enterprises with their own Information System infrastructures. Conclusion: The success factors identified include potential of legacy systems for being migrated, strategy of migration, SOA governance, the business process of the company, budgeting and resources, legacy architecture, close monitoring, dependence on commercial products, information architecture, testing and technical skills of the personnel. Out of all these factors, only three factors have been applied and mentioned by all the case companies in this study, which are the potential of legacy systems for being migrated into SOA, strategy of migration and SOA Governance

Modelling electronic service systems using UML

This paper presents a profile for modelling systems of electronic services using UML. Electronic services encapsulate business services, an organisational unit focused on delivering benefit to a consumer, to enhance communication, coordination and information management. Our profile is based on a formal, workflow-oriented description of electronic services that is abstracted from particular implementation technologies. Resulting models provide the basis for a formal analysis to verify behavioural properties of services. The models can also relate services to management components, including workflow managers and Electronic Service Management Systems (ESMSs), a novel concept drawn from experience of HP Service Composer and DySCo (Dynamic Service Composer), providing the starting point for integration and implementation tasks. Their UML basis and platform-independent nature is consistent with a Model-Driven Architecture (MDA) development strategy, appropriate to the challenge of developing electronic service systems using heterogeneous technology, and incorporating legacy systems

Service Oriented Architecture: impacts and challenges of an architecture paradigm change

International audienceAutomotive embedded software has relied on signal-based architecture for a long time. This architecture has proven through the last decades its reliability and ability to address complex systems such as a car embedding several tens of processors.Automotive industry foresees a large introduction of Service Oriented Architecture in the car whereas the technology was initially used by information systems and web applications. A complete change of architecture is clearly a challenge considering the number of heterogeneous actors, the heavy legacy of business and the safety constraints.This paper aims at providing feedbacks on the introduction of SOA in automotive industry through the prism of Software architecture and development team

Poster: Reengineering legacy systems for supporting SOA: A case study on the brazilian's secretary of state for taxation

© 2018 Authors. The migration of legacy systems to a service-oriented architecture (SOA) allows to deal with the demand for interoperability and the need to provide a robust high-Available service interface. However, such migration presents a considerable risk, as it often involves the use of different techniques on systems with elevated technical debt and high maintenance costs. For this purpose, a process is instantiated to provide an appropriate set of techniques that will minimize risks and at the same time ensure quality improvement of the systems throughout the migration process. In this sense, this work reports on a case study of the application of a process for the reengineering of legacy systems to support the implementation of SOA project. This study has been applied to the evolution of legacy systems of the Secretariat of State for Taxation of Rio Grande do Norte (SET/RN), Brazil, providing significant results regarding the achievement of important quality goals

Enabling Mainframe Assets to Services for SOA

Service-oriented architecture (SOA) is a mechanism for achieving interoperability between heterogeneous systems. SOA enables existing legacy systems to expose their functionality as services, without making significant changes to the legacy systems. Migration towards a service-oriented approach (SOA) not only standardizes interaction, but also allows for more flexibility in the existing process. Web services technology is an ideal technology choice for implementing a SOA. Web services can be implemented in any programming language. The functionality of Web services range from simple request-reply to full business process. These services can be newly developed applications or just wrapper program for existing business functions to be network-enabled. The strategy is to form a framework to integrate z/OS assets in distributed environment using SOA approach, to enable optimal business agility and flexibility. Mainframe applications run the business and contain critical business logic that is unique, difficult, and costly to replicate. Enabling existing applications allows reusing critical business assets and leveraging the assets as a service to be invoked in heterogeneous environment

A Web Service Approach to Geographical data distribution among public administrations

Abstract: In this paper a service-oriented architecture (SOA) is proposed to support the interaction with legacy Geographical Information Systems (GIS) and the implementation of value added data sharing services. In particular, we base our proposed architecture both on the standardization effort carried out by the Open Geospatial Consortium (OGC) and on current state-of-the-art Web Service middleware infrastructure. We have evaluated the proposed architecture in the context of GIS application integration in a departmental back-office scenario. The advantages of a service-oriented architecture are twofold: on one hand, it is possible to integrate several GIS application and data sources simply by wrapping their (legacy) services with appropriate interface and registering them in Web Service directories; on the other hand, this new service paradigm can be used to support the creation of completely new cartographic data sharing services