⚠ Official Notice: www.ijisrt.com is the official website of the International Journal of Innovative Science and Research Technology (IJISRT) Journal for research paper submission and publication. Please beware of fake or duplicate websites using the IJISRT name.



A Review of Cross-Project and Just-in-Time Software Defect Prediction with Lessons from Real-World Failures


Authors : Radhalakshmi Rajagopalan; Dr. Radha V.

Volume/Issue : Volume 11 - 2026, Issue 11 - November


Google Scholar : https://tinyurl.com/2s4cud7d

DOI : https://doi.org/10.38124/ijisrt/26nov573

Note : A published paper may take 4-5 working days from the publication date to appear in PlumX Metrics, Semantic Scholar, and ResearchGate.


Abstract : Software defects that escape into production can ground airline fleets, halt trading desks and disrupt essential services within minutes. This review connects the research on software defect prediction with the real cost of such failures. It first examines a set of widely reported incidents in aviation, airlines, finance and banking, drawn from official investigation reports, company filings and news coverage, and summarises their causes and documented losses. It then reviews two lines of defect prediction research that matter most in industrial settings. Cross-project defect prediction (CPDP) addresses the common situation in which a new or small project has too little history to train its own model, and must borrow knowledge from other projects through instance selection, feature transformation, transfer learning and deep domain adaptation. Just-in-time defect prediction (JIT-DP) scores each code change at the moment it is committed, so that risky changes can be reviewed before they reach production; deep learning models for JIT-DP learn directly from commit messages and code diffs. The review compares methods, datasets and evaluation practices in both lines, and then asks a practical question: for each incident, at which stage could a prediction model plausibly have raised a warning, and where were the causes outside its reach? It closes with a research agenda for deployment-aware defect prediction that combines cross-project knowledge, change-level risk scores and release-time safeguards.

Keywords : Software Defect Prediction, Cross-Project Defect Prediction, Just-in-Time Defect Prediction, Transfer Learning, Deep Learning, Software Failures, Cost of Poor Software Quality, Airline IT Outages.

References :

  • Academic Sources
  1. T. Hall, S. Beecham, D. Bowes, D. Gray, and S. Counsell, “A systematic literature review on fault prediction performance in software engineering,” IEEE Trans. Softw. Eng., vol. 38, no. 6, pp. 1276–1304, 2012.
  2. S. Hosseini, B. Turhan, and D. Gunarathna, “A systematic literature review and meta-analysis on cross project defect prediction,” IEEE Trans. Softw. Eng., vol. 45, no. 2, pp. 111–147, 2019.
  3. S. Herbold, A. Trautsch, and J. Grabowski, “A comparative study to benchmark cross-project defect prediction approaches,” IEEE Trans. Softw. Eng., vol. 44, no. 9, pp. 811–833, 2018.
  4. Y. Kamei et al., “A large-scale empirical study of just-in-time quality assurance,” IEEE Trans. Softw. Eng., vol. 39, no. 6, pp. 757–773, 2013.
  5. G. Giray, K. E. Bennin, Ö. Köksal, Ö. Babur, and B. Tekinerdogan, “On the use of deep learning in software defect prediction,” J. Syst. Softw., vol. 195, 2023.
  6. B. Kitchenham and S. Charters, “Guidelines for performing systematic literature reviews in software engineering,” Tech. Rep. EBSE-2007-01, Keele University and Durham University, 2007.
  7. J. Nam and S. Kim, “Heterogeneous defect prediction,” in Proc. ESEC/FSE, 2015, pp. 508–519.
  8. A. Mockus and D. M. Weiss, “Predicting risk of software changes,” Bell Labs Tech. J., vol. 5, no. 2, pp. 169–180, 2000.
  9. S. Kim, E. J. Whitehead, and Y. Zhang, “Classifying software changes: Clean or buggy?” IEEE Trans. Softw. Eng., vol. 34, no. 2, pp. 181–196, 2008.
  10. J. Śliwerski, T. Zimmermann, and A. Zeller, “When do changes induce fixes?” in Proc. MSR, 2005.
  11. Y. Kamei, T. Fukushima, S. McIntosh, K. Yamashita, N. Ubayashi, and A. E. Hassan, “Studying just-in-time defect prediction using cross-project models,” Empir. Softw. Eng., vol. 21, no. 5, pp. 2072–2106, 2016.
  12. T. Zimmermann, N. Nagappan, H. Gall, E. Giger, and B. Murphy, “Cross-project defect prediction: A large scale experiment on data vs. domain vs. process,” in Proc. ESEC/FSE, 2009.
  13. B. Turhan, T. Menzies, A. B. Bener, and J. Di Stefano, “On the relative value of cross-company and within-company data for defect prediction,” Empir. Softw. Eng., vol. 14, no. 5, pp. 540–578, 2009.
  14. Y. Ma, G. Luo, X. Zeng, and A. Chen, “Transfer learning for cross-company software defect prediction,” Inf. Softw. Technol., vol. 54, no. 3, pp. 248–256, 2012.
  15. J. Nam, S. J. Pan, and S. Kim, “Transfer defect learning,” in Proc. ICSE, 2013.
  16. S. J. Pan and Q. Yang, “A survey on transfer learning,” IEEE Trans. Knowl. Data Eng., vol. 22, no. 10, pp. 1345–1359, 2010.
  17. F. Zhang, A. Mockus, I. Keivanloo, and Y. Zou, “Towards building a universal defect prediction model,” in Proc. MSR, 2014.
  18. S. Wang, T. Liu, J. Nam, and L. Tan, “Deep semantic feature learning for software defect prediction,” IEEE Trans. Softw. Eng., vol. 46, no. 12, pp. 1267–1293, 2020.
  19. J. Chen et al., “Software visualization and deep transfer learning for effective software defect prediction,” in Proc. ICSE, 2020, pp. 578–589.
  20. Y. Ganin et al., “Domain-adversarial training of neural networks,” J. Mach. Learn. Res., vol. 17, no. 59, pp. 1–35, 2016.
  21. H. K. Dam et al., “Lessons learned from using a deep tree-based model for software defect prediction in practice,” in Proc. MSR, 2019, pp. 46–57.
  22. X. Yang, D. Lo, X. Xia, Y. Zhang, and J. Sun, “Deep learning for just-in-time defect prediction,” in Proc. IEEE QRS, 2015.
  23. T. Hoang, H. K. Dam, Y. Kamei, D. Lo, and N. Ubayashi, “DeepJIT: An end-to-end deep learning framework for just-in-time defect prediction,” in Proc. MSR, 2019.
  24. T. Hoang, H. J. Kang, D. Lo, and J. Lawall, “CC2Vec: Distributed representations of code changes,” in Proc. ICSE, 2020.
  25. Z. Zeng, Y. Zhang, H. Zhang, and L. Zhang, “Deep just-in-time defect prediction: How far are we?” in Proc. ISSTA, 2021, pp. 427–438.
  26. C. Pornprasit and C. Tantithamthavorn, “JITLine: A simpler, better, faster, finer-grained just-in-time defect prediction,” in Proc. MSR, 2021.
  27. C. Ni, W. Wang, K. Yang, X. Xia, K. Liu, and D. Lo, “The best of both worlds: Integrating semantic features with expert features for defect prediction and localization,” in Proc. ESEC/FSE, 2022.
  28. S. McIntosh and Y. Kamei, “Are fix-inducing changes a moving target? A longitudinal case study of just-in-time defect prediction,” IEEE Trans. Softw. Eng., vol. 44, no. 5, pp. 412–428, 2018.
  29. G. G. Cabral, L. L. Minku, E. Shihab, and S. Mujahid, “Class imbalance evolution and verification latency in just-in-time software defect prediction,” in Proc. ICSE, 2019.
  30. M. Jureczko and L. Madeyski, “Towards identifying software project clusters with regard to defect prediction,” in Proc. PROMISE, 2010.
  31. T. Menzies, J. Greenwald, and A. Frank, “Data mining static code attributes to learn defect predictors,” IEEE Trans. Softw. Eng., vol. 33, no. 1, pp. 2–13, 2007.
  32. M. Shepperd, Q. Song, Z. Sun, and C. Mair, “Data quality: Some comments on the NASA software defect datasets,” IEEE Trans. Softw. Eng., vol. 39, no. 9, pp. 1208–1215, 2013.
  33. M. D’Ambros, M. Lanza, and R. Robbes, “Evaluating defect prediction approaches: A benchmark and an extensive comparison,” Empir. Softw. Eng., vol. 17, pp. 531–577, 2012.
  34. S. Wattanakriengkrai, P. Thongtanunam, C. Tantithamthavorn, H. Hata, and K. Matsumoto, “Predicting defective lines using a model-agnostic technique,” IEEE Trans. Softw. Eng., vol. 48, no. 5, pp. 1480–1496, 2022.
  35. C. Tantithamthavorn, S. McIntosh, A. E. Hassan, and K. Matsumoto, “An empirical comparison of model validation techniques for defect prediction models,” IEEE Trans. Softw. Eng., vol. 43, no. 1, pp. 1–18, 2017.
  36. M. Shepperd, D. Bowes, and T. Hall, “Researcher bias: The use of machine learning in software defect prediction,” IEEE Trans. Softw. Eng., vol. 40, no. 6, pp. 603–616, 2014.
  37. E. C. Neto, D. A. da Costa, and U. Kulesza, “The impact of refactoring changes on the SZZ algorithm: An empirical study,” in Proc. SANER, 2018.
  38. H. Keshavarz and M. Nagappan, “ApacheJIT: A large dataset for just-in-time defect prediction,” in Proc. MSR, 2022.
  39. J. Jiarpakdee, C. Tantithamthavorn, H. K. Dam, and J. Grundy, “An empirical study of model-agnostic techniques for defect prediction models,” IEEE Trans. Softw. Eng., vol. 48, no. 1, pp. 166–185, 2022.
  • Incident, Regulatory and News Sources
  1. [N1] A. Culafi, “Delta sues CrowdStrike over IT outage fallout,” TechTarget, Oct. 2024. https://www.techtarget.com/cybersecurity/news/366614745/Delta-sues-CrowdStrike-over-IT-outage-fallout
  2. [N2] Reuters, “Delta sues CrowdStrike over software update that prompted flight disruptions,” Business Insurance, Oct. 2024. https://www.businessinsurance.com/delta-sues-crowdstrike-over-software-update-that-prompted-mass-flight-disruptions/
  3. [N3] NPR, “Southwest will pay a $140 million fine for its meltdown during the 2022 holidays,” Dec. 2023. https://www.npr.org/transcripts/1219906471
  4. [N4] Reuters, “Southwest fined $140 million for last year’s holiday meltdown,” NBC DFW, Dec. 2023. https://www.nbcdfw.com/news/business/money-report/southwest-fined-140-million-for-last-years-holiday-meltdown/3414112/
  5. [N5] NBC News, “FAA says problem that grounded US flights last week was unintentional,” Jan. 2023. https://www.nbcnews.com/news/us-news/faa-says-problem-grounded-us-flights-last-week-was-unintentional-rcna66649
  6. [N6] Fox 2 Detroit, “FAA reveals what caused computer outage prompting ground stop,” Jan. 2023. https://www.fox2detroit.com/news/faa-what-caused-january-computer-outage-prompting-ground-stop
  7. [N7] CISQ, “CISQ publishes the Cost of Poor Software Quality in the US: A 2022 Report,” press release, Dec. 2022. https://www.it-cisq.org/press-releases/12-06-22
  8. [N8] U.S. Securities and Exchange Commission, “In the Matter of Knight Capital Americas LLC,” Release No. 34-70694, Oct. 2013. https://www.sec.gov/litigation/admin/2013/34-70694.pdf
  9. [N9] Financial Conduct Authority, “TSB fined £48.65m for operational resilience failings,” press release, Dec. 2022. https://www.fca.org.uk/news/press-releases/tsb-fined-ps4865m-operational-resilience-failings
  10. [N10] ITPro, “TSB bank fined £48 million over botched IT upgrade programme,” Dec. 2022. https://itpro.com/business-strategy/it-infrastructure/369753/tsb-bank-fined-48-million-over-botched-it-upgrade
  11. [N11] Reuters, “CrowdStrike executive apologizes before US Congress for software glitch behind July Microsoft outage,” Deccan Herald, Sep. 2024.
  12. [N12] AIN Online, “FAA bolsters safeguards for NOTAM maintenance, database,” Jan. 2023. https://www.ainonline.com/aviation-news/air-transport/2023-01-31/faa-bolsters-safeguards-notam-maintenance-database.

Software defects that escape into production can ground airline fleets, halt trading desks and disrupt essential services within minutes. This review connects the research on software defect prediction with the real cost of such failures. It first examines a set of widely reported incidents in aviation, airlines, finance and banking, drawn from official investigation reports, company filings and news coverage, and summarises their causes and documented losses. It then reviews two lines of defect prediction research that matter most in industrial settings. Cross-project defect prediction (CPDP) addresses the common situation in which a new or small project has too little history to train its own model, and must borrow knowledge from other projects through instance selection, feature transformation, transfer learning and deep domain adaptation. Just-in-time defect prediction (JIT-DP) scores each code change at the moment it is committed, so that risky changes can be reviewed before they reach production; deep learning models for JIT-DP learn directly from commit messages and code diffs. The review compares methods, datasets and evaluation practices in both lines, and then asks a practical question: for each incident, at which stage could a prediction model plausibly have raised a warning, and where were the causes outside its reach? It closes with a research agenda for deployment-aware defect prediction that combines cross-project knowledge, change-level risk scores and release-time safeguards.

Keywords : Software Defect Prediction, Cross-Project Defect Prediction, Just-in-Time Defect Prediction, Transfer Learning, Deep Learning, Software Failures, Cost of Poor Software Quality, Airline IT Outages.

Paper Submission Last Date
30 - November - 2026

SUBMIT YOUR PAPER CALL FOR PAPERS
Video Explanation for Published paper

Never miss an update from Papermashup

Get notified about the latest tutorials and downloads.

Subscribe by Email

Get alerts directly into your inbox after each post and stay updated.
Subscribe
OR

Subscribe by RSS

Add our RSS to your feedreader to get regular updates from us.
Subscribe