Software Re-engineering Projects Research Articles

SPReaD: service-oriented process for reengineering and DevOps

The reengineering of systems into a microservice-based architecture can be seen as an implementation of a service-oriented architecture (SOA). However, the deployment of SOA into an enterprise is a challenging task, as it may involve the modernization of mission-critical systems with high technical debt and high maintenance costs. To this end, a process is required to provide an appropriate set of steps and techniques that minimize risks and at the same time ensure the quality of the systems during the migration process. Thus, this work presents the Service-oriented Process for Reengineering and DevOps—SPReaD, an instantiation of the mainstream SOA methodology focusing on the reengineering of legacy systems integrating DevOps aspects for developing microservices systems. This process has been defined during a real software reengineering project of legacy systems from a Brazilian State Department of Taxation. The results obtained include a substantial improvement in the quality of the main taxation system used by the state, including not only code-related metrics but also performance improvements of the services offered, and a change in the methodology adopted by the software development team.

Estimation of Risk in Software Re-engineering Projects

Estimation of Risk in Software Re-engineering Projects

Aufwandsschätzung von Software-Reengineering-Projekten

Prediction of costs and duration of software reengineering projects Costs and duration of projects to reengineer existing software are much easier to predict than the respective figures for software development projects. Moreover, in reengineering projects costs, risks and duration are much smaller. This article presents a tool-based method to calculate the three most important reengineering project types: encapsulation projects, renovation projects, and conversion projects. The method comprises eight consecutive steps — starting from reengineering requirements and ending with risk assessments and adjustments. A set of well-known prediction methods are incorporated, among them COCOMO, component analysis, function point analysis, data point analysis, and object point analysis. The method lays particular focus on the size of the projected software as well as on its complexity and quality.

Enterprise Networks: The Re-engineering of Complex Software Systems

Today technology design can no longer be understood as a design process on a “green site”. Design and implementation of new technology are always dependent on existing technology and the way it is used by people. In this respect Software-Engineering has also changed to the characteristics of “normal” technology design taking into account existing computer systems. Experiences show that the conditions and needs of such Software-Reengineering projects are highly complex and differ in their special characteristics ranging from aspects of quality of existing system documentation to organizational structures of the computer departments concerned. The Task-Artifact Cycle presented here gives a suitable engineering approach emphasizing both analysis and design in Software-Reengineering.

Enterprise Networks: The Re-Engineering of Complex Software Systems

Today technology design can no longer be understood as a design process on a “green site”. Design and implementation of new technology are always dependent on existing technology and the way it is used by people. In this respect Software-Engineering has also changed to the characteristics of “normal” technology design taking into account existing computer systems. Experiences show that the conditions and needs of such Software-Reengineering projects are highly complex and differ in their special characteristics ranging from aspects of quality of existing system documentation to organizational structures of the computer departments concerned. The Task-Artifact Cycle presented here gives a suitable engineering approach emphasizing both analysis and design in Software Reengineering.

An incremental approach to software systems re-engineering

Software re-engineering can dramatically improve an organization's ability to maintain and upgrade its legacy production systems. But the risks that accompany traditional re-engineering tend to offset the potential benefits. Incremental software re-engineering is the practice of re-engineering a system's software components on a phased basis, and then re-incorporating those components into production also on a phased basis. Incremental software re-engineering allows for safer re-engineering, increased flexibility and more immediate return on investment. But commercial automation to support incremental software re-engineering is currently weak. In addition, project managers need a methodology to plan and implement software re-engineering projects based on the incremental approach. This paper covers the advantages of incremental software re-engineering and what is available concerning support technology. The paper describes a process methodology for planning and implementing incremental software re-engineering projects. Finally, gaps in the support technology are identified with suggestions for future tools from vendors. © 1998 John Wiley & Sons, Ltd.

An incremental approach to software systems re‐engineering

Software re-engineering can dramatically improve an organization's ability to maintain and upgrade its legacy production systems. But the risks that accompany traditional re-engineering tend to offset the potential benefits. Incremental software re-engineering is the practice of re-engineering a system's software components on a phased basis, and then re-incorporating those components into production also on a phased basis. Incremental software re-engineering allows for safer re-engineering, increased flexibility and more immediate return on investment. But commercial automation to support incremental software re-engineering is currently weak. In addition, project managers need a methodology to plan and implement software re-engineering projects based on the incremental approach. This paper covers the advantages of incremental software re-engineering and what is available concerning support technology. The paper describes a process methodology for planning and implementing incremental software re-engineering projects. Finally, gaps in the support technology are identified with suggestions for future tools from vendors. © 1998 John Wiley & Sons, Ltd.

Enterprise networks: The re-engineering of complex software systems

Today technology design can no longer be understood as a design process on a ‘green site’. Design and implementation of new technology are always dependent on existing technology and the way it is used by people. In this respect Software-Engineering has also changed to the characteristics of ‘normal’ technology design taking into account existing computer systems. Experiences show that the conditions and needs of such Software-Reengineering projects are highly complex and differ in their special characteristics ranging from aspects of quality of existing system documentation to organizational structures of the computer departments concerned. The Task-Artifact Cycle presented here gives a suitable reengineering approach emphasizing both analysis and design in Software-Reengineering.

On the re-engineering of transaction systems

This paper provides a framework for considering the problems of re-engineering transaction processing systems. Such systems are key components of most modern business operations, and their continued enhancement is crucial for competitiveness. The paper grew out of a study of software re-engineering problems and practices carried out by Andersen Consulting at several major companies in the telecommunications industry. It describes some of the practical difficulties found in re-engineering transaction systems, especially the problems caused by the need for an incremental approach and the difficulties of re-engineering in parallel with the continuing evolution of the operational system. This paper presents a model of the maintenance and re-engineering processes showing the main activities that are needed and the data flows among them. Existing tools for re-engineering are then analysed against this model to identify gaps and potential for further tool development. Finally, there is a brief discussion of the very stringent personnel needs of software re-engineering projects.