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 object-oriented applications to component-based ones will contribute to improve these characteristics (maintainability and reuse). In this paper, we propose an approach to automatically transform object-oriented 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.

Sensitivity Analysis of Evolutionary Algorithm for Software Reusability

“…Two or more individual reusable components are grouped together to form a cohesive cluster and all such clusters with higher values of TurboMQ are identified in the cluster solution of the Pareto front obtained. Finally, the obtained results are investigated using the metric proposed in equation (1). As part of the analysis, the following research questions are formulated: RQ1.…”

“…Here, the sensitivity analysis is measured by computing the amount of deviation corresponding to the deviation introduced in the quality indicator function. This deviation is computed in terms of percentage, using equation (1).…”

“…These extracted components can be reused while developing other similar applications by using them from the component library. Many different approaches are proposed in the literature for extracting reusable components from the source-code of existing OO applications or legacy systems [3,5,8,6,1].…”

Refactoring Monolithic Object-Oriented Source Code to Materialize Microservice-oriented Architecture

“…The inheritance violation is caused when a class that inherits from another class belonging to a different microservice are encapsulated. To heal this encapsulation violation, we propose a two-step transformation process inspired from (Alshara et al, 2015): (i) Uncoupling the child/parent inheritance with a double proxy pattern. (ii) Recreating subtyping via interface inheritance.…”

“…The second mechanism that must be reproduced is the concept of polymorphic assignment. To preserve the first mechanism, we propose a double proxy pattern inspired by the work presented in (Alshara et al, 2015). In (Alshara et al, 2015), the authors propose a double delegate pattern to preserve the inheritance between the child and its parent class, residing each in a different components.…”