Refactoring: improving the design of existing code
Refactoring: improving the design of existing code
Test Driven Development: By Example
Test Driven Development: By Example
A Survey of Software Refactoring
IEEE Transactions on Software Engineering
Software architecture improvement through test-driven development
OOPSLA '05 Companion to the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Breaking the barriers to successful refactoring: observations and tools for extract method
Proceedings of the 30th international conference on Software engineering
Do Crosscutting Concerns Cause Defects?
IEEE Transactions on Software Engineering
How we refactor, and how we know it
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
An exploratory study of code smells in evolving aspect-oriented systems
Proceedings of the tenth international conference on Aspect-oriented software development
PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement
Extracting and evolving mobile games product lines
SPLC'05 Proceedings of the 9th international conference on Software Product Lines
| Hi-index | 0.00 |
There is growing empirical evidence that some (patterns of) code smells seem to be, either deliberately or not, ignored. More importantly, there is little knowledge about the factors that are likely to influence the longevity of smell occurrences in software projects. Some of them might be related to limitations of tool support, while others might be not. This paper presents the preliminary results of an explanatory survey aimed at better understanding the longevity of code smells in software projects. A questionnaire was elaborated and distributed to developers, and 33 answers were collected up to now. Our preliminary observations reveal, for instance, that smell removal with refactoring tools is often avoided when maintaining frameworks or product lines.