Missing link smell occurs when developers contribute to the same source code without communicating with each other. Existing studies have analyzed relationship of missing smells and developer contribution. However, productivity involved in has not been explored yet. This study investigates how differs between smelly non-smelly developers. For this purpose, seven open-source projects are analyze...

Software repositories are typically used to store code together with additional information. These repositories are a valuable source to train knowledge discovery algorithms to detect code smells and other qualitative defects. In this paper we present a lightweight framework to detect previously unknown knowledge from software reposit ories to support refactoring. The results will be usable by ...

In this paper we present RUST, an environment that assists the programmer in locating potential code improvements by searching for a set of predetermined patterns, identifying these areas as code smells, and providing a means to automatically implement refactorings. Results and changes are presented using an interface that allows the user to examine the affected code, try out and see the result...

This paper presents our empirical observations related to the evolution of a large automated test system. The system observed is used in the industry as a test tool for complex telecommunication systems, itself consisting of more than one million lines of source code. This study evaluates how different changes during the development have changed the number of observed Code Smells in the test sy...

A code smell is a surface indicator of an inherent problem in the system, most often due to deviation from standard coding practices on developer’s part during development phase. Studies observe that smells made more susceptible call for modifications and corrections than did not contain smells. Restructuring at early stage saves exponentially increasing amount effort it would require address i...

In this paper, we present our approach to a visual refactoring tool, the Type Access Analyzer (TAA), which uses program analysis to detect code smells and for suggesting and performing refactorings related to typing. In particular, the TAA is intended to help the developers with consistently programming to interfaces.

Anti-patterns and code-smells are signs in the source code which are not defects (does not prevent the program from functioning and does not cause compile errors) and are rather indicators of deeper and bigger problems. Exception handling is a programming construct designed to handle the occurrence of anomalous or exceptional conditions (that changes the normal flow of program execution). In th...

Recommendation Systems for Software Engineering are created for a variety of purposes, such as recommending sample code or to call attention to bad coding practices (code smells). We have created a system to recommend the use of design patterns. While many programmers have knowledge of design patterns, whether rushed to meet deadlines, inexperienced in their implementations, or unaware of a par...