1 of 9

An Introduction to

Bloat History Analysis

César Soto Valero

cesarsv@kth.se

​

November 5th, 2020

20th ASSERT Workshop

2 of 9

2

3 of 9

The panorama in software development...

3

4 of 9

4

5 of 9

5

6 of 9

Intuitive causes

  • Most codebases are add only
  • Developers have fear to break things
  • Legacy code
  • Bad design
  • Technical debt
  • Lack of adoption of good practices
  • Debloat tools not always available

6

7 of 9

Tentative RQs

For a piece of bloated code:

  • RQ1: What is its status at different time intervals?
  • RQ2: How it is managed by developers?

For a project:

  • RQ3: How does the bloat evolves through its history?
  • RQ4: What variables are more related to the presence of bloat?

​

7

8 of 9

Objectives

  • Characterize bloat through the history of software projects
  • Understand the nature of the phenomenon of bloat
  • Quantify the impact of bloat in OSS
  • Propose new metrics

8

9 of 9

WIP

To be continue...

​

9