NDLI: Comparing the fault-proneness of new and modified code: an industrial case study

Please wait, while we are loading the content...

Is there a future for empirical software engineering?

Comparing the fault-proneness of new and modified code: an industrial case study

Analysis of the influence of communication between researchers on experiment replication

A framework for the analysis of software cost estimation accuracy

An empirical comparison between pair development and software inspection in Thailand

Successful software project and products: An empirical investigation

Maximising the information gained from an experimental analysis of code inspection and static analysis for concurrent java components

The evolution of FreeBSD and linux

A follow up study of the effect of personality on the performance of software engineering teams

Improving software testing by observing practice

Common refactorings, a dependency graph and some code smells: an empirical study of Java OSS

A goal question metric based approach for efficient measurement framework definition

Requirement error abstraction and classification: an empirical study

Evaluating the efficacy of test-driven development: industrial case studies

Predicting fault-prone components in a java legacy system

Evaluating guidelines for empirical software engineering studies

A comparative study of attribute weighting heuristics for effort estimation by analogy

PBR vs. checklist: a replication in the n-fold inspection context

A case study on the application of UML in legacy development

Predicting good requirements for in-house development projects

Testing and inspecting reusable product line components: first empirical results

A family of empirical studies to compare informal and optimization-based planning of software releases

An empirical study of developers views on software reuse in statoil ASA

An industrial case study of structural testing applied to safety-critical embedded software

Drivers for software refactoring decisions

Evaluating the practical use of different measurement scales in requirements prioritisation

Identifying domain-specific defect classes using inspections and change history

Evaluating advantages of test driven development: a controlled experiment with professionals

Predicting component failures at design time

Using observational pilot studies to test and improve lab packages

Cross-company and single-company effort models using the ISBSG database: a further replicated study

An empirical analysis and comparison of random testing techniques

Documenting design decision rationale to improve individual and team design decision making: an experimental evaluation

Agile customer engagement: a longitudinal qualitative case study

A literature survey of the quality economics of defect-detection techniques

Empirical estimates of software availability of deployed systems

Distributed versus face-to-face meetings for architecture evalution: a controlled experiment

An empirical evaluation of a testing and debugging methodology for Excel

Eliciting better quality architecture evaluation scenarios: a controlled experiment on top-down vs. bottom-up

Comparing the fault-proneness of new and modified code: an industrial case study

Content Provider	ACM Digital Library
Author	Tomaszewski, Piotr Damm, Lars-Ola
Abstract	Faults are considered as one of the important factors affecting the cost of software development projects. To be able to efficiently handle faults, we must increase our understanding of the factors that make the code fault-prone. A majority of large software systems evolve during their lifetime. In each new release of the system the functionality can be added by writing new classes or/and by modifying already existing ones. In this study we compared the fault-proneness of new and modified classes in such systems. Our study is based on two releases of two large telecommunication systems developed at Ericsson. The major finding of the study is that the risk of introducing faults (the number of faults in the class /the number of new or modified lines of code in the class) is 20 to 40 times as high in modified classes compared to new ones. In the systems which we analyzed a small modification (a few percent) of the class resulted in as many faults as we would expect when the same class was written from scratch. Previous research on this relationship does not appear to exist. Partly in conflict with related research, we found that there is no statistically significant difference between the average number of faults in modified and new classes, and that the average fault-densities (the number of faults/the size of the entire class) in new and in modified classes are very similar. Finally, we also suggest how our findings can be used in practice.
Starting Page	2
Ending Page	7
Page Count	6
File Format	PDF
ISBN	1595932186
DOI	10.1145/1159733.1159737
Language	English
Publisher	Association for Computing Machinery (ACM)
Publisher Date	2006-09-21
Publisher Place	New York
Access Restriction	Subscribed
Subject Keyword	Modified code Fault-proneness Fault prediction
Content Type	Text
Resource Type	Article

Sl.	Authority	Responsibilities	Communication Details
1	Ministry of Education (GoI), Department of Higher Education	Sanctioning Authority	https://www.education.gov.in/ict-initiatives
2	Indian Institute of Technology Kharagpur	Host Institute of the Project: The host institute of the project is responsible for providing infrastructure support and hosting the project	https://www.iitkgp.ac.in
3	National Digital Library of India Office, Indian Institute of Technology Kharagpur	The administrative and infrastructural headquarters of the project	Dr. B. Sutradhar bsutra@ndl.gov.in
4	Project PI / Joint PI	Principal Investigator and Joint Principal Investigators of the project	Dr. B. Sutradhar bsutra@ndl.gov.in Prof. Saswat Chakrabarti will be added soon
5	Website/Portal (Helpdesk)	Queries regarding NDLI and its services	support@ndl.gov.in
6	Contents and Copyright Issues	Queries related to content curation and copyright issues	content@ndl.gov.in
7	National Digital Library of India Club (NDLI Club)	Queries related to NDLI Club formation, support, user awareness program, seminar/symposium, collaboration, social media, promotion, and outreach	clubsupport@ndl.gov.in
8	Digital Preservation Centre (DPC)	Assistance with digitizing and archiving copyright-free printed books	dpc@ndl.gov.in
9	IDR Setup or Support	Queries related to establishment and support of Institutional Digital Repository (IDR) and IDR workshops	idr@ndl.gov.in

Comparing design and code metrics for software quality prediction

An empirical study on dependence clusters for effort-aware fault-proneness prediction

The Effect of Testability on Fault Proneness A case study of the Apache HTTP Server

Exploratory study of a UML metric for fault prediction

G.: Fault-Proneness Estimation and Java Migration: A Preliminary Case Study (2009)

The Effect of Testability on Fault Proneness: A Case Study of the Apache HTTP Server

Comparing fault-proneness estimation models

An exploratory case study of aspect‐oriented metrics for fault proneness, content and fixing effort prediction

The Accuracy of Fault Prediction in Modified Code – Statistical Model vs. Expert Estimation

Comparing the fault-proneness of new and modified code: an industrial case study

Similar Documents

Comparing design and code metrics for software quality prediction

An empirical study on dependence clusters for effort-aware fault-proneness prediction

The Effect of Testability on Fault Proneness A case study of the Apache HTTP Server

Exploratory study of a UML metric for fault prediction

G.: Fault-Proneness Estimation and Java Migration: A Preliminary Case Study (2009)

The Effect of Testability on Fault Proneness: A Case Study of the Apache HTTP Server

Comparing fault-proneness estimation models

An exploratory case study of aspect‐oriented metrics for fault proneness, content and fixing effort prediction

The Accuracy of Fault Prediction in Modified Code – Statistical Model vs. Expert Estimation

Comparing the fault-proneness of new and modified code: an industrial case study