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

Abstract

Abstract-Service-OrientedEnterprise 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 Model-driven Ontology Approach for Developing Service System Applications

“…The Model -driven approach (MDA) for a system development was suggested, which is a variant of this refinementbased software development in which models are no longer loosely coupled, but connected in a systematic way: that is, model elements must be traceable from a more abstract model to a more concrete model and vice versa [17][18][19][20][21][22][23]. This is achieved through meta-modelling: meta-models define sets of valid models, facilitating their transformation, serialization, and exchange.…”

“…The solution, actively developed by leading providers of information technology (IBM, Microsoft, Oracle and others), is to move from a centralized IT infrastructure to an architecture which enables rapid creation of new systems from a set of available services. It means the transition to the so-called Serviceoriented Architecture (SOA) and its implementation in forms of process-oriented business models (Model-driven architecture, MDA) [1][2][3][4][5].…”

Analysis of Legacy System in Software Application Development: A Comparative Survey

“…Grace Lewis et al [5] used SMART tool to analyze the legacy components for determining changes to be made to enable migration of legacy system. This tool uses three sources of information to fortify the analysis activity-First Information cognate to the issues, quandaries that were noted by the team in revelation process, second information provided by a Service Migration Inventory (SMI) that extract the many desired behavior of services executing within SOAs into a set of topics and third source of information entails the utilization of code analysis and architecture reconstruction tools to analyze the subsisting source code for legacy components Smith, D et al [6] proposed a SMART technique with different behavior which assists organizations in analyzing legacy capabilities for use as services in an SOA environment. The goal of this activity is to obtain descriptive data like the name, function, size, language, operating platform, and age of the legacy components that are considered for migration.…”

Process-oriented design of software systems as a system service

“…Процесс проектирования системы сервисов может быть сведен к процессу преобразований моделей, начиная с метамодели в качестве входных данных и используя набор правил преобразования [9][10][11][12][13][14]. При этом преобразование само по себе является также моделью.…”