04299nam 22007455 450 99646587080331620200702003338.01-280-86572-597866108657273-540-71878-810.1007/978-3-540-71878-9(CKB)1000000000284077(EBL)3036632(SSID)ssj0000292741(PQKBManifestationID)11213251(PQKBTitleCode)TC0000292741(PQKBWorkID)10269773(PQKB)11396590(DE-He213)978-3-540-71878-9(MiAaPQ)EBC3036632(MiAaPQ)EBC6284383(PPN)123161665(EXLCZ)99100000000028407720100301d2007 u| 0engur|n|---|||||txtccrCooperative Bug Isolation[electronic resource] Winning Thesis of the 2005 ACM Doctoral Dissertation Competition /by Ben Liblit1st ed. 2007.Berlin, Heidelberg :Springer Berlin Heidelberg :Imprint: Springer,2007.1 online resource (112 p.)Programming and Software Engineering ;4440Revised version of the author's thesis (Ph.D.)--University of California, Berkeley, 2004."Association for Computing Machinery"--Cover.3-540-71877-X Includes bibliographical references (pages [97]-101) and index.Instrumentation Framework -- Practical Considerations -- Techniques for Statistical Debugging -- Related Work -- Conclusion.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.Programming and Software Engineering ;4440Software engineeringComputer logicAlgorithmsSoftware Engineering/Programming and Operating Systemshttps://scigraph.springernature.com/ontologies/product-market-codes/I14002Software Engineeringhttps://scigraph.springernature.com/ontologies/product-market-codes/I14029Logics and Meanings of Programshttps://scigraph.springernature.com/ontologies/product-market-codes/I1603XAlgorithm Analysis and Problem Complexityhttps://scigraph.springernature.com/ontologies/product-market-codes/I16021Software engineering.Computer logic.Algorithms.Software Engineering/Programming and Operating Systems.Software Engineering.Logics and Meanings of Programs.Algorithm Analysis and Problem Complexity.005.1068Liblit Benauthttp://id.loc.gov/vocabulary/relators/aut508805Association for Computing Machinery.MiAaPQMiAaPQMiAaPQBOOK996465870803316Cooperative Bug Isolation772424UNISA