Predicting software defect density: A case study on automated static code analysis

Artem Marchenko, Pekka Abrahamsson

Research output: Chapter in Book/Report/Conference proceedingConference article in proceedingsScientificpeer-review

8 Citations (Scopus)


The number of defects is an important indicator of software quality. Agile software development methods put an explicit requirement on automation and permanently low defect rates. Code analysis tools are seen as a prominent way to facilitate the defect prediction. There are only few studies addressing the feasibility of predicting a defect rate with the help of static code analysis tools in the area of embedded software. This study addresses the usefulness of two selected tools in the Symbian C++ environment. Five projects and 137 KLOC of the source code have been processed and compared to the actual defect rate. As a result a strong positive correlation with one of the tools was found. It confirms the usefulness of a static code analysis tool as a way for estimating the amount of defects left in the product.
Original languageEnglish
Title of host publicationAgile Processes in Software Engineering and Extreme Programming
Subtitle of host publication8th International Conference, XP 2007
EditorsGiulio Concas, Ernesto Damiani, Marco Scotto, Giancarlo Succi
Place of PublicationBerlin - Heidelberg
ISBN (Electronic)978-3-540-73101-6
ISBN (Print)978-3-540-73100-9
Publication statusPublished - 2007
MoE publication typeA4 Article in a conference publication
Event8th International Conference on Agile Software Development, XP 2007 - Como, Italy
Duration: 18 Jun 200722 Jun 2007

Publication series

SeriesLecture Notes in Computer Science


Conference8th International Conference on Agile Software Development, XP 2007


  • agile software development
  • static code analysis
  • automation
  • defect estimation
  • quality
  • embedded software
  • case study


Dive into the research topics of 'Predicting software defect density: A case study on automated static code analysis'. Together they form a unique fingerprint.

Cite this