Which Features Do My Users (Not) Use?

Eder, Sebastian; Femmer, Henning; Hauptmann, Benedikt; Junker, Maximilian

doi:10.1109/icsme.2014.71

Cited by 4 publications

(3 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A table with the full list of the 211 successfully debloated libraries that pass all the tests is available in the replication package of this paper. 15 We excluded 61 ( 20.2 %) libraries because the numbers of executed tests before and after the debloating did not match. This is due to changes in the tests' coniguration after injecting JDBL into the build of the libraries.…”

Section: Rq2mentioning

confidence: 99%

See 1 more Smart Citation

Coverage-Based Debloating for Java Bytecode

Soto-Valero

Durieux

Harrand

et al. 2023

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

Software bloat is code that is packaged in an application but is actually not necessary to run the application. The presence of software bloat is an issue for security, for performance, and for maintenance. In this paper, we introduce a novel technique for debloating, which we call coverage-based debloating. We implement the technique for one single language: Java bytecode. We leverage a combination of state-of-the-art Java bytecode coverage tools to precisely capture what parts of a project and its dependencies are used when running with a specific workload. Then, we automatically remove the parts that are not covered, in order to generate a debloated version of the project. We succeed to debloat 211 library versions from a dataset of 94 unique open-source Java libraries. The debloated versions are syntactically correct and preserve their original behavior according to the workload. Our results indicate that \(68.3\% \) of the libraries’ bytecode and \(20.3\% \) of their total dependencies can be removed through coverage-based debloating. For the first time in the literature on software debloating, we assess the utility of debloated libraries with respect to client applications that reuse them. We select 988 client projects that either have a direct reference to the debloated library in their source code or which test suite covers at least one class of the libraries that we debloat. Our results show that \(81.5\% \) of the clients, with at least one test that uses the library, successfully compile and pass their test suite when the original library is replaced by its debloated version.

show abstract

Section: Rq2mentioning

confidence: 99%

“…Research interest in software debloating has grown in recent years, motivated by the reuse of large open-source libraries designed to provide several functionalities for diferent clients [15,27]. Seminal work on debloating for Java programs was performed by Tip et al [53,54].…”

Section: Sotware Debloatingmentioning

confidence: 99%

Coverage-Based Debloating for Java Bytecode

Soto-Valero

Durieux

Harrand

et al. 2023

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

show abstract

“…Research interest in software debloat has grown in recent years, motivated by the reuse of large open-source libraries designed to provide several functionalities for different clients [24], [25]. Seminal work on debloat for Java programs was performed by Tip et al [26], [27].…”

Section: Software Debloatmentioning

confidence: 99%

Coverage-Based Debloating for Java Bytecode

Soto-Valero¹,

Durieux²,

Harrand³

et al. 2020

Preprint

View full text Add to dashboard Cite

Software bloat is code that is packaged in an application but is actually not used and not necessary to run the application. The presence of bloat is an issue for software security, for performance, and for maintenance. In recent years, several works have proposed techniques to detect and remove software bloat. In this paper, we introduce a novel technique to debloat Java bytecode through dynamic analysis, which we call trace-based debloat. We have developed JDBL, a tool that automates the collection of accurate execution traces and the debloating process. Given a Java project and a workload, JDBL generates a debloated version of the project that is syntactically correct and preserves the original behavior, modulo the workload. We evaluate the feasibility and the effectiveness of trace-based debloat with 395 open-source Java libraries for a total 10M+ lines of code. We demonstrate that our approach significantly reduces the size of these libraries while preserving the functionalities needed by their clients.

show abstract