scholarly journals REENGINEERING TECHNIQUE ADAPTATION OF LEGACY SOFTWARE SYSTEMS

2022 ◽  
pp. 88-99
Author(s):  
Алексей Геннадьевич Массель ◽  
Тимур Габилович Мамедов
Keyword(s):  
Software Development ◽  
Business Processes ◽  
Current Problem ◽  
Software Systems ◽  
Legacy Systems ◽  
Historical Overview ◽  
Software Complex ◽  
Legacy Software ◽  
Energy Complex ◽  
Predictive Research

В статье рассматривается адаптация методики реинжиниринга унаследованных систем. Приводится обзор подходов к реинжинирингу. Несмотря на то, что термин «реинжиниринг» в первую очередь относится к изменению бизнес процессов, он удачно подходит и к модернизации программного обеспечения. Обосновывается необходимость адаптации методики. В статье описывается применение адаптированной методики на примере реинжиниринга программного комплекса для прогнозных исследований ТЭК. Приведен исторический обзор версий ПК «ИНТЭК» и описаны поэтапно все шаги проведения его реинжиниринга на основе агентно-сервисного подхода The article presents an adaptation of the legacy systems reengineering technique. An overview of approaches to reengineering is given. Although the term “reengineering” primarily refers to changing business processes, it is well suited to software development. The necessity of adapting the method has been substantiated. The article describes the application of the described methodology on the example of software complex reengineering for predictive research of the fuel and energy complex. A historical overview of the current problem is given and all stages of INTEC PC reengineering are described step by step

Evolving Legacy System Towards E-Business

2011 ◽  
pp. 295-325 ◽  
Author(s):  
Lerina Aversano ◽  
Raffaele Esposito ◽  
Teresa Mallardo ◽  
Maria Tortorella
Keyword(s):  
Information Systems ◽  
Business Process ◽  
Business Processes ◽  
Software Systems ◽  
Legacy System ◽  
Legacy Software ◽  
Measurement Framework ◽  
Technical Issues ◽  
Legacy Applications ◽  
Decision Tables

In e-business, addressing the technical issues alone is not enough to drive the evolution of existing legacy applications, but it is necessary to consider problems concerning the strict relationship that exists between the evolution of the legacy system and the evolution of the e-business process. To fulfill this purpose, this chapter proposes a strategy for extracting the requirements for a legacy system evolution from the requirements of the e-business process evolution. The strategy includes a toolkit composed of a set of decision tables and a measurement framework, both referring to the organization, business processes, and legacy software systems. The decision tables allow the identification of the processes to be evolved, the actions to be performed on them and their activities, and the strategies to be adopted for evolving the information systems. The measurement framework aims at achieving a greater understanding of the processes and related problems, taking into account organizational and technological issues.

An Effortless Approach for Migrating from Legacy Software Systems to Web Services

2012 ◽  
pp. 219-225
Author(s):  
K. Velmurugan ◽  
M.A. Maluk Mohamed
Keyword(s):  
Web Services ◽  
Reverse Engineering ◽  
Software Metrics ◽  
Software Systems ◽  
Legacy Systems ◽  
Legacy Software ◽  
Internet Infrastructure ◽  
Business Applications ◽  
Simple Implementation ◽  
Business To Business

One of the vital reasons for reverse engineering legacy software systems is to make it inter-operable. Moreover, technological advancements and changes in usability also motivate reverse engineering to exploit new features and incorporate them in legacy software systems. In this context, Web services are emerging and evolving as solutions for software systems for business applications in terms of facilitating interactions between business to business and business to customers. Web services are gaining significance due to inherent features like interoperability, simple implementation, and exploiting the boom in Internet infrastructure. Thus, this work proposes a framework based strategy using .net for effortless migration from legacy software systems to Web services. Further, this work also proposes that software metrics observed during the process of reverse engineering facilitate design of Web services from legacy systems.

scholarly journals Software Archeology: A Case Study in Software Quality Assurance and Design

2009 ◽  
Author(s):  
Cameron J. Turner ◽  
John M. MacDonald ◽  
Jane A. Lloyd
Keyword(s):  
Quality Assurance ◽  
Software Quality ◽  
National Laboratory ◽  
Quality Assurance Program ◽  
Software Quality Assurance ◽  
Software Systems ◽  
Legacy Systems ◽  
Los Alamos National Laboratory ◽  
Legacy Software

Ideally, quality is designed into software, just as quality is designed into hardware. However, when dealing with legacy systems, demonstrating that the software meets required quality standards may be difficult to achieve. Evolving customer needs, expressed by new operational requirements, resulted in the need to develop a legacy software quality assurance program at Los Alamos National Laboratory (LANL). This need led to the development of a reverse engineering approach referred to as software archaeology. This paper documents the software archaeology approaches used at LANL to demonstrate the software quality in legacy software systems. A case study for the Robotic Integrated Packaging System (RIPS) software is included to describe our approach.

On the Rim Between Business Processes and Software Systems

2019 ◽  
pp. 170-196 ◽  
Author(s):  
Maria Estrela Ferreira da Cruz ◽  
Ricardo J. Machado ◽  
Maribel Yasmina Santos
Keyword(s):  
Software Development ◽  
Business Process ◽  
Process Model ◽  
Process Management ◽  
Business Processes ◽  
Process Models ◽  
Software Systems ◽  
Business Process Model ◽  
Constant Change ◽  
Development Processes

The constant change and rising complexity of organizations, mainly due to the transforming nature of their business processes, has driven the increase of interest in business process management by organizations. It is recognized that knowing business processes can help to ensure that the software under development will meet the business needs. Some of software development processes (like unified process) already refer to business process modeling as a first effort in the software development process. A business process model usually is created under the supervision, clarification, approval, and validation of the business stakeholders. Thus, a business process model is a proper representation of the reality (as is or to be), having lots of useful information that can be used in the development of the software system that will support the business. The chapter uses the information existing in business process models to derive software models specially focused in generating a data model.

Legacy Software Integration in Service-Driven Environments

2014 ◽  
pp. 414-438 ◽  
Author(s):  
Chung-Yeung Pang
Keyword(s):  
Context Awareness ◽  
Business Processes ◽  
Rapid Development ◽  
Intelligent Agent ◽  
Agile Development ◽  
Legacy Systems ◽  
Legacy Software ◽  
Programming Effort ◽  
Architectural Framework ◽  
Implementation Methodology

Maintaining and upgrading legacy systems is one of the challenges many enterprises face today. Despite their obsolescence, legacy systems continue to provide a competitive advantage by supporting unique business processes and acting as a repository for invaluable knowledge and historical data. However, enterprises would prefer to develop their applications with modern software technology instead of continuing to develop in the mainframe but leverage existing business processes and data from their legacy systems. This chapter presents an architectural framework and implementation methodology of a Central Intelligent Agent that is responsible for legacy integration. The framework uses an Enterprise Service Bus for service integration and agents to handle services. The Central Intelligent Agent uses a Prolog-style rule-based engine and context awareness for service handling and a complementary service agent on the mainframe side for legacy integration. The underlying framework provides a full set of functions to integrate legacy COBOL applications as services into the system without any programming effort in COBOL. The proposed technique enables fast prototyping and rapid development in an agile development process. It also facilitates legacy migration through successive and iterative processes.

REDESIGNING LEGACY SYSTEMS INTO THE OBJECT-ORIENTED PARADIGM

2004 ◽  
Vol 14 (03) ◽  
pp. 255-276
Author(s):  
W. ERIC WONG ◽  
JENNY LI
Keyword(s):  
Inventory Management ◽  
Source Code ◽  
Object Oriented ◽  
Original System ◽  
Software Systems ◽  
Legacy Systems ◽  
Dynamic Binding ◽  
Legacy Software ◽  
Original Program

Object-oriented languages support many modern programming concepts such as information hiding, inheritance, polymorphism, and dynamic binding. As a result, software systems implemented in OO languages are in general more reusable and reliable than others. Many legacy software systems, created before OO programming became popular, need to be redesigned and updated to OO programs. The process of abstracting OO designs from the procedural source code has often been done with limited assistance from program structural diagrams. Most reengineering focuses on the functionality of the original program, and the OO redesign often results in a completely new design based on the designers' understanding of the original program. Such an approach is not sufficient because it may take a significant amount of time and effort for designers to comprehend the original program. This paper presents a computer-aided semi-automatic method that abstracts OO designs from the original procedural source code. More specifically, it is a method for OO redesign based on program structural diagrams, visualization, and execution slices. We conducted a case study by applying this method to an inventory management software system. Results indicate that our method can effectively and efficiently abstract an appropriate OO design out of the original C code. In addition, some of the code from the original system can be automatically identified and reused in the new OO system.

scholarly journals Business Modeling in Process-Oriented Organizations for RUP-Based Software Development

2011 ◽  
pp. 98-117 ◽  
Author(s):  
Francisco J. Duarte ◽  
João M. Fernandes ◽  
Ricardo J. Machado
Keyword(s):  
Software Development ◽  
Process Model ◽  
Development Process ◽  
Business Processes ◽  
Software Systems ◽  
Business Modeling ◽  
Hierarchical Arrangement ◽  
Develop Software ◽  
Software House ◽  
Process Oriented

Several organizations are nowadays not particularly comfortable with their internal structuring based on a hierarchical arrangement (sub-divided in departments), where collaborators with a limited view of the overall organization perform their activities. Those organizations recognize the need to move to a model where multi-skilled teams run horizontal business processes that cross the organization, and impact suppliers and clients. To develop software systems for any organization, the development process must always be appropriate and controlled. Additionally for organizations who want to migrate to a horizontal business processes view, it is required to model the organizational platform where the organizational processes will run. This necessity is also true when the organization under consideration is a software house. In this chapter, a proposal of a generic framework for process-oriented software houses is presented. The way of managing the process model and the instantiation of their processes with the Rational Unified Process (RUP) disciplines, whenever they are available, or with other kind of processes is recommended as a way to control and define the software development process. To illustrate the usefulness of the proposal, it is presented how the generic reference framework was executed in a real project called “Premium Wage” and shown, in some detail, the created artifacts (which include several UML models) during the development phases following the RUP disciplines, especially the artifacts produced for business modeling.

An Approach to Evolving Legacy Software System into Cloud Computing Environment

2013 ◽  
pp. 207-229
Author(s):  
Shang Zheng ◽  
Feng Chen ◽  
Hongji Yang ◽  
Jianzhi Li
Keyword(s):  
Cloud Computing ◽  
Banking System ◽  
Software Systems ◽  
Legacy Systems ◽  
Problem Solution ◽  
Cloud Environment ◽  
New Paradigm ◽  
Legacy Software ◽  
Service Oriented ◽  
Resources Sharing

Cloud computing is a new paradigm for the intent of distributed resources sharing and coordinated problem solution. Affected by the Cloud trend and Service-Oriented need, many existing software systems will become legacy systems. These legacy software systems will need Cloud Oriented reengineering, which can facilitate the legacy systems reusable in Cloud Oriented architecture and allow the integration of legacy resources with Cloud features. This research focuses on establishing a general framework to assist with the evolution of legacy systems into Cloud environments. The methodology includes various phases, which use reverse engineering techniques to comprehend and decompose legacy systems, represent legacy resources by XML as Cloud component and integrate these Cloud components into Cloud environment. In this research, a legacy banking system has been chosen as a case study to prove the feasibility of the proposed approach. The legacy banking system can be transformed to run as a Service-Oriented Cloud application, which illustrates the proposed approach is powerful for utilising reusable legacy resources into Cloud environment.

scholarly journals Business Modeling in Process-Oriented Organizations for RUP-Based Software Development

2009 ◽  
pp. 2510-2527
Author(s):  
João M. Fernandes ◽  
Ricardo J. Machado
Keyword(s):  
Software Development ◽  
Process Model ◽  
Development Process ◽  
Business Processes ◽  
Software Systems ◽  
Business Modeling ◽  
Hierarchical Arrangement ◽  
Develop Software ◽  
Software House ◽  
Process Oriented

Several organizations nowadays are not particularly comfortable with their internal structuring based on a hierarchical arrangement (sub-divided in departments), where collaborators with a limited view of the overall organization perform theiractivities. Those organizations recognize the need to move to a model where multi-skilled teams run horizontal business processes that cross the organization and impact suppliers and clients. To develop software systems for any organization, the development process must always be appropriate and controlled. Additionally, for organizations that want to migrate to a horizontal business processes view, it is required to model the organizational platform where the organizational processes will run. This necessity is also true when the organization under consideration is a software house. In this chapter, a proposal of a generic framework for process-oriented software houses is presented. The way of managing the process model and the instantiation of their processes with the rational unified process (RUP) disciplines, whenever they are available or with other kind of processes, is recommended as a way to control and define the software development process. To illustrate the usefulness of the proposal, the chapter presents how the generic reference framework was executed in a real project called “Premium Wage” and shows, in some detail, the created artifacts (which include several UML models) during the development phases following the RUP disciplines, especially the artifacts produced for business modeling.

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

2016 ◽  
Vol 6 (1) ◽  
pp. 292
Author(s):  
M. Srinivas ◽  
G. Ramakrishna ◽  
K. Rajasekhara Rao ◽  
E. Suresh Babu
Keyword(s):  
Information And Communication Technologies ◽  
Business Processes ◽  
Software Evolution ◽  
Business Environment ◽  
Software Systems ◽  
Legacy Systems ◽  
Application Development ◽  
Global Business ◽  
Legacy System ◽  
Legacy Applications

<p class="PreformattedText">Software evolution is one of the challenging issues in today’s business environment. It is necessary for the organizations, which make use of Information, and Communication Technologies will have to align their business processes to compete with global business. The existing large software systems (“legacy” systems) have never been built to cope with the current business requirement for their poor coding, design structures, logic and documentation. Moreover, Legacy applications have various problems such as lack of up to-date documentation, skilled man power, resources of the Legacy applications, and high maintenance costs. Even though the Legacy system is obsolete, it contains detailed business rules and in continuous use, because it satisfies the users' needs and forms the backbone of the information flow of organization. One of the possible solutions is to refactor or modernize those systems into a new platform. It is necessary to analyse the existing legacy system for better understanding the business logic and its functionalities. This paper analyses various techniques proposed for understanding Legacy systems in existence.</p>

Sign in / Sign up

Export Citation Format

Share Document