Proceedings of the ACM-IEEE International Symposium on Empirical Software Engineering and Measurement 2012
DOI: 10.1145/2372251.2372308
|View full text |Cite
|
Sign up to set email alerts
|

The impact of process maturity on defect density

Abstract: Context: A common assumption in software engineering is that a more structured process delivers higher quality products. However, there are limited empirical studies that support this assumption. Objective: In this paper we analyze 61 projects looking for a relationship between process structured and quality of the product. The structure is considered under two dimensions: level of maturity (as measured by the CMMI assessment model) and type (e.g. TSP, RUP). The quality of the product is measured in terms of D… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
9
0

Year Published

2013
2013
2024
2024

Publication Types

Select...
7
3

Relationship

0
10

Authors

Journals

citations
Cited by 16 publications
(9 citation statements)
references
References 14 publications
0
9
0
Order By: Relevance
“…Software faults or defects (often called bugs) are one of the most persistent challenges of software reliability. Despite the modern tools available for developers and the intensive research on software reliability and quality, the general statistics for software developed (most of them related to software for critical applications) show high bug density figures, ranging from 1 to 5 bugs per 1000 lines of delivered code [2] [3][4]. This problem is amplified by the constant pressure to minimize the time-to-market and due to the dramatic increase in code size witnessed by modern software.…”
Section: Introductionmentioning
confidence: 99%
“…Software faults or defects (often called bugs) are one of the most persistent challenges of software reliability. Despite the modern tools available for developers and the intensive research on software reliability and quality, the general statistics for software developed (most of them related to software for critical applications) show high bug density figures, ranging from 1 to 5 bugs per 1000 lines of delivered code [2] [3][4]. This problem is amplified by the constant pressure to minimize the time-to-market and due to the dramatic increase in code size witnessed by modern software.…”
Section: Introductionmentioning
confidence: 99%
“…Steve McConnell’s seminal book [ 1 ] points to an industry average of about 15 defects per KLoCs, which is a very large standard deviation. Even when software is developed using highly mature processes, the deployed code still has a relatively high defect density, from 1 to 5 bugs per KLoC [ 2 , 3 , 4 , 5 ]. More recent field data from several projects show defects densities from 1 to 6 bugs per KLoC [ 6 ], suggesting that in real projects, often characterized by millions of lines of code, the defect density remains quite significant and represents a huge cost for the software industry and society in general.…”
Section: Introductionmentioning
confidence: 99%
“…The transversal nature of software use (i.e., software is needed for almost all modern human activities) makes software development one of the largest industry sectors, if not the largest. However, in spite of decades of research and advances in software engineering and software reliability, software defects (i.e., bugs) remain as the most enduring problem of software quality [3][4][5]. The average number of bugs per 1000 lines of delivered code (KLOC) [6] remains astonishingly high, which reinforces the importance of understanding error-monitoring processes in the brain during execution of this novel complex task.…”
Section: Introductionmentioning
confidence: 99%