TY - BOOK ID - 5452275 TI - Cooperative Bug Isolation : Winning Thesis of the 2005 ACM Doctoral Dissertation Competition AU - Liblit, Ben. AU - Association for Computing Machinery. PY - 2007 SN - 9783540718772 354071877X 9786610865727 1280865725 3540718788 PB - Berlin, Heidelberg : Springer Berlin Heidelberg : Imprint: Springer, DB - UniCat KW - Computer software KW - Computer programming KW - Evaluation KW - Mathematical models. KW - Management. KW - Computer software -- Reliability. KW - Computers -- Reliability. KW - Electronic books. -- local. KW - Computer Science KW - Engineering & Applied Sciences KW - Management KW - Information Technology KW - Software Engineering KW - Computers KW - Reliability. KW - Computer reliability KW - Computer science. KW - Software engineering. KW - Algorithms. KW - Computer logic. KW - Computer Science. KW - Software Engineering/Programming and Operating Systems. KW - Software Engineering. KW - Logics and Meanings of Programs. KW - Algorithm Analysis and Problem Complexity. KW - Computer science logic KW - Logic, Symbolic and mathematical KW - Algorism KW - Algebra KW - Arithmetic KW - Computer software engineering KW - Engineering KW - Informatics KW - Science KW - Foundations KW - Logic design. KW - Computer software. KW - Software, Computer KW - Computer systems KW - Design, Logic KW - Design of logic systems KW - Digital electronics KW - Electronic circuit design KW - Logic circuits KW - Machine theory KW - Switching theory KW - Computer programming management KW - Programming management (Electronic computers) UR - https://www.unicat.be/uniCat?func=search&query=sysid:5452275 AB - Efforts to understand and predict the behavior of software date back to the earliest days of computer programming,over half a century ago. In the intervening decades, the need for effective methods of understanding software has only increased; so- ware has spread to become the underpinning of much of modern society, and the potentially disastrous consequences of broken or poorly understood software have become all too apparent. Ben Liblit’s work reconsiders two common assumptions about how we should analyze software and it arrives at some striking new results. Inprinciple,understandingsoftware is not such a hardproblem. Certainlya c- puter scientist studying programs appears to be in a much stronger position than, say, a biologist trying to understand a living organism or an economist trying to understand the behavior of markets, because the biologist and the economist must rely on indirect observation of the basic processes they wish to understand. A c- puterscientist, however,starts with a complete,precise descriptionof the behaviorof software—the program itself! Of course, the story turns out not to be so straightf- ward, because despite having a perfect description, programs are suf ciently c- plex that it is usually dif cult or even impossible to answer many simple questions about them. ER -