The DOI matches its Crossref record; 30 of the 30 references it cites were found in a registry or an index.
An Empirical Study of the Impact of Two Antipatterns, Blob and Spaghetti Code, on Program Comprehension
Abstract
Antipatterns are "poor" solutions to recurring design problems which are conjectured in the literature to make object-oriented systems harder to maintain. However, little quantitative evidence exists to support this conjecture. We performed an empirical study to investigate whether the occurrence of antipatterns does indeed affect the understandability of systems by developers during comprehension and maintenance tasks. We designed and conducted three experiments, with 24 subjects each, to collect data on the performance of developers on basic tasks related to program comprehension and assessed the impact of two antipatterns and of their combinations: Blob and Spaghetti Code. We measured the developers' performance with: (1) the NASA task load index for their effort, (2) the time that they spent performing their tasks, and, (3) their percentages of correct answers. Collected data show that the occurrence of one antipattern does not significantly decrease developers' performance while the combination of two antipatterns impedes significantly developers. We conclude that developers can cope with one antipattern but that combinations of antipatterns should be avoided possibly through detection and refactorings.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Development of NASA-TLX (Task Load Index): Results of Empirical and Theoretical Research
(1988) · Advances in Psychology · doi:10.1016/s0166-4115(08)62386-9 · Cited by 15,003
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
Eye Tracking Methodology: Theory and Practice
Duchowski, A. T. (2003) · Springer eBooks · doi:10.1007/978-1-4471-3750-4 · Cited by 2,242
Experimentation in Software Engineering: An Introduction
Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., & Wesslén, A. (2011) · Lund University Publications (Lund University) · Cited by 2,214
Refactoring improving the design of existing code
Saca, M. A. (2017) · 2017 IEEE 37th Central America and Panama Convention (CONCAPAN XXXVII) · doi:10.1109/concapan.2017.8278488 · Cited by 2,054
Experimentation in Software Engineering
Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., & Wesslén, A. (2000) · The Kluwer International Series in Software Engineering · doi:10.1007/978-1-4615-4625-2 · Cited by 1,776
Eye Tracking Methodology; Theory and Practice
(2007) · Qualitative Market Research: An International Journal · doi:10.1108/13522750710740862 · Cited by 1,313
AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis
Brown, W. H., Malveau, R. C., McCormick, H. W., & Mowbray, T. J. (1998) · Cited by 932
DECOR: A Method for the Specification and Detection of Code and Design Smells
Moha, N., Gueheneuc, Y.-G., Duchien, L., & Le Meur, A.-F. (2010) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2009.50 · Cited by 803
Self-citationParnas, D. L. (1994) · doi:10.5555/257734.257788 · Cited by 655
Program comprehension during software maintenance and evolution
Von Mayrhauser, A., & Vans, A. M. (1995) · Computer · doi:10.1109/2.402076 · Cited by 575
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
Object-oriented design heuristics
Riel, A. J. (1996) · Cited by 546
Parnas, D. L. (2002) · Proceedings of 16th International Conference on Software Engineering · doi:10.1109/icse.1994.296790 · Cited by 369
Asking and Answering Questions during a Programming Change Task
Sillito, J., Murphy, G. C., & De Volder, K. (2008) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2008.26 · Cited by 319
An Exploratory Study of the Impact of Code Smells on Software Change-proneness
Khomh, F., Di Penta, M., & Gueheneuc, Y.-G. (2009) · 2009 16th Working Conference on Reverse Engineering · doi:10.1109/wcre.2009.28 · Cited by 306
Self-citationOrganizational Patterns of Agile Software Development
Coplien, J. O., & Harrison, N. B. (2004) · Cited by 282
The evolution and impact of code smells: A case study of two open source systems
Olbrich, S., Cruzes, D. S., Basili, V., & Zazworka, N. (2009) · 2009 3rd International Symposium on Empirical Software Engineering and Measurement · doi:10.1109/esem.2009.5314231 · Cited by 245
A Bayesian Approach for the Detection of Code and Design Smells
Khomh, F., Vaucher, S., Guéhéneuc, Y.-G., & Sahraoui, H. (2009) · 2009 Ninth International Conference on Quality Software · doi:10.1109/qsic.2009.47 · Cited by 224
Self-citationComparative Power of Student T Test and Mann-Whitney U Test for Unequal Sample Sizes and Variances
Zimmerman, D. W. (1987) · The Journal of Experimental Education · doi:10.1080/00220973.1987.10806451 · Cited by 195
Product Metrics for Automatic Identification of "Bad Smell" Design Problems in Java Source-Code
Munro, M. J. (2005) · 11th IEEE International Software Metrics Symposium (METRICS'05) · doi:10.1109/metrics.2005.38 · Cited by 191
Handbook of Parametric and Nonparametric Statistical Procedures: Third Edition
Sheskin, D. J. (2000) · Cited by 165
Wu, W., Guéhéneuc, Y., Antoniol, G., & Kim, M. (2010) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/1806799.1806848 · Cited by 156
Self-citationInvestigating the Evolution of Bad Smells in Object-Oriented Code
Chatzigeorgiou, A., & Manakos, A. (2010) · International Conference on the Quality of Information and Communications Technology (QUATIC) · doi:10.1109/quatic.2010.16 · Cited by 148
On the Impact of Design Flaws on Software Defects
D’Ambros, M., Bacchelli, A., & Lanza, M. (2010) · Asia-Pacific Conference on Quality Software (APAQS) · doi:10.1109/qsic.2010.58 · Cited by 141
Hart, S. G. (1986) · NASA Technical Reports Server (NASA) · Cited by 132
Wake, W. C. (2003) · CERN Document Server (European Organization for Nuclear Research) · Cited by 97
An empirical investigation of an object-oriented design heuristic for maintainability
Deligiannis, I., Shepperd, M., Roumeliotis, Μ., & Stamelos, I. G. (2003) · Journal of Systems and Software · doi:10.1016/s0164-1212(02)00054-7 · Cited by 76
A controlled experiment investigation of an object-oriented design heuristic for maintainability
Deligiannis, I., Stamelos, I. G., Angelis, L., Roumeliotis, Μ., & Shepperd, M. (2003) · Journal of Systems and Software · doi:10.1016/s0164-1212(03)00240-1 · Cited by 74
Porras, G. C., & Guéhéneuc, Y. (2010) · Empirical Software Engineering · doi:10.1007/s10664-009-9125-9 · Cited by 60
Cited by
Quantifying the Effect of Code Smells on Maintenance Effort
Sjoberg, D. I. K., Yamashita, A., Anda, B. C. D., Mockus, A., & Dyba, T. (2013) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2012.89 · Cited by 316
Palomba, F., Bavota, G., Penta, M. D., Fasano, F., Oliveto, R., & Lucia, A. D. (2018) · Empirical Software Engineering · doi:10.1007/s10664-017-9535-z · Cited by 305
Detecting 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
Azeem, M. I., Palomba, F., Shi, L., & Wang, Q. (2019) · Information and Software Technology · doi:10.1016/j.infsof.2018.12.009 · Cited by 289
Evolution of software in automated production systems: Challenges and research directions
Vogel-Heuser, B., Fay, A., Schaefer, I., & Tichy, M. (2015) · Journal of Systems and Software · doi:10.1016/j.jss.2015.08.026 · Cited by 289
Metadata
- Authors
- Abbes, M., Khomh, F., Gueheneuc, Y.-G., & Antoniol, G.
- Venue
- 2011 15th European Conference on Software Maintenance and Reengineering
- Publisher
- IEEE
- Published
- 2011-03
- Pages
- 181-190
- ISSN
- 1534-5351 (ISSN-L)
- OpenAlex
- W2108086273
- Cited by
- 309
- References
- 30
- FWCI
- 10.82
- Type
- conference paper
- Language
- en
- Open access
- closed
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.