• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.8 no.6
• /
• pp.2118-2138
• /
• 2014

Risks are involved in all phases of the software life cycle, and due to these risks, software can face various problems that can cause different negative outcomes and sometimes, in extreme cases, the failure of the software. Most of these risks lie in the legacy software migration process. These risks can create many problems, and in the worst case they can lead to the failure of the migration project. This paper explores different types of risk analysis methods such as CRAMM, CORAS, OCTAVE and VECTOR. After comparing these methods, the two suitable methods were chosen, namely, OCTAVE and VECTOR. Based on the use of these two methods, the project suggests an enhanced EOV method for risk analysis in the migration of legacy software.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.8 no.6
• /
• pp.1428-1442
• /
• 2007

Nowadays, as IT environment is changing rapidly, traditional infra system such as hardware, software, and development methodology are changing as well. Legacy system has been filled with Intellectual property such as invested budget and development period for the time of IT is developing. Many countries around the world are having troubles with how to manage the legacy system. It is time to study on a development method and the implementation of supporting tool to reuse or process the legacy system. In this paper, it proves the definition, concept and also background of legacy system by showing real market and technology trend. Developed to handle the concrete development methodology, procedure and reference. We can get more profitability and productivity advance by reuse of legacy system and maintenance cost-saving through legacy migration.

• The KIPS Transactions:PartD
• /
• v.14D no.7
• /
• pp.763-772
• /
• 2007

Due to increased software development cost, interest about the method and automated tool for reusing legacy system have been running high. Therefore, In this study, it proves the definition, concept and also background of legacy system by showing real market and technology trend. Automation tool is designed and developed to handle the concrete development methodology, procedure and reference. Also, we implemented the process that analyze the legacy system and extract, refine, store and reuse the candidate components by using LM(Legacy to Modern System) supporting tool presented in this paper. If LM supporting tool is applied to legacy system migration, we can expect cutting costs, shortening the developing period and succeeding the intellectual property by software re-engineering.

• The KIPS Transactions:PartD
• /
• v.16D no.4
• /
• pp.583-594
• /
• 2009

Most of the SOA solutions applicable to businesses and organizations are taking a top-down methodology. It starts with an analysis of an organization's requirements, followed by definition of business models and identification of candidate services and ends with finding or developing required services. Challenges in adopting SOA while abandoning legacy systems involve time and cost required during the process. Many businesses and organizations want to gradually migrate into SOA while making the most of the existing system. In this paper, we propose A Method for Migration of Legacy System into Web Service(M-LSWS); it allows legacy system to be migrated into web service accessible by SOA and be used as data repositories. M-LSWS defines procedures for migration into reusable web services through analysis of business processes and identification of candidate services based on design specification and code of legacy system. M-LSWS aims to migrate of legacy system into web service appropriate for SOA. The proposed method consists of four steps: analysis of legacy system, elicitation of reusable service and its specification, service wrapping and service registration. Each step has its own process and guideline. The eligibility of the proposed method will be tested by applying the method to book management system.

• Journal of Korea Multimedia Society
• /
• v.8 no.3
• /
• pp.398-412
• /
• 2005

There is an increasing interest in migration legacy systems to new hardware platforms and to new software development paradigms. The reason is that high maintenance costs and lack of documentation. In order to migrate or transform legacy system, various approaches such as screen scrapping, wrapping, semi-development, and re-development, tools, and methodologies are introduced until now. However, architecture or requirements level's transformation is not suggested because most of those approaches focus on code-level transformation or a few model-level transform. In this paper, we suggest a meta-model driven approach applying 3D space concept, which can be applied into architecture and requirement phase. Proposed integrated model drives seamless migration or co-evolution from code to architecture of reverse engineering and from architecture to code of forward engineering.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.18 no.8
• /
• pp.2450-2463
• /
• 2024

Many legacy information systems are currently being clouded. This is due to the advantage of being able to respond flexibly to the changes in user needs and system environment while reducing the initial investment cost of IT infrastructure such as servers and storage. The infrastructure of the information system migrated to the cloud is being integrated through the API connections, while being subdivided by using MSA (Micro Service Architecture) internally. DBMS (Database Management System) is also becoming larger after cloud migration. Scale calculation in most layers of the application architecture can be measured and calculated from auto-scaling perspective, but the method of hardware scale calculation for DBMS has not been established as standardized methodology. If there is an error in hardware scale calculation of DBMS, problems such as poor performance of the information system or excessive auto-scaling may occur. In addition, evaluating hardware size is more crucial because it also affects the financial cost of the migration. CPU is the factor that has the greatest influence on hardware scale calculation of DBMS. Therefore, this paper aims to calculate the conversion factor for CPU scale calculation that will facilitate the cloud migration between heterogeneous DBMS. In order to do that, we utilize the concept and definition of hardware capacity planning and scale calculation in the on-premise information system. The methods to calculate the conversion factor using TPC-H tests are proposed and verified. In the future, further research and testing should be conducted on the size of the segmented CPU and more heterogeneous DBMS to demonstrate the effectiveness of the proposed test model.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2014.11a
• /
• pp.703-706
• /
• 2014

AUOTSAR(Automotive Open system Architecture)는 자동차 ECU(Electronic Control Unit) 에 내장되는 소프트웨어에 대한 표준 구조로서, ECU 소프트웨어의 품질 향상은 물론, 개발 및 관리 비용의 절감에 기여하는 등 많은 장점을 갖는다. AUTOSAR 의 이런 장점 때문에 많은 자동차 회사들이 ECU 소프트웨어에 AUTOSAR 적용을 추진하고 있다. 이에 따라 기존 레거시 ECU 소프트웨어 시스템을 AUTOSAR 표준에 맞는 ECU 소프트웨어 시스템으로 변환하는 방법에 대한 관심도 높아지고 있다. 그 이유는 이미 많은 ECU 레거시 소프트웨어 시스템들이 개발되어 사용되고 있으며, 이들에게는 이미 기능 및 안정성 검증을 위하여 많은 시간과 비용이 투자하여 되어 있다. 따라서 ECU 소프트웨어 시스템에 AUTOSAR 를 적용하는 경우 기존의 레거시 소프트웨어 시스템을 재사용할 수 있으면 생산성 및 품질 면에서 많은 장점을 갖는다. 본 연구에서는 C 언어로 작성된 기존의 ECU 소프트웨어 시스템을 AUTOSAR 플랫폼에서 재사용할 수 있도록 하기 위하여, 기존의 레거시 ECU 소프트웨어 시스템을 AUTOSAR 플랫폼으로 마이그레이션하는 방법에 대하여 연구하였다. 마이그레이션 과정은 크게 두 단계로 나누어 지는데, 이는 레거시 소프트웨어 시스템을 분석하여 마이그레이션이 가능하도록 기능별로 분해하는 것과, 분해된 구성 요소들을 AUTOSAR 플랫폼에 맞는 구조로 재구성하는 과정이다. 본 논문에서는 이중 첫 번째 과정인 레거시 소프트웨어 시스템의 분석 및 기능별 분해 방법을 제시하고자 한다.

• The KIPS Transactions:PartD
• /
• v.17D no.1
• /
• pp.25-40
• /
• 2010

Service-Oriented Architecture (SOA) is a development paradigm for reusing services as an independent reuse unit. A service delivers a cohesive functionality through its external interface. Since services have unique characteristics which are not typically presented in conventional development approaches, there is a demand for effective approaches to developing services. Most of the current SOA methodologies presenta process where services are designed and developed from the requirements rather than reusing existing assets, which demands high cost and effort. Hence, a desirable approach is to be able to develop services by migrating from their existing legacy systems such as object-oriented system. A difficulty in this migration is that objects in object-oriented systems reveal characteristics which differ considerably from those of services. That is, objects are designed without considering commonalities among several consumers. In this paper, we first define mapping relationships between key artifacts in object-oriented system and those in SOA services. By these relationships and considering commonalities among several applications in a domain, we propose three systematic methods to migrate from object-oriented system to SOA services. Each method consists of a list of input and output artifacts and detailed guidelines which are performed in order. Through these methods, service developers can easily develop services with less effort.