A Case Study of Defect-Density and Change-Density and their Progress over Time

Gupta, Anita; Slyngstad, Odd Petter N.; Conradi, Reidar; Mohagheghi, Parastoo; Rønneberg, Harald; Landre, Einar

doi:10.1109/csmr.2007.5

Cited by 6 publications

(12 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Another major incentive has been to the ability to use a consistent and resilient technical platform for development and integration of software systems [19]. This reuse strategy is now being propagated to and adopted in other divisions within StatoilHydro ASA.…”

Section: Contextmentioning

confidence: 99%

“…In summary, between releases the change requests show experienced evolution, while the trouble reports show needed maintenance. A complete description of change data handling in StatoilHydro ASA is reported in [19]. Data on defect density and change density for the reusable components, using what is here called the test-last approach, were also analyzed and compared to non-reusable components by us in [19].…”

Section: Contextmentioning

confidence: 99%

See 1 more Smart Citation

The Impact of Test Driven Development on the Evolution of a Reusable Framework of Components  An Industrial Case Study

Slyngstad

Conradi

et al. 2008

2008 the Third International Conference on Software Engineering Advances

Self Cite

View full text Add to dashboard Cite

Test Driven Development (TDD) is a software engineering technique to promote fast feedback, taskoriented development, improved quality assurance and more comprehensible low-level software design. Benefits have been shown for non-reusable software development in terms of improved quality (e.g. lower defect density). We have carried out an empirical study of a framework of reusable components, to see whether these benefits can be shown for reusable components. The framework is used in building new applications and provides services to these applications during runtime. The three first versions of this framework were developed using traditional test-last development, while for the two latest versions TDD was used. Our results show benefits in terms of reduced mean defect density (35.86%), when using TDD, over two releases. Mean change density was 76.19% lower for TDD than for test-last development. Finally, the change distribution for the TDD approach was 33.3% perfective, 5.6% adaptive and 61.1% preventive.

show abstract

Section: Contextmentioning

confidence: 99%

Section: Contextmentioning

confidence: 99%

The Impact of Test Driven Development on the Evolution of a Reusable Framework of Components  An Industrial Case Study

Slyngstad

Conradi

et al. 2008

2008 the Third International Conference on Software Engineering Advances

Self Cite

View full text Add to dashboard Cite

show abstract

“…Reused components had a higher number of defects of the highest severity before delivery, but fewer defects post-delivery. Reusable vs. non-reusable components [4] Defect density (number of defects/SLOC) and change density (number of change requests/SLOC).…”

Section: Related Workmentioning

confidence: 99%

The Empirical Studies on Quality Benefits of Reusing Software Components

Gupta

Arvid

et al. 2007

31st Annual International Computer Software and Applications Conference - Vol. 2 - (COMPSAC 2007)

Self Cite

View full text Add to dashboard Cite

The benefits of reusing software components have been studied for many years. Several previous studies have concluded that reused components have fewer defects in general than non-reusable components. However, few of these studies have gone a further step, i.e., investigating which type of defects has been reduced because of reuse. Thus, it is suspected that making a software component reusable will automatically improve its quality. This paper presents an on-going industrial empirical study on the quality benefits of reuse. We are going to compare the defects types, which are classified by ODC (Orthogonal Defect Classification), of the reusable component vs. the non-reusable components in several large and medium software systems. The intention is to figure out which defects have been reduced because of reuse and the reasons of the reduction.

show abstract

“…Several previous studies have concluded that reusable software components are more stable (less change density) than non-reusable components [20][21][22]. However, few of these studies have investigated and compared the characteristics of software changes (such as distribution, how long the changes tend to stay in the system, and number of files modified for each change type) for reusable and non-reusable components.…”

Section: Introductionmentioning

confidence: 99%

“…Other studies [20][21][22][23][24][25] have investigated whether the amount of changes varies according to development characteristics without classifying changes into different categories. We are aware of no previous studies that have compared change distributions between reusable software components and non-reusable ones, which we are looking at in this study.…”

Section: Related Workmentioning

confidence: 99%

Experience Report on the Effect of Software Development Characteristics on Change Distribution

Gupta

Conradi

Shull

et al.

Product-Focused Software Process Improvement

Self Cite

View full text Add to dashboard Cite

Abstract. This paper reports on an industrial case study in a large Norwegian Oil and Gas company (StatoilHydro ASA) involving a reusable Java-class framework and an application that uses that framework. We analyzed software changes from three releases of the framework and the application. On the basis of our analysis of the data, we found that perfective and corrective changes account for the majority of changes in both the reusable framework and the nonreusable application. Although adaptive changes are more frequent and has longer active time in the reusable framework, it went through less refactoring compared to the non-reusable application. For the non-reusable application we saw preventive changes as more frequent and with longer active time. We also found that designing for reuse seems to lead to fewer changes, as well as we saw a positive effect on doing refactoring.

show abstract

A Case Study of Defect-Density and Change-Density and their Progress over Time

Abstract: Abstract

Cited by 6 publications

References 13 publications

The Impact of Test Driven Development on the Evolution of a Reusable Framework of Components  An Industrial Case Study

The Impact of Test Driven Development on the Evolution of a Reusable Framework of Components  An Industrial Case Study

The Empirical Studies on Quality Benefits of Reusing Software Components

Experience Report on the Effect of Software Development Characteristics on Change Distribution

Contact Info

Product

Resources

About

A Case Study of Defect-Density and Change-Density and their Progress over Time

Abstract: Abstract

Cited by 6 publications

References 13 publications

The Impact of Test Driven Development on the Evolution of a Reusable Framework of Components &#150; An Industrial Case Study

The Impact of Test Driven Development on the Evolution of a Reusable Framework of Components &#150; An Industrial Case Study

The Empirical Studies on Quality Benefits of Reusing Software Components

Experience Report on the Effect of Software Development Characteristics on Change Distribution

Contact Info

Product

Resources

About

The Impact of Test Driven Development on the Evolution of a Reusable Framework of Components An Industrial Case Study

The Impact of Test Driven Development on the Evolution of a Reusable Framework of Components An Industrial Case Study