Subjective evaluation of software evolvability using code smells: An empirical study
The DOI matches its Crossref record; 70 of the 70 references it cites were found in a registry or an index.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Citations
Cites
Nonparametric Statistics for the Behavioral Sciences
Guitton, H., & Siegel, S. (1958) · Revue économique · doi:10.2307/3498751 · Cited by 35,245
Nonparametric statistics for the behavioral sciences
McGinn, L. C. (1957) · Journal of the Franklin Institute · doi:10.1016/0016-0032(57)90766-4 · Cited by 7,204
McCabe, T. J. (1976) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1976.233837 · Cited by 6,059
A metrics suite for object oriented design
Chidamber, S. R., & Kemerer, C. F. (1994) · IEEE Transactions on Software Engineering · doi:10.1109/32.295895 · Cited by 5,669
Refactoring: Improving the Design of Existing Code
Fowler, M. (2002) · Lecture Notes in Computer Science · doi:10.1007/3-540-45672-4_31 · Cited by 5,591
Manifesto for agile software development
Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., & Thomas, D. A. (2001) · Cited by 4,284
Halstead, M. H. (1977) · CERN Document Server (European Organization for Nuclear Research) · Cited by 3,638
Halstead, M. H. (1977) · CERN Document Server (European Organization for Nuclear Research) · Cited by 2,339
Reverse engineering and design recovery: a taxonomy
Chikofsky, E. J., & Cross, J. H. (1990) · IEEE Software · doi:10.1109/52.43044 · Cited by 2,012
A survey of software refactoring
Mens, T., & Tourwe, T. (2004) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2004.1265817 · Cited by 1,193
Stevens, W. P., Myers, G. J., & Constantine, L. L. (1974) · IBM Systems Journal · doi:10.1147/sj.132.0115 · Cited by 1,185 · cited 1×
“One design principle that has been around for decades is low coupling (Stevens et al., 1974).”
BackgroundObject-oriented metrics that predict maintainability
Li, W., & Henry, S. (1993) · Journal of Systems and Software · doi:10.1016/0164-1212(93)90077-b · Cited by 1,077 · cited 3×
“Although some studies report successes in measuring maintainability with metrics (Bansiya and David, 2002; Chidamber et al., 1998; Coleman et al., 1994; Li and Henry 1993; Subramanyam and Krishnan, 2003), there are people, especially in the agile community (Beck et al.”
BackgroundA hierarchical model for object-oriented design quality assessment
Bansiya, J., & Davis, C. G. (2002) · IEEE Transactions on Software Engineering · doi:10.1109/32.979986 · Cited by 1,020
IEEE Standard Glossary of Software Engineering Terminology
(2008) · doi:10.1109/ieeestd.1990.101064 · Cited by 979
Kendall, M. G., & Smith, B. B. (1939) · The Annals of Mathematical Statistics · doi:10.1214/aoms/1177732186 · Cited by 944
AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis
Brown, W. H., Malveau, R. C., McCormick, H. W., & Mowbray, T. J. (1998) · Cited by 932
A unified framework for coupling measurement in object-oriented systems
Briand, L. C., Daly, J. W., & Wust, J. K. (1999) · IEEE Transactions on Software Engineering · doi:10.1109/32.748920 · Cited by 814 · cited 1×
“Widely studied source code or design metrics (Briand et al., 1997, 1999; Chidamber and Kemerer, 1994; Halstead, 1977; Harrison et al., 1998; Henderson- Sellers, 1996; Hitz and Montazeri, 1996; Lorenz and Kidd, 1994; McCabe, 1976; Succi et al., 2005), which can be gathered using program analysis,…”
BackgroundSoftware Psychology: Human Factors in Computer and Information Systems
Shneiderman, B. (1980) · CERN Document Server (European Organization for Nuclear Research) · Cited by 779
Subramanyam, R., & Krishnan, M. S. (2003) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2003.1191795 · Cited by 672
A hierarchical model for object-oriented design quality assessment
Gupta, N., Goyal, D., & Goyal, M. (2015) · International Journal of Advances in Engineering Sciences (RG Journals of Scientific Research) · Cited by 660
Software Psychology: Human Factors in Computer and Information Systems
Shneiderman, B. (1980) · CERN Document Server (European Organization for Nuclear Research) · Cited by 617
A language independent approach for detecting duplicated code
Ducasse, S., Rieger, M., & Demeyer, S. (1999) · Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360) · doi:10.1109/icsm.1999.792593 · Cited by 615
Detection strategies: metrics-based rules for detecting design flaws
Marinescu, R. (2004) · 20th IEEE International Conference on Software Maintenance, 2004. Proceedings. · doi:10.1109/icsm.2004.1357820 · Cited by 551 · cited 2×
“There also exists a branch of work that has used subjective evolvability by the developers to tune their metrics-based design flaw or code evolvability tools (Marinescu, 2004; Schwanke and Hanson, 1994).”
BackgroundSoftware quality: the elusive target [special issues section]
Kitchenham, B., & Pfleeger, S. L. (1996) · IEEE Software · doi:10.1109/52.476281 · Cited by 545
Managerial use of metrics for object-oriented software: an exploratory analysis
Chidamber, S. R., Darcy, D. P., & Kemerer, C. F. (1998) · IEEE Transactions on Software Engineering · doi:10.1109/32.707698 · Cited by 477 · cited 2×
“Although some studies report successes in measuring maintainability with metrics (Bansiya and David, 2002; Chidamber et al., 1998; Coleman et al., 1994; Li and Henry 1993; Subramanyam and Krishnan, 2003), there are people, especially in the agile community (Beck et al.”
BackgroundMethodUsing metrics to evaluate software system maintainability
Coleman, D., Ash, D., Lowther, B., & Oman, P. (1994) · Computer · doi:10.1109/2.303623 · Cited by 431 · cited 5×
“Some work in this area has been done by Oman et al. (1991), 2 who listed different factors affecting software evolvability.”
BackgroundMethodInfluentialOn understanding laws, evolution, and conservation in the large-program life cycle
Lehman, M. M. (1979) · Journal of Systems and Software · doi:10.1016/0164-1212(79)90022-0 · Cited by 377 · cited 1×
“Lehman (Lehman, 1980) has proposed laws that affect software evolution, some of which also affect software evolvability.”
BackgroundPractical Software Maintenance: Best Practices for Managing Your Software Investment
Pigoski, T. M. (1996) · Medical Entomology and Zoology · Cited by 374
Principles of survey research: part 1: turning lemons into lemonade
Pfleeger, S. L., & Kitchenham, B. A. (2001) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/505532.505535 · Cited by 373 · cited 2×
“Although we tried to make our study as reliable as possible, for example by using the instructions presented by Pfleeger and Kitchenham (Kitchenham and Pfleeger, 2002a,b,c,d; Pfleeger and Kitchenham, 2001 ), the study still has many limitations we must address.”
MethodAn evaluation of the MOOD set of object-oriented software metrics
Harrison, R., Counsell, S. J., & Nithi, R. V. (1998) · IEEE Transactions on Software Engineering · doi:10.1109/32.689404 · Cited by 359
Principles of survey research: part 5: populations and samples
Kitchenham, B., & Pfleeger, S. L. (2002) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/571681.571686 · Cited by 329 · cited 1×
“Although we tried to make our study as reliable as possible, for example by using the instructions presented by Pfleeger and Kitchenham (Kitchenham and Pfleeger, 2002a,b,c,d; Pfleeger and Kitchenham, 2001), the study still has many limitations we must address.”
MethodObject-Oriented Software Metrics
Polgar, J. (2005) · IGI Global eBooks · doi:10.4018/978-1-59140-553-5.ch379 · Cited by 318 · cited 5×
“We can accept slightly larger GUI classes than regular classes and we might be willing to accept that a GUI class can be up to three times larger in terms of variables than a model class as suggested by Lorenz and Kidd (1994).”
BackgroundMethodInfluentialA unified framework for cohesion measurement in object-oriented systems
Briand, L., Daly, J. W., & Wüst, J. (1997) · IEEE International Software Metrics Symposium (METRICS) · doi:10.1109/metric.1997.637164 · Cited by 299
Principles of survey research part 4: questionnaire evaluation
Kitchenham, B. A., & Pfleeger, S. L. (2002) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/638574.638580 · Cited by 288 · cited 1×
“Although we tried to make our study as reliable as possible, for example by using the instructions presented by Pfleeger and Kitchenham (Kitchenham and Pfleeger, 2002a,b,c,d; Pfleeger and Kitchenham, 2001), the study still has many limitations we must address.”
MethodSimon, F., Steinbruckner, F., & Lewerentz, C. (2002) · Proceedings Fifth European Conference on Software Maintenance and Reengineering · doi:10.1109/.2001.914965 · Cited by 275 · cited 2×
“, (Balazinska et al., 2000; Ducasse et al., 1999; Kataoka et al., 2001; Simon et al., 2001; Tourwé and Mens, 2003) have focused on automatically detecting poor structures in software or using historical data to detect spots where refactorings have been performed (Maruyama and Shima, 1999).”
MethodHow effective developers investigate source code: an exploratory study
Robillard, M. P., Coelho, W., & Murphy, G. C. (2004) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2004.101 · Cited by 260 · cited 1×
“3 A recent study ( Robillard et al., 2004 ) of program modification tasks also showed that”
BackgroundA staged model for the software life cycle
Rajlich, V. T., & Bennett, K. H. (2000) · Computer · doi:10.1109/2.869374 · Cited by 241 · cited 2×
“Rajlich and Bennett (2000) propose an improvement to the traditional develop and maintain model by presenting a life cycle model that also describes the phases after the software has been released.”
BackgroundPrinciples of survey research part 2: designing a survey
Kitchenham, B. A., & Pfleeger, S. L. (2002) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/566493.566495 · Cited by 231 · cited 2×
“Although we tried to make our study as reliable as possible, for example by using the instructions presented by Pfleeger and Kitchenham ( Kitchenham and Pfleeger, 2002a, b,c,d; Pfleeger and Kitchenham, 2001), the study still has many limitations we must address.”
MethodThe Use of Software Complexity Metrics in Software Maintenance
Kafura, D., & Reddy, G. R. (1987) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1987.233164 · Cited by 213 · cited 2×
“In related work, Kafura and Reddy (1987) concluded that the expert evaluations on maintainability were in conformance with the complexity source code metric used to measure the maintainability, but there are three differences compared to our study.”
BackgroundResultA taxonomy and an initial empirical study of bad smells in code
Mantyla, M., Vanhanen, J., & Lassenius, C. (2004) · International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings. · doi:10.1109/icsm.2003.1235447 · Cited by 211 · cited 1×
“The taxonomy is an improved version of our previous taxonomy that was presented in (Mäntylä et al., 2003).”
MethodSelf-citationChidamber and Kemerer's metrics suite: a measurement theory perspective
Hitz, M., & Montazeri, B. (1996) · IEEE Transactions on Software Engineering · doi:10.1109/32.491650 · Cited by 207 · cited 2×
“Widely studied object-oriented metrics (Briand et al., 1997, 1999; Chidamber and Kemerer, 1994; Harrison et al., 1998; Henderson-Sellers, 1996; Hitz and Montazeri, 1996; Lorenz and Kidd, 1994) offer a way to assess software maintainability.”
BackgroundAutomated support for program refactoring using invariants
Kataoka, Y., Ernst, M. D., Griswold, W. G., & Notkin, D. S. (2002) · IEEE International Conference on Software Maintenance (ICSM) · doi:10.1109/icsm.2001.972794 · Cited by 194 · cited 2×
“Recent studies, e.g., (Balazinska et al., 2000; Ducasse et al., 1999; Kataoka et al., 2001; Simon et al., 2001; Tourwé and Mens, 2003) have focused on automatically detecting poor structures in software or using historical data to detect spots where refactorings have been performed (Maruyama and…”
MethodPrinciples of survey research: part 3: constructing a survey instrument
Kitchenham, B. A., & Pfleeger, S. L. (2002) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/511152.511155 · Cited by 186 · cited 1×
“Although we tried to make our study as reliable as possible, for example by using the instructions presented by Pfleeger and Kitchenham (Kitchenham and Pfleeger, 2002a,b,c,d; Pfleeger and Kitchenham, 2001), the study still has many limitations we must address.”
MethodConstruction and testing of polynomials predicting software maintainability
Oman, P., & Hagemeister, J. (1994) · Journal of Systems and Software · doi:10.1016/0164-1212(94)90067-1 · Cited by 183 · cited 5×
“Oman et al. (Coleman et al., 1994, 1995; Oman and Hagemeister, 1994; Welker et al., 1997) report on the construction of a maintainability index.”
BackgroundMethodInfluentialAdvanced clone-analysis to support object-oriented system refactoring
Balazinska, M., Merlo, E., Dagenais, M., Lague, B., & Kontogiannis, K. (2002) · Proceedings Seventh Working Conference on Reverse Engineering · doi:10.1109/wcre.2000.891457 · Cited by 178 · cited 2×
“Recent studies, e.g., (Balazinska et al., 2000; Ducasse et al., 1999; Kataoka et al., 2001; Simon et al., 2001; Tourwé and Mens, 2003) have focused on automatically detecting poor structures in software or using historical data to detect spots where refactorings have been performed (Maruyama and…”
MethodTurning Lemons into Lemonade: Where Is the Value in Peer Reviews?
Starbuck, W. H. (2003) · Journal of Management Inquiry · doi:10.1177/1056492603258972 · Cited by 175
A quantitative evaluation of maintainability enhancement by refactoring
Kataoka, Y., Imai, T., Andou, H., & Fukaya, T. (2003) · International Conference on Software Maintenance, 2002. Proceedings. · doi:10.1109/icsm.2002.1167822 · Cited by 172 · cited 6×
“Kataoka et al. (2002) report that experts' subjective evaluations on the effectiveness of refactorings correlated quite well with improvement in coupling metrics.”
BackgroundInfluentialPredicting maintenance performance using object-oriented design complexity metrics
Bandi, R. K., Vaishnavi, V. K., & Turk, D. E. (2003) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2003.1166590 · Cited by 165 · cited 1×
“Several well-constructed studies (Bandi et al., 2003; Li and Henry, 1993; Rombach, 1987) show that using source code metrics for evolvability evaluation can predict the future development effort.”
BackgroundPractical Software Maintenance
Seaman, C. B. (2000) · Journal of Software Maintenance Research and Practice · doi:10.1002/1096-908x(200007/08)12:4<249::aid-smr213>3.0.co;2-n · Cited by 163
A Controlled Expeniment on the Impact of Software Structure on Maintainability
Rombach, H. D. (1987) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1987.233165 · Cited by 153 · cited 1×
“Several well-constructed studies (Bandi et al., 2003; Li and Henry, 1993; Rombach, 1987) show that using source code metrics for evolvability evaluation can predict the future development effort.”
BackgroundIdentifying refactoring opportunities using logic meta programming
Tourwé, T., & Mens, T. (2003) · Euromicro Conference on Software Maintenance and Reengineering (CSMR) · doi:10.1109/csmr.2003.1192416 · Cited by 150 · cited 2×
“, (Balazinska et al., 2000; Ducasse et al., 1999; Kataoka et al., 2001; Simon et al., 2001; Tourwé and Mens, 2003) have focused on automatically detecting poor structures in software or using historical data to detect spots where refactorings have been performed (Maruyama and Shima, 1999).”
MethodSuccessfully applying software metrics
Grady, R. B. (1994) · Computer · doi:10.1109/2.312034 · Cited by 112
The application of software maintainability models in industrial software systems
Coleman, D., Lowther, B., & Oman, P. (1995) · Journal of Systems and Software · doi:10.1016/0164-1212(94)00125-7 · Cited by 110 · cited 4×
“Firstly, Oman et al., measured the high-level concept of maintainability whereas we measured more exact code smells.”
BackgroundMethodInfluentialWake, W. C. (2003) · CERN Document Server (European Organization for Nuclear Research) · Cited by 97
McDavid, D., Zamir, S., Moser, S., & Henderson‐Sellers, B. (1998) · CRC Press eBooks · doi:10.1201/9780849331350.sec9 · Cited by 96
A maintainability model for industrial software systems using design level metrics
Muthanna, S., Kontogiannis, K. A., Ponnambalam, K., & Stacey, B. (2002) · Working Conference on Reverse Engineering (WCRE) · doi:10.1109/wcre.2000.891476 · Cited by 85 · cited 2×
“Code metrics have been combined to create polynomial equations whose outcomes give a single measure of evolvability (Coleman et al., 1994; Muthanna et al., 2000).”
BackgroundArnold, R. S. (1989) · Proceedings of the IEEE · doi:10.1109/5.24146 · Cited by 82
Succi, G., Witold Pedrycz, C., Djokic, S., Zuliani, P., & Russo, B. (2004) · Empirical Software Engineering · doi:10.1023/b:emse.0000048324.12188.a2 · Cited by 76 · cited 2×
“…Chidamber and Kemerer, 1994; Halstead, 1977; Harrison et al., 1998; Henderson- Sellers, 1996; Hitz and Montazeri, 1996; Lorenz and Kidd, 1994; McCabe, 1976; Succi et al., 2005), which can be gathered using program analysis, have traditionally played a big role in evaluating software evolvability.”
BackgroundDevelopment and Application of an Automated Source Code Maintainability Index
Welker, K. D., Oman, P., & Atkinson, G. G. (1997) · Journal of Software Maintenance Research and Practice · doi:10.1002/(sici)1096-908x(199705)9:3<127::aid-smr149>3.0.co;2-s · Cited by 73
Design metrics: an empirical analysis
Shepperd, M. (1990) · Software Engineering Journal · doi:10.1049/sej.1990.0002 · Cited by 65
A Unified Framework for Cohesion Measurement
Briand, L., Daly, J. W., & Wuest, J. R. (1997) · Cited by 60
Using Neural Networks to Modularize Software
Schwanke, R. W., & Hanson, S. J. (1994) · Machine Learning · doi:10.1023/a:1022669305303 · Cited by 51 · cited 2×
“There also exists a branch of work that has used subjective evolvability by the developers to tune their metrics-based design flaw or code evolvability tools (Marinescu, 2004; Schwanke and Hanson, 1994).”
BackgroundObject-oriented metrics: an annotated bibliography
Whitty, R. W. (1996) · ACM SIGPLAN Notices · doi:10.1145/249118.249128 · Cited by 43
Automatic method refactoring using weighted dependence graphs
Maruyama, K., & Shima, K.-I. (1999) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/302405.302627 · Cited by 33 · cited 2×
“, 2001; Tourwé and Mens, 2003) have focused on automatically detecting poor structures in software or using historical data to detect spots where refactorings have been performed (Maruyama and Shima, 1999).”
BackgroundMethodIEEE Standard for Software Maintenance
(1992) · IEEE Standards · doi:10.1109/ieeestd.1993.115570 · Cited by 18
System architecture metrics for controlling software maintainability
Shepperd, M. (1990) · Cited by 7
Experimental analysis of the cognitive processes of program maintainers during software maintenance
Iio, K., Furuyama, T., & Arai, Y. (1997) · International Conference on Software Maintenance · doi:10.1109/icsm.1997.624251 · Cited by 6 · cited 2×
“Related work on the differences between novice and expert coders exists, but these studies have mainly focused on the cognitive process and improving the novices' performance, e.g. (Iio et al., 1997; Yu et al., 1994).”
BackgroundBandi, R. K., Vaishnavi, V. K., & Turk, D. (2003) · Cited by 6
Johnson, S. K. (1988) · Defense Technical Information Center (DTIC) · Cited by 5
Helping novice programmers bridge the conceptual gap
He, Y., Ikeda, M., & Mizoguchi, R. (2002) · International Conference on Expert Systems for Development · doi:10.1109/icesd.1994.302282 · Cited by 4 · cited 1×
“Related work on the differences between novice and expert coders exists, but these studies have mainly focused on the cognitive process and improving the novices' performance, e.g. (Iio et al., 1997; Yu et al., 1994).”
Background
Research works printed but not linked: 8
- Cusumano MA, Selby RW (1995) Microsoft secrets. Free Press, USA
- Cusumano MA, Yoffie DB (1998) Design strategy. In: Competing on internet time. Free Press, New York, USA, pp 180–198
- Fowler M, Beck K (2000) Bad smells in code. In: Refactoring: improving the design of existing code, 1st edn. Addison-Wesley, Boston, pp 75–88
- Garvin DA (1984) What does “product quality” really mean? Sloan Manage Rev 26:25–43
- Kitchenham BA, Pfleeger SL (2002d) Principles of survey research: part 5: populations and samples. ACM SIGSOFT Softw Eng Notes 27:17–20 · DOI · Paper page
- McConnell S (1993) Code complete. Microsoft, Redmond, Washington
- Sommerville I (2001) Software engineering. Addison-Wesley, Reading, Massachusetts
- Szulewski PA, Budlong FC (1996) Metrics for ada 95: focus on reliability and maintainability. CrossTalk—The Journal of Defence Software Engineering 1996
Cited by
Comparing and experimenting machine learning techniques for code smell detection
Arcelli Fontana, F., Mäntylä, M. V., Zanoni, M., & Marino, A. (2016) · Empirical Software Engineering · doi:10.1007/s10664-015-9378-4 · Cited by 450
“In fact, code smells can be subjectively interpreted (Mäntylä and Lassenius 2006), the results provided by detectors are usually different (Arcelli Fontana et al.”
BackgroundSelf-citationDetecting code smells using machine learning techniques: Are we there yet?
Di Nucci, D., Palomba, F., Tamburri, D. A., Serebrenik, A., & De Lucia, A. (2018) · 2018 IEEE 25th International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner.2018.8330266 · Cited by 305
“In the first place, code smells detected by existing approaches can be subjectively perceived and interpreted by developers [30], [31].”
BackgroundAzeem, M. I., Palomba, F., Shi, L., & Wang, Q. (2019) · Information and Software Technology · doi:10.1016/j.infsof.2018.12.009 · Cited by 289
“Only a small amount of works (20%) focused on the problem of code smell prioritization: as the intensity of code smells represents one of the key aspects when scheduling refactoring operations [31] and given the great potential that machine learning has in mitigating the subjectiveness with which code smells are inter…”
BackgroundSharma, T., & Spinellis, D. (2018) · Journal of Systems and Software · doi:10.1016/j.jss.2017.12.034 · Cited by 251
“• Many authors have asserted that smell detection is a subjective process [73, 96, 84].”
BackgroundOlbrich, S. M., Cruzes, D. S., & Sjoberg, D. I. K. (2010) · 2010 IEEE International Conference on Software Maintenance · doi:10.1109/icsm.2010.5609564 · Cited by 236
“The performance of different automated detection heuristics have been compared with manual approaches in various studies [6], [9], [13], [14], [15], [17], [21].”
BackgroundMethod
Metadata
- Authors
- Mäntylä, M. V., & Lassenius, C.
- Corresponding author
- Mäntylä, Mika V.
- Lassenius, Casper
- Venue
- Empirical Software Engineering
- Published
- 2006-05-27
- Volume
- 11
- Issue
- 3
- Pages
- 395-431
- ISSN
- 1382-3256 (ISSN-L)
- 1573-7616
- OpenAlex
- W1963598945
- Cited by
- 171
- References
- 70
- Citations by year
- 2026: 2 · 2025: 4 · 2024: 8 · 2023: 10 · 2022: 6 · 2021: 16 · 2020: 9 · 2019: 17 · 2018: 10 · 2017: 19 · 2016: 7 · 2015: 8 · 2014: 14 · 2013: 12 · 2012: 7
- FWCI
- 5.94
- Type
- journal article
- Language
- en
- Open access
- closed
- Licence
- www.springer.com/tdm (tdm)
- Locations
- Empirical Software Engineering (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
- Keywords
- software evolvability, code smells, subjective evaluation, source code metrics, automatic program analysis, software maintainability
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.