At a Glance; Contents; About the Author; About the Technical Reviewer; Acknowledgments; Introduction; Chapter 1: Introduction; 1.1 Software Quality, Software Reviews and Inspections; 1.2 About This Book; 1.2.1 Organization of This Book; 1.2.2 Intended Audience and How to Use This Book; 1.3 References; Chapter 2: Software Review Procedures; 2.1 A Generic Software Review Procedure; 2.2 Fagan Inspection and Extensions; 2.2.1 Fagan Inspection; 2.2.2 Extensions to Fagan Inspection; 2.2.2.1 Meeting or No Meeting; 2.2.2.2 What Is the Right Team Size?; 2.2.2.3 Other Extensions

2.3 Active Design Review and Extensions2.3.1 Active Design Review; 2.3.2 Extensions to the Active Design Review; 2.4 Other Types of Reviews; 2.5 Factors Impacting Software Reviews; 2.6 Summary; 2.7 References; Chapter 3: Basic Software Reading Techniques; 3.1 Introduction to Software Reading; 3.1.1 Definition of Software Reading; 3.1.2 Purposes of Software Reading; 3.1.3 Taxonomy of Software Reading Techniques; 3.2 Ad hoc Reading; 3.3 Checklist-Based Reading; 3.3.1 Checklist Definition, Types, and Examples; 3.3.2 Checklists with Guidance; 3.3.3 Best Practices of Checklists

3.3.4 Empirical Experiences3.4 Differential Reading; 3.5 Summary; 3.6 References; Chapter 4: Scenario-Based Reading Techniques; 4.1 Principles of Scenario-Based Reading; 4.2 Defect-Based Reading; 4.2.1 Taxonomy of Defects in Requirements Specifications; 4.2.2 Defect-Based Reading Techniques; 4.2.3 Empirical Experiences; 4.3 Perspective-Based Reading; 4.3.1 A Generic Perspective-Based Reading; 4.3.1.1 Reading Scenarios and Template; 4.3.1.2 Developing Reading Scenarios; 4.3.1.3 Characteristics of Perspective-Based Reading; 4.3.2 Perspective-Based Requirements Reading

4.3.2.1 Reading Scenarios for Requirements Specifications4.3.2.2 Empirical Experiences; 4.3.3 Perspective-Based Design Reading; 4.3.3.1 Reading Scenarios for Design Documents; 4.3.3.2 Empirical Experiences; 4.3.4 Perspective-Based Code Reading; 4.3.4.1 Reading Scenarios for Code Modules; 4.3.4.2 Empirical Experiences; 4.3.5 Perspective-Based Usability Reading; 4.3.5.1 Reading Scenarios for Usability; 4.3.5.2 Empirical Experiences; 4.3.6 Why Does Perspective-Based Reading Work?; 4.3.6.1 Cognitive Analysis of Perspective-Based Reading; 4.3.6.2 An Analytical Model

4.4 Alternative Partitioning of Reading Responsibilities4.4.1 Ad hoc Partition; 4.4.2 Function Point-Based Partition; 4.5 Summary; 4.6 References; Chapter 5: Requirements Reading Techniques; 5.1 Critical Roles of Requirements in Software Development; 5.2 A Combined Reading Technique for Requirements; 5.2.1 Motivations for a Combined Reading; 5.2.2 The Combined-Reading Technique; 5.2.3 Empirical Experiences; 5.3 Test-Case Driven Reading for Requirements; 5.3.1 Test-Case-Driven Reading Technique; 5.3.2 Empirical Experiences; 5.4 Individual Factors Impacting Requirements Reading Efficiency