Incorporating a fault categorization and analysis process in the software build cycle

  • Authors:
  • Carol Masuck

  • Affiliations:
  • University of Idaho, Moscow, Idaho

  • Venue:
  • Journal of Computing Sciences in Colleges
  • Year:
  • 2005

Quantified Score

Hi-index 0.00

Visualization

Abstract

Much research has been carried out to study the correlations between software faults and other variables including complexity, time, size, etc. Little work, however, has studied the cause of faults in software and how recognizing the type of fault can improve the quality of software code. In this paper I review a programming technique that requires programmers to both categorize and understand the reason for any faults at each iterative build. Using this technique, experiments were carried out that measured software quality along three variables: total number of faults, total time taken to write the code, and total number of builds. The data collected suggests that all three measured variables improve when programmers take the time to categorize and understand the reason for a fault at build time. The output is particularly interesting because while fault analysis in itself is a time consuming process, the act of fault analysis by the programmer allowed him/her to complete the work in less total time.