Debugging by thinking: a multidisciplinary approach
Gespeichert in:
| 1. Verfasser: | |
|---|---|
| Format: | Elektronisch E-Book |
| Sprache: | English |
| Veröffentlicht: |
Boston
Elsevier Digital Press
2004
|
| Schlagworte: | |
| Online-Zugang: | FAW01 FAW02 Volltext |
| Beschreibung: | Title from title screen. - Title from book cover on Web Page (viewed Dec. 23, 2005). - 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 Includes bibliographical references and index 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 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 |
| Beschreibung: | 1 Online-Ressource (xxv, 567 p.) |
| ISBN: | 0080503810 1555583075 9780080503813 9781555583071 |
Internformat
MARC
| LEADER | 00000nmm a2200000zc 4500 | ||
|---|---|---|---|
| 001 | BV043158834 | ||
| 003 | DE-604 | ||
| 005 | 00000000000000.0 | ||
| 007 | cr|uuu---uuuuu | ||
| 008 | 151126s2004 |||| o||u| ||||||eng d | ||
| 020 | |a 0080503810 |c electronic bk. |9 0-08-050381-0 | ||
| 020 | |a 1555583075 |9 1-55558-307-5 | ||
| 020 | |a 9780080503813 |c electronic bk. |9 978-0-08-050381-3 | ||
| 020 | |a 9781555583071 |9 978-1-55558-307-1 | ||
| 035 | |a (OCoLC)62739690 | ||
| 035 | |a (DE-599)BVBBV043158834 | ||
| 040 | |a DE-604 |b ger |e aacr | ||
| 041 | 0 | |a eng | |
| 049 | |a DE-1046 |a DE-1047 | ||
| 082 | 0 | |a 005.1/4 |2 22 | |
| 100 | 1 | |a Metzger, Robert C. |e Verfasser |4 aut | |
| 245 | 1 | 0 | |a Debugging by thinking |b a multidisciplinary approach |c Robert Charles Metzger |
| 264 | 1 | |a Boston |b Elsevier Digital Press |c 2004 | |
| 300 | |a 1 Online-Ressource (xxv, 567 p.) | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b c |2 rdamedia | ||
| 338 | |b cr |2 rdacarrier | ||
| 500 | |a Title from title screen. - Title from book cover on Web Page (viewed Dec. 23, 2005). - 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 | ||
| 500 | |a Includes bibliographical references and index | ||
| 500 | |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 -- | ||
| 500 | |a - 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 -- | ||
| 500 | |a - 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 | ||
| 500 | |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 | ||
| 650 | 7 | |a COMPUTERS / Software Development & Engineering / Quality Assurance & Testing |2 bisacsh | |
| 650 | 7 | |a Debugging in computer science |2 fast | |
| 650 | 4 | |a Debugging in computer science | |
| 856 | 4 | 0 | |u http://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&db=nlabk&AN=209346 |x Aggregator |3 Volltext |
| 912 | |a ZDB-4-EBA | ||
| 999 | |a oai:aleph.bib-bvb.de:BVB01-028583025 | ||
| 966 | e | |u http://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&db=nlabk&AN=209346 |l FAW01 |p ZDB-4-EBA |q FAW_PDA_EBA |x Aggregator |3 Volltext | |
| 966 | e | |u http://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&db=nlabk&AN=209346 |l FAW02 |p ZDB-4-EBA |q FAW_PDA_EBA |x Aggregator |3 Volltext | |
Datensatz im Suchindex
| _version_ | 1804175626976886784 |
|---|---|
| any_adam_object | |
| author | Metzger, Robert C. |
| author_facet | Metzger, Robert C. |
| author_role | aut |
| author_sort | Metzger, Robert C. |
| author_variant | r c m rc rcm |
| building | Verbundindex |
| bvnumber | BV043158834 |
| collection | ZDB-4-EBA |
| ctrlnum | (OCoLC)62739690 (DE-599)BVBBV043158834 |
| dewey-full | 005.1/4 |
| dewey-hundreds | 000 - Computer science, information, general works |
| dewey-ones | 005 - Computer programming, programs, data, security |
| dewey-raw | 005.1/4 |
| dewey-search | 005.1/4 |
| dewey-sort | 15.1 14 |
| dewey-tens | 000 - Computer science, information, general works |
| discipline | Informatik |
| format | Electronic eBook |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>05812nmm a2200457zc 4500</leader><controlfield tag="001">BV043158834</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">00000000000000.0</controlfield><controlfield tag="007">cr|uuu---uuuuu</controlfield><controlfield tag="008">151126s2004 |||| o||u| ||||||eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">0080503810</subfield><subfield code="c">electronic bk.</subfield><subfield code="9">0-08-050381-0</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">1555583075</subfield><subfield code="9">1-55558-307-5</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9780080503813</subfield><subfield code="c">electronic bk.</subfield><subfield code="9">978-0-08-050381-3</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781555583071</subfield><subfield code="9">978-1-55558-307-1</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)62739690</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV043158834</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">aacr</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-1046</subfield><subfield code="a">DE-1047</subfield></datafield><datafield tag="082" ind1="0" ind2=" "><subfield code="a">005.1/4</subfield><subfield code="2">22</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Metzger, Robert C.</subfield><subfield code="e">Verfasser</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Debugging by thinking</subfield><subfield code="b">a multidisciplinary approach</subfield><subfield code="c">Robert Charles Metzger</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Boston</subfield><subfield code="b">Elsevier Digital Press</subfield><subfield code="c">2004</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">1 Online-Ressource (xxv, 567 p.)</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Title from title screen. - Title from book cover on Web Page (viewed Dec. 23, 2005). - 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</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Includes bibliographical references and index</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="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 -- </subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a"> - 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 -- </subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a"> - 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</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="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</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">COMPUTERS / Software Development & Engineering / Quality Assurance & Testing</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">Debugging in computer science</subfield><subfield code="2">fast</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Debugging in computer science</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="u">http://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&db=nlabk&AN=209346</subfield><subfield code="x">Aggregator</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-4-EBA</subfield></datafield><datafield tag="999" ind1=" " ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-028583025</subfield></datafield><datafield tag="966" ind1="e" ind2=" "><subfield code="u">http://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&db=nlabk&AN=209346</subfield><subfield code="l">FAW01</subfield><subfield code="p">ZDB-4-EBA</subfield><subfield code="q">FAW_PDA_EBA</subfield><subfield code="x">Aggregator</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="966" ind1="e" ind2=" "><subfield code="u">http://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&db=nlabk&AN=209346</subfield><subfield code="l">FAW02</subfield><subfield code="p">ZDB-4-EBA</subfield><subfield code="q">FAW_PDA_EBA</subfield><subfield code="x">Aggregator</subfield><subfield code="3">Volltext</subfield></datafield></record></collection> |
| id | DE-604.BV043158834 |
| illustrated | Not Illustrated |
| indexdate | 2024-07-10T07:19:17Z |
| institution | BVB |
| isbn | 0080503810 1555583075 9780080503813 9781555583071 |
| language | English |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-028583025 |
| oclc_num | 62739690 |
| open_access_boolean | |
| owner | DE-1046 DE-1047 |
| owner_facet | DE-1046 DE-1047 |
| physical | 1 Online-Ressource (xxv, 567 p.) |
| psigel | ZDB-4-EBA ZDB-4-EBA FAW_PDA_EBA |
| publishDate | 2004 |
| publishDateSearch | 2004 |
| publishDateSort | 2004 |
| publisher | Elsevier Digital Press |
| record_format | marc |
| spelling | Metzger, Robert C. Verfasser aut Debugging by thinking a multidisciplinary approach Robert Charles Metzger Boston Elsevier Digital Press 2004 1 Online-Ressource (xxv, 567 p.) txt rdacontent c rdamedia cr rdacarrier Title from title screen. - Title from book cover on Web Page (viewed Dec. 23, 2005). - 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 Includes bibliographical references and index 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 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 COMPUTERS / Software Development & Engineering / Quality Assurance & Testing bisacsh Debugging in computer science fast Debugging in computer science http://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&db=nlabk&AN=209346 Aggregator Volltext |
| spellingShingle | Metzger, Robert C. Debugging by thinking a multidisciplinary approach COMPUTERS / Software Development & Engineering / Quality Assurance & Testing bisacsh Debugging in computer science fast Debugging in computer science |
| title | Debugging by thinking a multidisciplinary approach |
| title_auth | Debugging by thinking a multidisciplinary approach |
| title_exact_search | Debugging by thinking a multidisciplinary approach |
| title_full | Debugging by thinking a multidisciplinary approach Robert Charles Metzger |
| title_fullStr | Debugging by thinking a multidisciplinary approach Robert Charles Metzger |
| title_full_unstemmed | Debugging by thinking a multidisciplinary approach Robert Charles Metzger |
| title_short | Debugging by thinking |
| title_sort | debugging by thinking a multidisciplinary approach |
| title_sub | a multidisciplinary approach |
| topic | COMPUTERS / Software Development & Engineering / Quality Assurance & Testing bisacsh Debugging in computer science fast Debugging in computer science |
| topic_facet | COMPUTERS / Software Development & Engineering / Quality Assurance & Testing Debugging in computer science |
| url | http://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&db=nlabk&AN=209346 |
| work_keys_str_mv | AT metzgerrobertc debuggingbythinkingamultidisciplinaryapproach |