Migrating large object-oriented Applications into component-based ones: instantiation and inheritance transformation

Abstract

Large object-oriented applications have complex and numerous dependencies, and usually do not have explicit software architectures. Therefore they are hard to maintain, and parts of them are difficult to reuse. Component-based development paradigm emerged for improving these aspects and for supporting effective maintainability and reuse. It provides better understandability through a high-level architecture view of the application. Thereby migrating objectoriented applications to component-based ones will contribute to improve these characteristics (maintainability and reuse). In this paper, we propose an approach to automatically transform objectoriented applications to component-based ones. More particularly, the input of the approach is the result provided by software architecture recovery: a component-based architecture description. Then, our approach transforms the object-oriented source code in order to produce deployable components. We focus in this paper on the transformation of source code related to instantiation and inheritance dependencies between classes that are in different components. We experimented the proposed solution in the transformation of a collection of Java applications into the OSGi framework. The experimental results are discussed in this paper.

Defaultification refactoring: A tool for automatically converting Java methods to default

“…Other refactorings [8,14,15] reorganize type hierarchies, though not for default methods. [16] and [17] transform Java programs to use lambda expressions and enumerated types, respectively, while [18] demacrofies C++11 programs.…”

Refactoring Object-Oriented Applications towards a better Decoupling and Instantiation Unanticipation

“…The implementation class is instantiated and injected at runtime by an object container, such as Spring's one 3 . The first case that we deal with is the one where an instantiation is made inside a method/constructor, the reference to the created instance is stored in a field, and the instantiation does not take any argument or it takes attainable ones (arguments whose values can be calculated by a static analysis).…”

“…This method makes component interfaces operational by the use of two design patterns: Adapter and Façade. In another work, Alshara et al [3] proposed another approach to automatically transform Java applications into OSGi ones. This approach takes as input a Java application and the description of its CB architecture.…”

“…Existing works that propose migration solutions [2,3] consider that the modularity and reuse unit, i.e. the component, is a group of classes, called a cluster.…”

Multi-paradigm Architecture Constraint Specification and Configuration Based on Graphs and Feature Models

“…We take the example of an object-oriented application which is designed with UML and implemented with java, and which represents an information screen [2]. This application simulates the behavior of an information screen, a software system which displays in a public transportation's embedded screen, the names of stations, the expected time at each station, etc.…”