Home

About

Advanced Search

Browse by Discipline

Scientific Societies

E-print Alerts

Add E-prints

E-print Network
FAQHELPSITE MAPCONTACT US


  Advanced Search  

 
Sampling User Executions for Bug Isolation Ben Liblit Alex Aiken Alice X. Zheng Michael I. Jordan
 

Summary: Sampling User Executions for Bug Isolation
Ben Liblit Alex Aiken Alice X. Zheng Michael I. Jordan
{liblit,aiken,alicez,jordan}@cs.berkeley.edu
Department of Electrical Engineering and Computer Science
University of California, Berkeley
Berkeley, CA 94720-1776
1. Introduction
Many computer scientists think of a program as either
correct (i.e. it meets some specification) or incorrect (i.e. it
does not meet some specification). But industrial software
development is as much about economics as computer sci-
ence. Software quality is a monetary balancing act among
engineers' salaries, time to market, user expectations, and
other business concerns. We ship software when it seems
correct enough to neither embarrass us nor alienate users.
We ship software with known bugs that are not worth fix-
ing, and users uncover new bugs that we never imagined.
Practitioners clearly need something other than a
Boolean notion of correctness, but such a notion has been
difficult to quantify. In-house testing can only guess at field

  

Source: Aiken, Alex - Department of Computer Science, Stanford University
Jordan, Michael I. - Department of Electrical Engineering and Computer Sciences, University of California at Berkeley

 

Collections: Computer Technologies and Information Sciences