Note: Supplemental materials are not guaranteed with Rental or Used book purchases.
- ISBN: 9781420099560 | 1420099566
- Cover: Hardcover
- Copyright: 9/14/2009
Actually looking at software testing as a manufacturing activity rather than a service, this book explains how one can improve productivity by commoditizing software testing. Creating schedules, allocating resources, and managing quality, all normal functions of manufacturing can be applied to software testing. Going beyond that concept, this work serves as a complete handbook for software testing as a business. It looks at different kinds of software testing, strategies, and approaches. It explains how to estimate costs, allocate resources, and make a competitive bid. Providing examples and case histories, the book shows how proper planning can help assure a good return on investment.
Preface | p. xv |
Acknowledgments | p. xvii |
About the Author | p. xix |
Introduction to Software Testing Management | p. 1 |
Product Defect: A Case Study | p. 2 |
Case Analysis | p. 3 |
Return on Investment | p. 4 |
Causes of Defects in Software | p. 5 |
Factors Creating Problems in Software Development Process | p. 7 |
Solutions to Software Development Problems | p. 8 |
Definition of Software Quality | p. 9 |
Definition of Good Design | p. 9 |
Definition of Good Code | p. 10 |
Definition of Testing | p. 11 |
Case Study | p. 11 |
Inputs | p. 11 |
Outputs | p. 12 |
Analysis | p. 12 |
Conclusion | p. 12 |
Software Testing Evolution | p. 13 |
Software Engineering | p. 14 |
Software Testing Methodologies | p. 15 |
Tools | p. 15 |
Test Case Execution Automation | p. 15 |
Test Coverage | p. 16 |
Defect Tracking | p. 16 |
Test Management | p. 16 |
Project Offshoring | p. 16 |
Testing Being Commoditized? | p. 17 |
Conclusion | p. 17 |
Kinds of Software Testing Projects | p. 19 |
Software Testing Types | p. 19 |
What Needs to Be Tested? | p. 23 |
Enterprise System Testing | p. 24 |
Enterprise System Types | p. 25 |
Banking, Finance, Insurance, and Securities (BFSI) Systems | p. 25 |
Enterprise Resource Planning (ERP) Systems | p. 25 |
Desktop System Testing | p. 26 |
Device Driver System Testing | p. 26 |
Stage of Software Life Cycle | p. 27 |
Outsourced Software Testing | p. 27 |
Software Vendor Perspective | p. 27 |
Software Service Provider Perspective | p. 28 |
Performance Testing | p. 28 |
Security Testing | p. 29 |
Software Testing Project Strategies | p. 31 |
Strategy versus Planning | p. 32 |
Complexity Management | p. 32 |
Case Study on Complexity Management | p. 33 |
Module Description | p. 34 |
Strategy | p. 34 |
Complexity | p. 34 |
Problems | p. 35 |
Solution | p. 35 |
Pseudo Logic | p. 35 |
Technology Management | p. 39 |
People Managemenr | p. 40 |
Skills Required | p. 40 |
Risk Factors | p. 41 |
Technological Risks | p. 41 |
Scheduling Risk | p. 42 |
Human Risks | p. 42 |
Strategy for Automation | p. 42 |
Strategy for Manual Testing | p. 43 |
Automation Tool Selection | p. 43 |
Strategy for Creating Automation Framework | p. 43 |
Software Product Life Cycle and Automation | p. 44 |
Test Case Prioritization | p. 46 |
Ad Hoc Testing | p. 46 |
Software Test Project Strategy Checklist | p. 46 |
Challenges | p. 47 |
Conclusion | p. 47 |
Project Effort Estimation | p. 49 |
Estimation by Experience | p. 50 |
Estimation Using Test Point Analysis | p. 51 |
Basic Components of TPA | p. 51 |
ProjectSize | p. 51 |
Test Strategy | p. 52 |
Productivity | p. 52 |
TPA Calculation Details | p. 53 |
Dynamic Test Point Characteristics | p. 53 |
Dynamic Quality Characteristics | p. 54 |
Test Point Calculation | p. 55 |
Productivity Factor | p. 55 |
Primary Test Hours | p. 56 |
Total Number of Test Hours | p. 56 |
Phase Breakdown | p. 57 |
Application of TPA | p. 57 |
TPA at Bidding Stage | p. 57 |
TPA-Based Effort Estimation Implementation | p. 58 |
Identify Test Life Cycle Stages | p. 58 |
Identify Activities for Each Phase | p. 59 |
Size Estimation for Each Phase | p. 59 |
Test Requirement Phase | p. 59 |
Test Case Design Phase | p. 60 |
Test Script Development Phase | p. 60 |
Test Case Execution Phase | p. 61 |
Regression Phase | p. 61 |
Effort Estimation for Each Phase | p. 61 |
Synopsis | p. 62 |
Importance of Effort Estimation | p. 63 |
Practical Advice | p. 63 |
Schedule versus Effort | p. 64 |
Task Elasticity | p. 64 |
Effort Estimation Checklist | p. 66 |
Checklist for Software Test Schedule Estimation | p. 66 |
Checklist for Software Test Effort Estimation | p. 66 |
Challenges | p. 67 |
Software Testing Project Plan | p. 69 |
Test Area Prioritization | p. 70 |
Skill Matching | p. 70 |
Resource Allocation | p. 70 |
Tools Selection | p. 70 |
Methodology Selection | p. 71 |
Sample Project | p. 71 |
Technology | p. 72 |
Infrastructure | p. 72 |
Testing Resources | p. 72 |
Testing Process | p. 73 |
Test Automation | p. 74 |
Steps for Test Case Automation | p. 74 |
Automation Framework | p. 75 |
Test Data Management | p. 75 |
Data Maintenance in Production Environment | p. 75 |
Testing without a Formal Test Plan | p. 76 |
The Drawbacks | p. 77 |
Software Test Plan Checklist | p. 78 |
Test Plan Checklist-Analysis and Review | p. 78 |
Test Plan Checklist-Testing Activities | p. 78 |
Test Plan Checklist-Test Environment | p. 78 |
Test Plan Checklist-Organizarion | p. 79 |
Test Plan Checklist-Test Schedule | p. 79 |
Test Plan Checklist-Test Tools | p. 79. |
Test Plan Checklist-Configuration Management | p. 80 |
Test Plan Checklist-Test Metrics | p. 80 |
Test Plan Checklist-Project Tracking for Unit/Integration Testing | p. 80 |
Test Plan Checklist-Project Tracking for Acceptance Testing | p. 81 |
Test Plan Checklist-Project Tracking for System Testing | p. 81 |
Software Testing Project Risk Management | p. 83 |
Risk Measurement Method | p. 84 |
Create a Scale and Assign a Score to Each Risk | p. 85 |
Count Number of Times the Risk Occurs in the Project | p. 85 |
Risk Analysis Case Study | p. 85 |
Risks Related to the Application Being Tested | p. 86 |
Kinds of Risks | p. 87 |
Communication Risks | p. 87 |
Effectiveness | p. 87 |
Cultural Risks | p. 88 |
Process Risks | p. 88 |
Size | p. 88 |
Challenges | p. 88 |
Checklist for Risk Management | p. 89 |
Software Testing Project Execution | p. 91 |
Earned Value Management | p. 92 |
Need for EVM | p. 93 |
EVM Implementation for Software Projects | p. 94 |
Audit Trail | p. 95 |
Defect Tracking and Life Cycle | p. 95 |
Monitoring of Production Systems | p. 96 |
Test Case Execution | p. 97 |
Checklist for Test Execution | p. 97 |
Software Testing Project Reporting | p. 99 |
Importance of Reporting | p. 100 |
What Should Go in a Report | p. 100 |
Case Study | p. 100 |
Test Report | p. 101 |
Test Report Components | p. 102 |
Acceptance Criteria | p. 103 |
Accessibility Testing | p. 103 |
Status Report | p. 103 |
Blocked Test Cases | p. 103 |
Boundary Value Coverage | p. 103 |
TestCharrer | p. 103 |
Test Bed | p. 104 |
Test Basis | p. 104 |
Test Approach | p. 104 |
Test Metrics | p. 104 |
Metrics and Reports | p. 105 |
Bibliography | p. 106 |
Automated Software Testing Benefits | p. 107 |
Considerations for Automation | p. 109 |
Analysis of Test Case Activities | p. 109 |
Financial and Execution Time Impacts | p. 110 |
Workload Factor | p. 110 |
Test Automation History | p. 111 |
Case Studies | p. 112 |
Business Case 1 | p. 112 |
Wrong Customer Expectations | p. 112 |
Problem Statement | p. 112 |
IssuesFaced | p. 112 |
Solution | p. 113 |
Lessons Learned | p. 113 |
Business Case 2 | p. 113 |
Automation Strategy | p. 113 |
Issues Faced | p. 114 |
Solution | p. 114 |
Lessons Learned | p. 114 |
Business Case 3 | p. 115 |
Tool Selection | p. 115 |
Solution | p. 115 |
Lessons Learned | p. 115 |
Business Case 4 | p. 115 |
Problems | p. 115 |
Solution | p. 116 |
Lesson Learned | p. 116 |
Business Case 5 | p. 116 |
Test Estimation | p. 116 |
IssuesFaced | p. 116 |
Solution | p. 116 |
Lessons Learned | p. 117 |
Business Case 6 | p. 117 |
Technical Issue | p. 117 |
Solution | p. 117 |
Lessons Learned | p. 117 |
Business Case 7 | p. 118 |
New Technology | p. 118 |
IssuesFaced | p. 118 |
Solution | p. 118 |
Keyword-Driven Automation Framework | p. 118 |
Steps for Creating Keyword Framework | p. 119 |
Data-Driven Automated Testing | p. 120 |
Customer Expectation Management | p. 121 |
Difficult Proposition | p. 121 |
Service Level Agreement | p. 122 |
Product Development | p. 123 |
History | p. 123 |
Challenges | p. 125 |
Requirement Analysis | p. 125 |
Project Process Information | p. 126 |
Case Study; Electronics Retailer | p. 127 |
Customer Expectation Management Strategies | p. 127 |
Customer Involvement | p. 127 |
KickoffMeeting | p. 128 |
Get Approval for Delivery Methodology | p. 128 |
Communicate Risks Early | p. 129 |
Commit Less and Deliver More | p. 129 |
Be Cool and Share Lighter Moments | p. 129 |
Stick to SLAs | p. 129 |
Bibliography | p. 130 |
Software Testing Practice and Offshoring | p. 131 |
Challenges | p. 133 |
Customer Concerns | p. 133 |
Commercial Concerns | p. 133 |
Technical and Process Concerns | p. 134 |
Legal Concerns | p. 135 |
Benefits of Offshoring | p. 136 |
Tradirional Approach to Testing | p. 137 |
Cost of Late Detection of Defects | p. 137 |
Proposed Organization Structure | p. 138 |
Process Structure | p. 139 |
Projecr Components | p. 139 |
Infrasrructure | p. 139 |
Tools | p. 139 |
Operating Model | p. 140 |
Organization | p. 140 |
Software Testing Consolidation | p. 140 |
Advantages of Offshoring Coupled with Centralized Quality Group | p. 141 |
Offshore Team Srructure | p. 141 |
Case Study | p. 141 |
The Current State Scenario | p. 142 |
The Future State Scenario | p. 142 |
A 3-Year Labor Cost ROI Scenario | p. 143 |
Challenge | p. 143 |
Solution | p. 143 |
New Model Implementation Details | p. 144 |
Pilot Project Details | p. 144 |
Process Model | p. 145 |
Benefits of New Model | p. 146 |
Productivity | p. 146 |
Quality | p. 146 |
Cost | p. 147 |
Automation Benefits | p. 147 |
Key Highlights | p. 149 |
Sanity Testing | p. 149 |
Software Testing as a Commodity | p. 151 |
Software Offshoring | p. 153 |
The New Concept | p. 153 |
Old Organization Structure | p. 153 |
New Organization Structure | p. 154 |
Linking Test Project with Development Project | p. 157 |
Mass Manufacturing | p. 158 |
Setup | p. 159 |
Idle Time | p. 160 |
Sequencing | p. 160 |
Disassembling | p. 160 |
Aggregation | p. 162 |
Pegging | p. 162 |
Project versus Manufacturing | p. 164 |
Projecr | p. 164 |
Manufacturing | p. 164 |
Mass Servicing of Software Test Projects | p. 165 |
Rework Aspects | p. 165 |
Conclusion | p. 165 |
Quality, Standards, and Software Testing | p. 167 |
Quality | p. 167 |
Standards | p. 168 |
Benchmarking | p. 168 |
Six Sigma | p. 369 |
Software Development Process Quality | p. 169 |
Standards for Software Development Processes | p. 172 |
Requirements | p. 172 |
Software Project Planning | p. 173 |
Software Project Tracking and Oversight | p. 173 |
Software Subcontract Management | p. 173 |
Software Quality Assurance | p. 174 |
Software Testing and Quality | p. 174 |
Quality Standards Evolution | p. 175 |
Bibliography | p. 175 |
IEEE Standard for Software Test Documentation (ANSI/IEEE Standard 829-1983) | p. 177 |
Software Testing Glossary | p. 181 |
Index | p. 213 |
Table of Contents provided by Ingram. All Rights Reserved. |
What is included with this book?
The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.
The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.