Software Reengineering

The identification of design patterns as part of the reengineering process can convey important information to the designer.
However, existing pattern detection methodologies generally have problems in dealing with one or more of the following issues:
Identification of modified pattern versions, search space explosion for large systems and extensibility to novel patterns. In this paper, a design pattern detection methodology is proposed that is based on similarity scoring between graph vertices. Due to the nature of the underlying graph algorithm, this approach has the ability to also recognize patterns that are modified from their standard representation. Moreover, the approach exploits the fact that patterns reside in one or more inheritance hierarchies, reducing the size of the graphs to which the algorithm is applied. Finally, the algorithm does not rely on any pattern-specific heuristic, facilitating the extension to novel design structures. Evaluation on three open-source projects demonstrated the accuracy and the efficiency of the proposed method.

We present the R 2 D 2 redundancy detector. R 2 D 2 identifies redundant code fragments in large software systems written in Lisp. For each pair of code fragments, R 2 D 2 uses a combination of techniques ranging from syntaxbased analysis to semantics-based analysis, that detects positive and negative evidences regarding the redundancy of the analyzed code fragments. These evidences are combined according to a well-defined model and sufficiently redundant fragments are reported to the user. R 2 D 2 explores several techniques and heuristics to operate within reasonable time and space bounds and is designed to be extensible.

M a y / J u n e 2 0 0 2 0 7 4 0 -7 4 5 9 / 0 2 / $ 1 7 . 0 0 © 2 0 0 2 I E E E during the reengineering process. We propose tracing "all around"-from existing code to the legacy system's design to its requirements during reverse engineering, and from the modified requirements to the new design and the new code during development of the successor system. In effect, this means integrating traceability during reverse engineering with (more standard) traceability during forward engineering. Our approach uses the Requirements Engineering Through Hypertext (RETH) method and tool to install traces during both reverse and forward engineering. 2,3 Our experience in a real-world reengineering project suggests that all-around tracing can yield immediate benefits that appear to be specific to reengineering. In this article, we describe all-around tracing and present a case study to demonstrate how our approach can be useful in reengineering efforts.

Refactoring tools are extremely important to prevent errors in legacy systems restructuring. Unfortunately, to be effective, these tools require huge computer resources that cause unacceptable inefficiencies or limit the size of the restructured programs or even the programming language expressiveness. Previous approaches also made it difficult for the programmer to extend the tool with new refactoring operations.

This paper addresses the challenge of automated remodularization of large systems as microservices. It focuses on the analysis of enterprise systems, which are widely used in corporate sectors and are notoriously large, monolithic and challenging to manually decouple because they manage asynchronous, userdriven business processes and business objects (BOs) having complex structural relationships. The technique presented leverages semantic knowledge of enterprise systems, i.e., BO structure, together with syntactic knowledge of the code, i.e., classes and interactions as part of static profiling and clustering. On a semantic level, BOs derived from databases form the basis for prospective clustering of classes as modules, while on a syntactic level, structural and interaction details of classes provide further insights for module dependencies and clustering, based on K-Means clustering and optimization. Our integrated techniques are validated using two open source enterprise customer relationship management systems, SugarCRM and ChurchCRM. The results demonstrate improved feasibility of remodularizing enterprise systems (inclusive of coded BOs and classes) as microservices. Furthermore, the recommended microservices, integrated with 'backend' enterprise systems, demonstrate improvements in key non-functional characteristics, namely high execution efficiency, scalability and availability.

Abstract This paper describes a unifying structure for the full spectrum of activities that constitute a reengineering project. Part of the framework's" value added" is its usefulness as a reference model for planning a reengineering project and for identifying, describing, understanding, assessing, or evaluating the technical, managerial, and project-related factors that characterize reengineering efforts. The framework can serve as a tool for planning, implementing, and assessing reengineering projects.

Many information systems are reengineered and redeveloped in practice, since they are legacy software. Typically, no requirements and design specifications exist and, therefore, also no traceability information. While especially the long-term utility of such information is well known, an important question in reengineering is whether installing it can have immediate benefits in the course of the reengineering effort. Are there even special benefits of traceability for reengineering? In this paper, we argue for completely tracing all around from code over specifications to code in the course of reverse engineering an existing software system and its subsequent redesign and redevelopment. Experience from a real-world project indicates that it can indeed be useful in practice to provide traceability all around also for the developers and in terms of short-term benefits already during the development. We found several cases where traceability provided benefits that appear to be specific for reengineering. As a consequence, we recommend special emphasis on traceability during reengineering legacy software.

In software development life cycle, software maintenance is among the critical phases. It is a postimplementation activity that requires rigorous human efforts. For any software developer, maintaining software for a longer period is the primary objective. This objective can be accomplished if good quality software is developed. Maintainability is one of the vital characteristics of software maintenance. Maintainability enables developers to keep the system alive for a longer period of time at a limited cost. Software Maintainability can be enhanced using reengineering. The proposed research validates improvement in the quality of the reengineered software system. The quality of the software is analyzed using a coupling, cohesion, inheritance, and other essential design metrics. The observed improvement in the software design is 62.1%. The execution time of the software is also reduced by 6.5%. Reduction in the cost of maintenance is also another important outcome of this research. The observed reduction in the maintenance cost is 36.8%. Thus, the main objective of the proposed research is to analyze and validate the quality improvement in the reengineered software. Agile Scrum methodology has been used to perform software reengineering. Design Metrics are measured using the Chidamber and Kemerer Java metric (CKJM) version-9.0 tool. For reengineering implementation, Net Beans 7.3 has been used.
Keywords: Software quality, Software metric, Software Engineering, Reengineering, Software maintainability

Understanding systematically the modernization literature and grasping the major concepts is challenging and timeconsuming. Even more, research evolves, and it does it based on the assumption that many words (such as migration) have a single well-known meaning that we all share. Since these word meanings are rarely explicit, and their usage heterogeneous, these words end up polluted with multiple and many times opposite or incompatible senses. In this context, we ask the following question: What would be a valid theoretical framework that relates and gives meaning to the techniques, technologies and concepts that are required to achieve an iterative incremental migration process successfully?. This article contributes multiple bottom-up taxonomies that cover the various concepts that characterize a modernization: Legacy systems, their decline by decadence and obsolescence, the reasons that drive to recover from this decline, the different families of approaches to recover from decline, how each of these families of solutions instruments their processes and the material relation in between these processes and the features that are recognized as key in software engineering: iterativity, incrementality and validity. For building these taxonomies we propose eleven different research questions to guide the crafting of the taxonomies. To respond to this question we conduct a carefully detailed Systematic Literature Review protocol resulting in the selection of 30 articles. We extract the qualitative data to respond to the research questions by applying the Grounded Theory approach with open codification. The application of the method produced 756 different codes, and an appendix, all this content available online. This article includes more than 20 definitions, arranged in 5 taxonomies, responding to each of the eleven research questions. It also provides the mapping between different taxonomies and the classification of all our readings with the produced taxonomies. After discussing the threats to the validity, the article finishes with the proposal of a few research directions and a conclusion

The present research estimates the efficacy of a legacy program and the areas of its development. The research also intends to put forward as to what extent reengineering of a legacy program has to be done on the basis of the estimation approach. The study has tried to outline the current issues and trends in reengineering of a legacy program from various perspectives. An allinclusive literature review reveals that a lot of work has already been piled up with legacy system estimation and the reengineering domain, yet the basic assumptions of Complexity, Quality and Effort have not been worked out collectively. Hence the present research underlines this very maxim and studies the reengineering of a legacy program on the paradigms of Quality, Complexity, and Effort Estimation collectively. The findings put forward an equation and reengineering scale which would be highly compatible with present technology for the feasibility of an effective reengineering.

Reengineering of legacy program is the most important issue faced by software industry. There are many challenges in the way of reengineering, so to overcome these problems some important dimensions are explored. There are many factors which identify the reengineering dimensions like environmental, size, economical, technical etc. In the present work an attempt has been made by review of literature to identify the dimensions and their parameters in the software Industry. In the present study these dimensions are analysed by conceptual and empirical studies.

The availability of computer-aided systems-engineering environments has redefined the organization system development. Pace of change accelerates in the twenty-first century as a result of technological opportunities, liberalization of the world markets, demands for innovation and continually decreasing life cycle of software. Organizations have to continuously readjust and realign their operation to meet all these challenges. This pace of changes has increasingly forced organization to be more outward looking, market-oriented and knowledge driven. This paper present integrated framework of how reverse engineering process work goes in Enterprise Information System(EIS).The essential functions in reverse engineering, how they are associated with EIS, what will be the impact on the organization which is using reverse engineering.

Generally an organization using the labor system to carry the material from different points and it takes more
expenditure. Our analytical study finds out that using the machinery system we can reduce the amount of expenditure. We
propose a new definition of supply chain management on the basis of statically analysis in this paper; we focus the latest
technology of machinery system. Through these systems we can reduce upcoming expenditure to carry the material from
different stages. We also propose a new process of SCM to manage the chain system of material. As we know that everything
has positive and negative attitudes so our proposal also satisfy these statements and finally we gave the analytical study of
research on supply chain management.

"Currently available software requirements engineering processes do not study operational business processes’ performances to identify performance specific improvement scopes and do not
relate the same to maximise business benefits through  optimizing technology capabilities. Business analysts’ concept of business process reengineering and software system analysts’ concept of software engineering aiming for the same goal of business benefit increase, are digitally divided by their information technological and business performance knowledge gap. The paper proposes a software requirements engineering process incorporating operational process evaluation and baselining, business process reengineering, goal and role based requirements analysis with measurable increase in business benefits through performance improvement and selecting technology capabilities. It suggests that traditional software requirements engineering activities need to be mingled with business process reengineering activities and requirements measurement and management matrices for different business domains need to be prescribed."