Software faults: a quantifiable definition

  • Authors:

  • John C. Munson;Allen P. Nikora;Joseph S. Sherif

  • Affiliations:

  • Computer Science Department, University of Idaho, Moscow, ID;Jet Propulsion Laboratory, California Institute of Technology, Pasadena, CA;California State University, Fullerton, CA

  • Venue:
  • Advances in Engineering Software
  • Year:
  • 2006

Quantified Score

Hi-index 0.00

Visualization

Abstract

An important aspect of developing models relating the number and type of faults in a software system to a set of structural measurement is defining what constitutes a fault. By definition, a fault is a structural imperfection in a software system that may lead to the system's eventually failing. A measurable and precise definition of what faults are makes it possible to accurately identify and count them, which in turn allows the formulation of models relating fault counts and types to other measurable attributes of a software system. Unfortunately, the most widely used definitions are not measurable--there is no guarantee that two different individuals looking at the same set of failure reports and the same set of fault definitions will count the same number of underlying faults. The incomplete and ambiguous nature of current fault definitions adds a noise component to the inputs used in modeling fault content, If this noise component is sufficiently large, any attempt to develop a fault model will produce invalid results. In this paper, we base our recognition and enumeration of software faults on the grammar of the language of the software system. By tokenizing the differences between a version of the system exhibiting a particular failure behavior, and the version in which changes were made to eliminate that behavior, we are able to unambiguously count the number of faults associated with that failure. With modern configuration management tools, the identification and counting of software faults can be automated.