Debugging by Thinking: A Multidisciplinary Approach (HP Technologies)
Debugging by Thinking: A Multidisciplinary Approach (HP Technologies)
ISBN: 1555583075
EAN: 2147483647
EAN: 2147483647
Year: 2002
Pages: 172
Pages: 172
Authors: Robert Charles Metzger
- Table of Contents
- BackCover
- Debugging by Thinking - A Multidisciplinary Approach
- Preface
- Who Should Read This Book
- How to Read This Book
- Typographical and Grammatical Conventions
- Acknowledgments
- Permissions
- Chapter 1: Introduction
- 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.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.2 The character of Lord Peter Wimsey
- 3.3 The methods of Lord Peter Wimsey
- 3.4 Review
- Chapter 4: Professor Solomon
- 4.2 The methods of Professor Solomon
- 4.3 Review
- Chapter 5: Case Studies I
- Chapter 6: Mathematical Problem Solving
- 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.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.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.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.2 Case Study 3
- Chapter 11: The Way of the Safety Expert
- 11.2 Worldview of the safety expert
- 11.3 Root-cause analysis
- 11.4 Software-defect root causes
- 11.5 Cause-and-event charting
- 11.6 Fault-tree analysis
- 11.7 Review
- Chapter 12: The Way of the Psychologist
- 12.2 Worldview of the psychologist
- 12.3 Models of human cognition
- 12.4 Defining and classifying human error
- 12.5 Explaining error causes
- 12.6 Research review
- 12.7 Review
- Chapter 13: The Way of the Engineer
- 13.2 Worldview of the engineer
- 13.3 Classifying errors by development stage
- 13.4 Avoiding errors by development stage
- 13.5 Avoiding errors by coding conventions
- 13.6 Building debugging infrastructure
- 13.7 Review
- Chapter 14: The Way of the Computer Scientist
- 14.2 The worldview of the computer scientists
- 14.3 Classifying errors by linguistic formalism
- 14.4 Detecting programming errors by linguistic formalism
- 14.5 Static-analysis tools
- 14.6 Dynamic-analysis tools
- 14.7 Analysis comparison
- 14.8 Review
- Chapter 15: Get Back to Work
- 15.1 Review the methods
- 15.2 Measure your work
- 15.3 Visit our Web site
- Glossary
- C
- D
- E
- F
- H
- I
- P
- R
- S
- T
- Appendix A: Root-Cause Checklist
- A.2 Coding errors
- Appendix B: Books about Debugging
- Appendix C: Software Recommendations
- C.2 Static and Dynamic Analysis
- References
- Object-Oriented Development Techniques
- Prototyping
- Peer Review Methods
- Diagramming Methods
- Testing
- Program Analysis
- Data Structures and Algorithms
- Robust Data Structures
- Miscellany
- Books about Supporting Disciplines Literary Detectives
- Mathematical Problem Solving
- Engineering
- Root Cause Analysis
- Psychology of Human Error
- Books about Thinking Skills
- Experimental Psychology and Debugging
- Index
- Index_B
- Index_C
- Index_D
- Index_E
- Index_F
- Index_G
- Index_H
- Index_I
- Index_K
- Index_L
- Index_M
- Index_N
- Index_O
- Index_P
- Index_Q
- Index_R
- Index_S
- Index_T
- Index_U
- Index_V
- Index_W
- List of Tables
Debugging by Thinking: A Multidisciplinary Approach (HP Technologies)
ISBN: 1555583075
EAN: 2147483647
EAN: 2147483647
Year: 2002
Pages: 172
Pages: 172
Authors: Robert Charles Metzger
Similar book on Amazon
- Chapter II Information Search on the Internet: A Causal Model
- Chapter V Consumer Complaint Behavior in the Online Environment
- Chapter XIV Product Catalog and Shopping Cart Effective Design
- Chapter XVII Internet Markets and E-Loyalty
- Chapter XVIII Web Systems Design, Litigation, and Online Consumer Behavior