Identifying software components from object-oriented APIs based on dynamic analysis

Abstract

The reuse at the component level is generally more effective than the one at the object-oriented class level. This is due to the granularity level where components expose their functionalities at an abstract level compared to the fine-grained object-oriented classes. Moreover, components clearly define their dependencies through their provided and required interfaces in an explicit way that facilitates the understanding of how to reuse these components. Therefore, several component identification approaches have been proposed to identify components based on the analysis object-oriented software applications. Nevertheless, most of the existing component identification approaches did not consider co-usage dependencies between API classes to identify classes/methods that can be reused to implement a specific scenario. In this paper, we propose an approach to identify reusable software components in object-oriented APIs, based on the interactions between client applications and the targeted API. As we are dealing with actual clients using the API, dynamic analysis allows to better capture the instances of API usage. Approaches using static analysis are usually limited by the difficulty of handling dynamic features such as polymorphism and class loading. We evaluate our approach by applying it to three Java APIs with eight client applications from the DaCapo benchmark. DaCapo provides a set of pre-defined usage scenarios. The results show that our component identification approach has a very high precision.

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

“…While in (El Hamdouni et al, 2010), relational concept analysis is used to extract a component-based architecture. Finally, (Shatnawi et al, 2018) uses dynamic analysis to identify components.…”

Runtime Monitoring in Continuous Deployment by Differencing Execution Behavior Model

“…Execution logs have been extensively studied in such contexts as anomaly detection [4] [20], identification of software components [24], component behavior discovery [17], process mining [28], behavioral differencing [12], failure diagnosis [25], fault localization [30], invariant inference [5], and performance diagnosis [10] [26]. In this section, we focus on automatic analysis of execution logs.…”

Automate migration to microservices architecture using Machine Learning techniques

“…Over the past decades, software engineering research identified and attempted to solve a variety of issues pertaining to several phases of the software lifecycle. However, the fast pace of evolution in the IT industry and the staggering growth of new technologies [50] based on APIs [30,45,25], containers [48], microservices [40,1,41,29], cloud and virtualization, put an increasing pressure on software development [2] and deployment [49,47] practice to fully exploit this paradigm shift. This led to constant questioning of existing techniques [30] and results of software engineering research [36,35], leading to investigating the use of AI and ML-based techniques to solve software engineering problems in topics related to software reuse [16], recommendation systems [34], mining software repositories [36], software data analytics and patterns mining [38,19,37,31] , program analysis and visualization [39,33], testing in the cloud environment, Edge-Enabled systems [24], microservices architecture [43] and mobile applications.…”