The Vital Few Versus the Trivial Many: Examining the Pareto Principle for Software

Authors:
Mechelle Gittens;Yong Kim;David Godwin
Affiliations:
IBM Corporation;IBM Corporation;IBM Corporation
Venue:
COMPSAC '05 Proceedings of the 29th Annual International Computer Software and Applications Conference - Volume 01
Year:
2005

Citing 0
Cited 5

PAT: A pattern classification approach to automatic reference oracles for the testing of mesh simplification programs

Journal of Systems and Software
F007: finding rediscovered faults from the field using function-level failed traces of software in the field

Proceedings of the 2010 Conference of the Center for Advanced Studies on Collaborative Research
Diagnosing new faults using mutants and prior faults (NIER track)

Proceedings of the 33rd International Conference on Software Engineering
Characteristics of multiple-component defects and architectural hotspots: a large system case study

Empirical Software Engineering
An empirical study on the use of mutant traces for diagnosis of faults in deployed systems

Journal of Systems and Software

Quantified Score

Hi-index	0.00

Visualization

Abstract

This paper discusses the Pareto principle as it relates to the distribution of software defects in code. We look at evidence in the context of both the software test team, and users of the software. We also investigate two related principles. The first principle is that the distribution of defects in code relates to the distribution of complexity in code. The second principle is that how we define complexity relates to the distribution of defects in code. We present this work as an empirical study of three general hypotheses investigated for large production-level software; we show that the essence of the principle holds, while precise percentages do not.