The DOI matches its Crossref record; 13 of the 13 references it cites were found in a registry or an index.
CVS release history data for detecting logical couplings
Abstract
The dependencies and interrelations between classes and modules affect the maintainability of object-oriented systems. It is therefore important to capture weaknesses of the software architecture to make necessary corrections. We describe a method for software evolution analysis. It consists of three complementary steps, which form an integrated approach for the reasoning about software structures based on historical data: 1) the quantitative analysis uses version information for the assessment of growth and change behavior; 2) the change sequence analysis identifies common change patterns across all system parts; and 3) the relation analysis compares classes based on CVS release history data and reveals the dependencies within the evolution of particular entities. We focus on the relation analysis and discuss its results; it has been validated based on empirical data collected from a concurrent versions system (CVS) covering 28 months of a picture archiving and communication system (PACS). Our software evolution analysis approach enabled us to detect shortcomings of PACS such as architectural weaknesses, poorly designed inheritance hierarchies, or blurred interfaces of modules.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
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
Software Metrics: A Rigorous and Practical Approach
Fenton, N., & Pfleeger, S. L. (2013) · Cited by 2,509
Programs, life cycles, and laws of software evolution
Lehman, M. M. (1980) · Proceedings of the IEEE · doi:10.1109/proc.1980.11805 · Cited by 1,181
Populating a Release History Database from version control and bug tracking systems
Fischer, M., Pinzger, M., & Gall, H. (2004) · International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings. · doi:10.1109/icsm.2003.1235403 · Cited by 525
Self-citationDetection of logical coupling based on product release history
Gall, H., Hajek, K., & Jazayeri, M. (2002) · Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272) · doi:10.1109/icsm.1998.738508 · Cited by 447
Self-citationPredicting fault-prone software modules in telephone switches
Ohlsson, N., & Alberg, H. (1996) · IEEE Transactions on Software Engineering · doi:10.1109/32.553637 · Cited by 346
Hipikat: recommending pertinent software development artifacts
Čubranić, D., & Murphy, G. C. (2003) · doi:10.5555/776816.776866 · Cited by 317
Open Source Development with CVS
Bar, M., & Fogel, K. (1999) · Medical Entomology and Zoology · Cited by 192
Hipikat: recommending pertinent software development artifacts
Cubranic, D., & Murphy, G. C. (2003) · 25th International Conference on Software Engineering, 2003. Proceedings. · doi:10.1109/icse.2003.1201219 · Cited by 174
Software evolution observations based on product release history
Gall, H. C., Jazayeri, M., KLÖSCH, R. R., & Trausmuth, G. (1997) · International Conference on Software Maintenance · doi:10.1109/icsm.1997.624242 · Cited by 150
Self-citationEick, S. G., Graves, T., Karr, A. F., Mockus, A., & Schuster, P. (2002) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2002.995435 · Cited by 135
Cited by
Mining version histories to guide software changes
Zimmermann, T., Zeller, A., Weissgerber, P., & Diehl, S. (2005) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2005.72 · Cited by 856
Moser, R., Pedrycz, W., & Succi, G. (2008) · Proceedings of the 13th international conference on Software engineering - ICSE '08 · doi:10.1145/1368088.1368114 · Cited by 701
Predicting Faults from Cached History
Kim, S., Zimmermann, T., Whitehead Jr., E. J., & Zeller, A. (2007) · 29th International Conference on Software Engineering (ICSE'07) · doi:10.1109/icse.2007.66 · Cited by 486
Kagdi, H., Collard, M. L., & Maletic, J. I. (2007) · Journal of Software Maintenance and Evolution: Research and Practice · doi:10.1002/smr.344 · Cited by 413
Lucia, A. D., Fasano, F., Oliveto, R., & Tortora, G. (2007) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/1276933.1276934 · Cited by 354
DynaMine: finding common error patterns by mining software revision histories
Livshits, B., & Zimmermann, T. (2005) · Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering · doi:10.1145/1081706.1081754 · Cited by 330
Hipikat: a project memory for software development
Cubranic, D., Murphy, G. C., Singer, J., & Booth, K. S. (2005) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2005.71 · Cited by 324
Mining version histories to guide software changes
Zimmermann, T., Weibgerber, P., Diehl, S., & Zeller, A. (2004) · Proceedings. 26th International Conference on Software Engineering · doi:10.1109/icse.2004.1317478 · Cited by 322
Extraction of Microservices from Monolithic Software Architectures
Mazlami, G., Cito, J., & Leitner, P. (2017) · 2017 IEEE International Conference on Web Services (ICWS) · doi:10.1109/icws.2017.61 · Cited by 255
An Industrial Case Study of Program Artifacts Viewed During Maintenance Tasks
Zou, L., & Godfrey, M. W. (2006) · 2006 13th Working Conference on Reverse Engineering · doi:10.1109/wcre.2006.12 · Cited by 20
Metadata
- Authors
- Gall, H., Jazayeri, M., & Krajewski, J.
- Venue
- Sixth International Workshop on Principles of Software Evolution, 2003. Proceedings.
- Publisher
- IEEE
- Published
- 2004-06-22
- Pages
- 13-23
- OpenAlex
- W1533432827
- Cited by
- 291
- References
- 13
- FWCI
- 22.62
- 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.