Fault Slip Through measurement in software development process

  • Duka D
  • Hribar L
  • 1


    Mendeley users who have this article in their library.
  • N/A


    Citations of this article.


The pressure to improve software development process is not new, but in today's competitive environment there is even greater emphasis on delivering a better service at lower cost. In market-driven development where time-to-market is of crucial importance, software development companies seek improvements that can decrease the lead-time and improve the delivery precision. One way to achieve this is by analyzing the test process since rework commonly accounts for more than half of the development time. A large reason for high rework costs is fault slippage from earlier phases where they are cheaper to find and remove. As an input to improvements, this article introduces a measure that can quantify this relationship. That is, a measure called faults-slip-through, which determines the faults that would have been more cost-effective to find in an earlier phase.

Author-supplied keywords

  • Current measurement
  • Fault diagnosis
  • Organizations
  • Phase measurement
  • Programming
  • Software
  • Testing
  • early fault detection
  • fault latency
  • fault metric
  • fault slip through measurement
  • faults-slip-through
  • market-driven development
  • software development management
  • software development process
  • software fault tolerance
  • software metrics

Get free article suggestions today

Mendeley saves you time finding and organizing research

Sign up here
Already have an account ?Sign in

Find this document


  • D. Duka

  • L. Hribar

Cite this document

Choose a citation style from the tabs below

Save time finding and organizing research with Mendeley

Sign up for free