| |
| |
| List of Figures | |
| |
| |
| List of Tables | |
| |
| |
| Preface | |
| |
| |
| Overview And Basics | |
| |
| |
| Overview | |
| |
| |
| Meeting People's Quality Expectations | |
| |
| |
| Book Organization and Chapter Overview | |
| |
| |
| Dependency and Suggested Usage | |
| |
| |
| Reader Preparation and Background Knowledge | |
| |
| |
| Problems | |
| |
| |
| What Is Software Quality? | |
| |
| |
| Quality: Perspectives and Expectations | |
| |
| |
| Quality Frameworks and ISO-9126 | |
| |
| |
| Correctness and Defects: Definitions, Properties, and Measurements | |
| |
| |
| A Historical Perspective of Quality | |
| |
| |
| So, What Is Software Quality? Problems | |
| |
| |
| Quality Assurance | |
| |
| |
| Classification: QA as Dealing with Defects | |
| |
| |
| Defect Prevention | |
| |
| |
| Education and training | |
| |
| |
| Formal method | |
| |
| |
| Other defect prevention techniques | |
| |
| |
| Defect Reduction | |
| |
| |
| Inspection: Direct fault detection and removal | |
| |
| |
| Testing: Failure observation and fault removal | |
| |
| |
| Other techniques and risk identification | |
| |
| |
| Defect Containment | |
| |
| |
| Software fault tolerance | |
| |
| |
| Safety assurance and failure containment | |
| |
| |
| Concluding Remarks | |
| |
| |
| Problems | |
| |
| |
| Quality Assurance in Context | |
| |
| |
| Handling Discovered Defect During QA Activities | |
| |
| |
| QA Activities in Software Processes | |
| |
| |
| Verification and Validation Perspectives | |
| |
| |
| Reconciling the Two Views | |
| |
| |
| Concluding Remarks | |
| |
| |
| Problems | |
| |
| |
| Quality Engineering | |
| |
| |
| Quality Engineering: Activities and Process | |
| |
| |
| Quality Planning: Goal Setting and Strategy Formation | |
| |
| |
| Quality Assessment and Improvement | |
| |
| |
| Quality Engineering in Software Processes | |
| |
| |
| Concluding Remarks | |
| |
| |
| Problems | |
| |
| |
| Software'testing | |
| |
| |
| Testing: Concepts, Issues, and Techniques | |
| |
| |
| Purposes, Activities, Processes, and Context | |
| |
| |
| Questions About Testing | |
| |
| |
| Functional vs. Structural Testing: What to Test? | |
| |
| |
| Coverage-Based vs. Usage-Based Testing: When to Stop Testing? | |
| |
| |
| Concluding Remarks | |
| |
| |
| Problems | |
| |
| |
| Test Activities, Management, and Automation | |
| |
| |
| Test Planning and Preparation | |
| |
| |
| Test planning: Goals, strategies, and techniques | |
| |
| |
| Testing models and test cases | |
| |
| |
| Test suite preparation and management | |
| |
| |
| Preparation of test procedure | |
| |
| |
| Test Execution, Result Checking, and Measurement | |
| |
| |
| Analysis and Follow-up | |
| |
| |
| Activities, People, and Management | |
| |
| |
| Test Automation | |
| |
| |
| Concluding Remarks | |
| |
| |
| Problems | |
| |
| |
| Coverage and Usage Testing Based on Checklists and Partitions | |
| |
| |
| Checklist-Based Testing and Its Limitations | |
| |
| |
| Testing for Partition Coverage | |
| |
| |
| Some motivational examples | |
| |
| |
| Partition: Concepts and definitions | |
| |
| |
| Testing decisions and predicates for partition coverage | |
| |
| |
| Usage-Based Statistical Testing with Musa's Operational Profiles | |
| |
| |
| The cases for usage-based statistical testing | |
| |
| |
| Musa OP: Basic ideas | |
| |
| |
| Using OPs for statistical testing and other purposes | |
| |
| |
| Constructing Operational Profiles | |
| |
| |
| Generic methods and participants | |
| |
| |
| OP development procedure: Musa-1 | |
| |
| |
| OP development procedure: Musa-2 | |
| |
| |
| Case Study: OP for the Cartridge Support Software | |
| |
| |
| Background and participants | |
| |
| |
| OP development in five steps | |
| |
| |
| Metrics collection, result validation, and lessons learned | |
| |
| |
| Concluding Remarks | |
| |
| |
| Problems | |
| |
| |
| Input Domain Partitioning and Boundary Testing | |
| |
| |
| Input Domain Partitioning and Testing | |
| |
| |
| Basic concepts, definitions, and terminology | |
| |
| |
| Input domain testing for partition and boundary problems | |
| |
| |
| Simple Domain Analysis and the Extreme Point Combination Strategy | |
| |
| |
| Testing Strategies Based on Boundary Analysis | |
| |
| |
| Weak N x 1 strategy | |
| |
| |
| Weak 1 x 1 strategy | |
| |
| |
| Other Boundary Test Strategies and Applications | |
| |
| |
| Strong and approximate strategies | |