Cargando…

Debugging by thinking : a multidisciplinary approach /

Debugging by Thinking: A Multi-Disciplinary Approach is the first book to apply the wisdom of six disciplineslogic, mathematics, psychology, safety analysis, computer science, and engineeringto the problem of debugging. It uses the methods of literary detectives such as Sherlock Holmes, the techniqu...

Descripción completa

Detalles Bibliográficos
Clasificación:Libro Electrónico
Autor principal: Metzger, Robert C.
Formato: Electrónico eBook
Idioma:Inglés
Publicado: Boston : Elsevier Digital Press, 2004.
Colección:HP Technologies Ser.
Temas:
Acceso en línea:Texto completo

MARC

LEADER 00000cam a2200000 a 4500
001 SCIDIR_ocm62739690
003 OCoLC
005 20231117015023.0
006 m o d
007 cr zn|||||||||
008 051223s2004 mau ob 001 0 eng d
040 |a NTG  |b eng  |e pn  |c NTG  |d BMU  |d QE2  |d N$T  |d YDXCP  |d MERUC  |d OCLCE  |d OCLCQ  |d E7B  |d OCLCQ  |d U5D  |d IDEBK  |d OCLCQ  |d B24X7  |d DEBBG  |d OCLCQ  |d OCLCF  |d OPELS  |d OKU  |d OCLCQ  |d EBLCP  |d ZCU  |d DEBSZ  |d OCLCQ  |d COO  |d OCLCQ  |d D6H  |d VTS  |d OCLCQ  |d UKMGB  |d S9I  |d JBG  |d STF  |d OCLCQ  |d AJS  |d INARC  |d OCLCO  |d OCLCQ  |d OCLCO  |d OCLCQ 
015 |a GBB6H3837  |2 bnb 
016 7 |a 017581909  |2 Uk 
019 |a 162595143  |a 180879243  |a 437191506  |a 441815778  |a 476108674  |a 507020633  |a 606025582  |a 607055544  |a 607178794 
020 |a 9780080503813  |q (electronic bk.) 
020 |a 0080503810  |q (electronic bk.) 
020 |z 1555583075 
020 |z 9781555583071 
035 |a (OCoLC)62739690  |z (OCoLC)162595143  |z (OCoLC)180879243  |z (OCoLC)437191506  |z (OCoLC)441815778  |z (OCoLC)476108674  |z (OCoLC)507020633  |z (OCoLC)606025582  |z (OCoLC)607055544  |z (OCoLC)607178794 
042 |a dlr 
050 4 |a QA76.9.D43  |b M48 2004b 
072 7 |a COM  |x 051330  |2 bisacsh 
082 0 4 |a 005.1/4  |2 22 
100 1 |a Metzger, Robert C. 
245 1 0 |a Debugging by thinking :  |b a multidisciplinary approach /  |c Robert Charles Metzger. 
260 |a Boston :  |b Elsevier Digital Press,  |c 2004. 
300 |a 1 online resource (xxv, 567 pages) 
336 |a text  |b txt  |2 rdacontent 
337 |a computer  |b c  |2 rdamedia 
338 |a online resource  |b cr  |2 rdacarrier 
347 |a data file 
490 1 |a HP Technologies Ser. 
500 |a Title from title screen. 
500 |a Title from book cover on Web Page (viewed December 23, 2005). 
504 |a Includes bibliographical references and index. 
505 0 |a Cover -- Debugging by Thinking: A Multidisciplinary Approach -- Copyright Page -- Contents -- Preface -- Why I Wrote This Book -- Who Should Read This Book -- How to Read This Book -- Typographical and Grammatical Conventions -- Acknowledgments -- Permissions -- Chapter 1. Introduction -- 1.1 The nature of the problem -- 1.2 The six ways of thinking -- 1.3 The two eras of software engineering -- 1.4 Debugging and development methodologies -- 1.5 Review -- Chapter 2. Sherlock Holmes -- 2.1 Preview -- 2.2 Worldview of the detective -- 2.3 Detective fiction -- 2.4 The character of Sherlock Holmes -- 2.5 The methods of Sherlock Holmes -- 2.6 Review -- Chapter 3. Lord Peter Wimsey -- 3.1 Preview -- 3.2 The character of Lord Peter Wimsey -- 3.3 The methods of Lord Peter Wimsey -- 3.4 Review -- Chapter 4. Professor Solomon -- 4.1 Preview -- 4.2 The methods of Professor Solomon -- 4.3 Review -- Chapter 5. Case Studies I -- 5.1 Case Study I -- Chapter 6. Mathematical Problem Solving -- 6.1 Preview -- 6.2 Worldview of the mathematician -- 6.3 Polya and mathematical heuristics -- 6.4 Mathematical proof texts -- 6.5 Schoenfeld and mathematical problem solving -- 6.6 Applying Schoenfeld to debugging -- 6.7 Review -- Chapter 7. Debugging Strategies -- 7.1 Preview -- 7.2 Evaluation mechanisms -- 7.3 Binary search strategy -- 7.4 Greedy search strategy -- 7.5 Breadth-first search strategy -- 7.6 Depth-first search strategy -- 7.7 Program slice strategy -- 7.8 Deductive-analysis strategy -- 7.9 Inductive-analysis strategy -- 7.10 Choosing a strategy -- 7.11 Review -- Chapter 8. Debugging Heuristics -- 8.1 Preview -- 8.2 Stabilize the program -- 8.3 Create a test case -- 8.4 Reduce the required input -- 8.5 Categorize the problem -- 8.6 Describe the problem -- 8.7 Explain the problem to someone else -- 8.8 Recall a similar problem -- 8.9 Draw a diagram -- 8.10 Choose a hypothesis from historical data -- 8.11 Review -- Chapter 9. Debugging Tactics -- 9.1 Preview -- 9.2 Read the source code -- 9.3 Write a unit test -- 9.4 Display variable values -- 9.5 Display execution messages -- 9.6 Display procedure arguments -- 9.7 Generate a flow trace -- 9.8 Generate a variable snapshot -- 9.9 Generate memory dump -- 9.10 Force variable value -- 9.11 Assert assumptions -- 9.12 Check data structures -- 9.13 Display data structures -- 9.14 Use runtime subscript checking -- 9.15 Use runtime stack checking -- 9.16 Use runtime heap checking -- 9.17 Initialize global variables -- 9.18 Initialize local variables -- 9.19 Change storage class -- 9.20 Use a different compiler -- 9.21 Compile to assembly code -- 9.22 Execute on a different platform -- 9.23 Review -- Chapter 10. Case Studies II -- 10.1 Case Study 2 -- 10.2 Case Study 3 -- Chapter 11. The Way of the Safety Expert --T$107. 
506 |3 Use copy  |f Restrictions unspecified  |2 star  |5 MiAaHDL 
520 |a Debugging by Thinking: A Multi-Disciplinary Approach is the first book to apply the wisdom of six disciplineslogic, mathematics, psychology, safety analysis, computer science, and engineeringto the problem of debugging. It uses the methods of literary detectives such as Sherlock Holmes, the techniques of mathematical problem solving, the results of research into the cognitive psychology of human error, the root cause analyses of safety experts, the compiler analyses of computer science, and the processes of modern engineering to define a systematic approach to identifying and correcting software errors. * Language Independent Methods: Examples are given in Java and C++ * Complete source code shows actual bugs, rather than contrived examples * Examples are accessible with no more knowledge than a course in Data Structures and Algorithms requires * A "thought process diary" shows how the author actually resolved the problems as they occurred 
533 |a Electronic reproduction.  |b [Place of publication not identified] :  |c HathiTrust Digital Library,  |d 2010.  |5 MiAaHDL 
538 |a Master and use copy. Digital master created according to Benchmark for Faithful Digital Reproductions of Monographs and Serials, Version 1. Digital Library Federation, December 2002.  |u http://purl.oclc.org/DLF/benchrepro0212  |5 MiAaHDL 
583 1 |a digitized  |c 2010  |h HathiTrust Digital Library  |l committed to preserve  |2 pda  |5 MiAaHDL 
650 0 |a Debugging in computer science. 
650 6 |a D�ebogage.  |0 (CaQQLa)201-0014818 
650 7 |a COMPUTERS  |x Software Development & Engineering  |x Quality Assurance & Testing.  |2 bisacsh 
650 7 |a Debugging in computer science  |2 fast  |0 (OCoLC)fst00888884 
776 0 8 |i Print version:  |a Metzger, Robert C.  |t Debugging by thinking.  |d Boston : Digital Press, �2004  |z 1555583075  |z 9781555583071  |w (DLC) 2003055655  |w (OCoLC)52729152 
830 0 |a HP Technologies Ser. 
856 4 0 |u https://sciencedirect.uam.elogim.com/science/book/9781555583071  |z Texto completo