Is a strategy for code smell assessment long overdue?
Is a strategy for code smell assessment long overdue?
复制标题
DOI：
10.1145/1809223.1809228
复制
发表时间：
2010-05
期刊：
影响因子：
--
通讯作者：
S. Counsell;R. Hierons;H. Hamza;S. Black;M. Durrand
中科院分区：
文献类型：
--
作者：
S. Counsell;R. Hierons;H. Hamza;S. Black;M. Durrand
代码气味反映了代码衰减，因此，开发人员应试图通过以一种或多种重构的形式使用“除臭剂”来消除这种气味。但是，在理论上或经验上，探索代码探索代码的缺乏表明，既没有在愤怒中使用气味，也不是大量研究的主题。在本文中，我们提出了三项研究，作为这一主张的支持证据。第一个是对五个开源Java系统组的分析，第二次是对专有，基于C＃Web应用程序的子系统的经验研究，第三个是对气味相关的重构的理论列举。这项研究的主要发现是首先，开发人员似乎避免消除表面上“简单”的气味，而倾向于更“晦涩”的气味。其次，试图识别臭代码时，很快就出现了各种冲突和异常。最后，消除气味的努力可能是一个关键因素。该研究强调了关于代码气味问题及其识别和测量各个方面的更清晰的研究策略的需求。
Code smells reflect code decay and, as such, developers should seek to eradicate such smells through application of 'deodorant' in the form of one or more refactorings. However, a dearth of studies exploring code smells either theoretically or empirically suggests that there are reasons why smell eradication is neither being applied in anger, nor the subject of significant research. In this paper, we present three studies as supporting evidence for this claim. The first is an analysis of a set of five, open-source Java systems, the second an empirical study of a sub-system of a proprietary, C# web-based application and the third, a theoretical enumeration of smell-related refactorings. Key findings of the study were first, that developers seemed to avoid eradicating superficially 'simple' smells in favor of more 'obscure' ones; second, a wide range of conflicts and anomalies soon emerged when trying to identify smelly code. Finally, perceived effort to eradicate a smell may be a key factor. The study highlights the need for a clearer research strategy on the issue of code smells and all aspects of their identification and measurement.