Subjective Evaluation of Software Evolvability Using Code Smells: An Empirical Study. Mäntylä, M. V. & Lassenius, C. 11(3):395–431. ![Subjective Evaluation of Software Evolvability Using Code Smells: An Empirical Study [link]](https://bibbase.org/img/filetypes/link.svg "link")
Paper doi abstract bibtex This paper presents the results of an empirical study on the subjective evaluation of code smells that identify poorly evolvable structures in software. We propose use of the term software evolvability to describe the ease of further developing a piece of software and outline the research area based on four different viewpoints. Furthermore, we describe the differences between human evaluations and automatic program analysis based on software evolvability metrics. The empirical component is based on a case study in a Finnish software product company, in which we studied two topics. First, we looked at the effect of the evaluator when subjectively evaluating the existence of smells in code modules. We found that the use of smells for code evaluation purposes can be difficult due to conflicting perceptions of different evaluators. However, the demographics of the evaluators partly explain the variation. Second, we applied selected source code metrics for identifying four smells and compared these results to the subjective evaluations. The metrics based on automatic program analysis and the human-based smell evaluations did not fully correlate. Based upon our results, we suggest that organizations should make decisions regarding software evolvability improvement based on a combination of subjective evaluations and code metrics. Due to the limitations of the study we also recognize the need for conducting more refined studies and experiments in the area of software evolvability.
@article{mantylaSubjectiveEvaluationSoftware2006,
title = {Subjective Evaluation of Software Evolvability Using Code Smells: An Empirical Study},
author = {Mäntylä, Mika V. and Lassenius, Casper},
date = {2006-09},
journaltitle = {Empirical Software Engineering},
volume = {11},
pages = {395--431},
issn = {1382-3256},
doi = {10.1007/s10664-006-9002-8},
url = {https://doi.org/10.1007/s10664-006-9002-8},
abstract = {This paper presents the results of an empirical study on the subjective evaluation of code smells that identify poorly evolvable structures in software. We propose use of the term software evolvability to describe the ease of further developing a piece of software and outline the research area based on four different viewpoints. Furthermore, we describe the differences between human evaluations and automatic program analysis based on software evolvability metrics. The empirical component is based on a case study in a Finnish software product company, in which we studied two topics. First, we looked at the effect of the evaluator when subjectively evaluating the existence of smells in code modules. We found that the use of smells for code evaluation purposes can be difficult due to conflicting perceptions of different evaluators. However, the demographics of the evaluators partly explain the variation. Second, we applied selected source code metrics for identifying four smells and compared these results to the subjective evaluations. The metrics based on automatic program analysis and the human-based smell evaluations did not fully correlate. Based upon our results, we suggest that organizations should make decisions regarding software evolvability improvement based on a combination of subjective evaluations and code metrics. Due to the limitations of the study we also recognize the need for conducting more refined studies and experiments in the area of software evolvability.},
keywords = {*imported-from-citeulike-INRMM,~INRMM-MiD:c-6335663,antipattern,software-engineering,software-errors,software-evolvability},
number = {3}
}
Downloads: 0
{"_id":"mTCtQH8ms9RWkDrzw","bibbaseid":"mntyl-lassenius-subjectiveevaluationofsoftwareevolvabilityusingcodesmellsanempiricalstudy","authorIDs":[],"author_short":["Mäntylä, M. V.","Lassenius, C."],"bibdata":{"bibtype":"article","type":"article","title":"Subjective Evaluation of Software Evolvability Using Code Smells: An Empirical Study","author":[{"propositions":[],"lastnames":["Mäntylä"],"firstnames":["Mika","V."],"suffixes":[]},{"propositions":[],"lastnames":["Lassenius"],"firstnames":["Casper"],"suffixes":[]}],"date":"2006-09","journaltitle":"Empirical Software Engineering","volume":"11","pages":"395–431","issn":"1382-3256","doi":"10.1007/s10664-006-9002-8","url":"https://doi.org/10.1007/s10664-006-9002-8","abstract":"This paper presents the results of an empirical study on the subjective evaluation of code smells that identify poorly evolvable structures in software. We propose use of the term software evolvability to describe the ease of further developing a piece of software and outline the research area based on four different viewpoints. Furthermore, we describe the differences between human evaluations and automatic program analysis based on software evolvability metrics. The empirical component is based on a case study in a Finnish software product company, in which we studied two topics. First, we looked at the effect of the evaluator when subjectively evaluating the existence of smells in code modules. We found that the use of smells for code evaluation purposes can be difficult due to conflicting perceptions of different evaluators. However, the demographics of the evaluators partly explain the variation. Second, we applied selected source code metrics for identifying four smells and compared these results to the subjective evaluations. The metrics based on automatic program analysis and the human-based smell evaluations did not fully correlate. Based upon our results, we suggest that organizations should make decisions regarding software evolvability improvement based on a combination of subjective evaluations and code metrics. Due to the limitations of the study we also recognize the need for conducting more refined studies and experiments in the area of software evolvability.","keywords":"*imported-from-citeulike-INRMM,~INRMM-MiD:c-6335663,antipattern,software-engineering,software-errors,software-evolvability","number":"3","bibtex":"@article{mantylaSubjectiveEvaluationSoftware2006,\n title = {Subjective Evaluation of Software Evolvability Using Code Smells: An Empirical Study},\n author = {Mäntylä, Mika V. and Lassenius, Casper},\n date = {2006-09},\n journaltitle = {Empirical Software Engineering},\n volume = {11},\n pages = {395--431},\n issn = {1382-3256},\n doi = {10.1007/s10664-006-9002-8},\n url = {https://doi.org/10.1007/s10664-006-9002-8},\n abstract = {This paper presents the results of an empirical study on the subjective evaluation of code smells that identify poorly evolvable structures in software. We propose use of the term software evolvability to describe the ease of further developing a piece of software and outline the research area based on four different viewpoints. Furthermore, we describe the differences between human evaluations and automatic program analysis based on software evolvability metrics. The empirical component is based on a case study in a Finnish software product company, in which we studied two topics. First, we looked at the effect of the evaluator when subjectively evaluating the existence of smells in code modules. We found that the use of smells for code evaluation purposes can be difficult due to conflicting perceptions of different evaluators. However, the demographics of the evaluators partly explain the variation. Second, we applied selected source code metrics for identifying four smells and compared these results to the subjective evaluations. The metrics based on automatic program analysis and the human-based smell evaluations did not fully correlate. Based upon our results, we suggest that organizations should make decisions regarding software evolvability improvement based on a combination of subjective evaluations and code metrics. Due to the limitations of the study we also recognize the need for conducting more refined studies and experiments in the area of software evolvability.},\n keywords = {*imported-from-citeulike-INRMM,~INRMM-MiD:c-6335663,antipattern,software-engineering,software-errors,software-evolvability},\n number = {3}\n}\n\n","author_short":["Mäntylä, M. V.","Lassenius, C."],"key":"mantylaSubjectiveEvaluationSoftware2006","id":"mantylaSubjectiveEvaluationSoftware2006","bibbaseid":"mntyl-lassenius-subjectiveevaluationofsoftwareevolvabilityusingcodesmellsanempiricalstudy","role":"author","urls":{"Paper":"https://doi.org/10.1007/s10664-006-9002-8"},"keyword":["*imported-from-citeulike-INRMM","~INRMM-MiD:c-6335663","antipattern","software-engineering","software-errors","software-evolvability"],"downloads":0},"bibtype":"article","biburl":"https://tmpfiles.org/dl/58794/INRMM.bib","creationDate":"2020-07-02T22:41:13.616Z","downloads":0,"keywords":["*imported-from-citeulike-inrmm","~inrmm-mid:c-6335663","antipattern","software-engineering","software-errors","software-evolvability"],"search_terms":["subjective","evaluation","software","evolvability","using","code","smells","empirical","study","mäntylä","lassenius"],"title":"Subjective Evaluation of Software Evolvability Using Code Smells: An Empirical Study","year":null,"dataSources":["DXuKbcZTirdigFKPF"]}