Assessing technical debt by identifying design flaws in software systems

PROJECT TITLE :

Assessing technical debt by identifying design flaws in software systems

ABSTRACT :

Tough time-to-market constraints and unanticipated integration or evolution issues lead to design tradeoffs that usually cause flaws in the structure of a software system. So, maintenance prices grow significantly. The impact of these design decisions, which give short-term benefits at the expense of the system’s design integrity, is sometimes referred to as technical debt. During this paper, I propose a novel framework for assessing technical debt employing a technique for detecting style flaws, i.e., specific violations of well-established style principles and rules. To form the framework comprehensive and balanced, it is built on high of a group of metrics-primarily based detection rules for well-known design flaws that cowl all of the main aspects of design like coupling, complexity, and encapsulation. I demonstrate the effectiveness of the framework by assessing the evolution of technical debt symptoms over a total of sixty three releases of two widespread Eclipse® projects. The case study shows how the framework will detect debt symptoms and past refactoring actions. The experiment conjointly reveals that within the absence of such a framework, restructuring actions are not continually coherent and systematic, not even when performed by terribly experienced developers.

Did you like this research project?

To get this research project Guidelines, Training and Code... Click Here