An Empirical Investigation of Code Smell 'Deception' and Research Contextualisation through Paul's Criteria

Counsell, Steve; Hamza, Hamza; Hierons, Rob M.
December 2010
Journal of Computing & Information Technology;Dec2010, Vol. 18 Issue 4, p333
Academic Journal
No abstract available.


Related Articles

  • Automated detection and optimization research on code defects and code smells. LIU Wei; LIU Hong-tao; HU Zhi-gang // Application Research of Computers / Jisuanji Yingyong Yanjiu;Jan2014, Vol. 31 Issue 1, p170 

    To implement automated detection and optimization of code defects and code smells, and to improve the efficiency of code optimization and refactoring, this paper designed and developed a source code optimization and refactoring tool called SCORT. Firstly, SCORT parsed source code to an abstract...

  • Bad Smelling Concept in Software Refactoring. Regulwar, Ganesh B.; Tugnayat, Raju M. // International Proceedings of Economics Development & Research;2012, Vol. 45, p56 

    "This paper discusses refactoring, which is one of the techniques to keep software maintainable. However, refactoring itself will not bring the full benefits, if we do not understand when refactoring needs to be applied. To make it easier for a software developer to decide whether certain...

  • Software Refactoring Process to Accommodate User-Interface Adaptivity in Existing Applications. Savidis, Anthony; Stephanidis, Constantine // Interacting with Computers;Nov2013, Vol. 25 Issue 6, p461 

    Adaptive user-interfaces are capable of: (a) composing themselves at runtime according to a given deployment profile typically encompassing user and usage-context information and (b) possibly dropping user-interface components and activate better alternatives in their place in response to...

  • USING IMPACT ANALYSIS BASED KNOWLEDGE FOR VALIDATING REFACTORING STEPS. Bozó, István; Tóth, Melinda; Tejfel, Máté; Horpácsi, Dániel; Kitlei, Róbert; Kőszegi, Judit; Horváth, Zoltán // Studia Universitatis Babes-Bolyai, Informatica;2011, Vol. 56 Issue 3, p57 

    In the life cycle of a large software product the source code often has to be changed to fit to new requirements, which can be aided by refactorings. In order to minimise the possibility of breaking the functionality of the code, various test suites are used. In this paper, we present a method...

  • An extended assessment of type-3 clones as detected by state-of-the-art tools. Tiarks, Rebecca; Koschke, Rainer; Falke, Raimar // Software Quality Journal;Jun2011, Vol. 19 Issue 2, p295 

    Code reuse through copying and pasting leads to so-called software clones. These clones can be roughly categorized into identical fragments (type-1 clones), fragments with parameter substitution (type-2 clones), and similar fragments that differ through modified, deleted, or added statements...

  • Programmer-Friendly Refactoring Errors. Murphy-Hill, Emerson; Black, Andrew P. // IEEE Transactions on Software Engineering;Nov2012, Vol. 38 Issue 6, p1417 

    Refactoring tools, common to many integrated development environments, can help programmers to restructure their code. These tools sometimes refuse to restructure the programmer's code, instead giving the programmer a textual error message that she must decode if she wishes to understand the...

  • Code Generation.  // Network Dictionary;2007, p105 

    An encyclopedia entry for "Code Generation" is presented. In software development, this term refers to a process by which a compiler converts source codes or computer into a series of machine-executable instructions. Inputs to this process consists of a parse tree, abstract syntax tree, or...

  • What's Good Software, Anyway? Erdogmus, Hakan // IEEE Software;Mar/Apr2007, Vol. 24 Issue 2, p5 

    The article discusses the criteria of a good source code. The software developer must, in the first place, knew how to break the code or understand how it is organized. The software should also be written according to a coding standard to improve its appearance and readability. Its design must...

  • Incremental Maintenance of Software Artifacts. Reiss, Steven P. // IEEE Transactions on Software Engineering;Sep2006, Vol. 32 Issue 9, p682 

    Software is multidimensional, but the tools that support it are not. This lack of tool support causes the software artifacts representing different dimensions to evolve independently and to become inconsistent over time. In order to properly support the evolution of software, one must ensure...


Read the Article


Sorry, but this item is not currently available from your library.

Try another library?
Sign out of this library

Other Topics