Testing Computer Software
Author: Cem Kaner
This book will teach you how to test computer software under real-world conditions. The authors have all been test managers and software development managers at well-known Silicon Valley software companies. Successful consumer software companies have learned how to produce high-quality products under tight time and budget constraints. The book explains the testing side of that success.
Who this book is for:
* Testers and Test Managers
* Project Managers-Understand the timeline, depth of investigation, and quality of communication to hold testers accountable for.
* Programmers-Gain insight into the sources of errors in your code, understand what tests your work will have to pass, and why testers do the things they do.
* Students-Train for an entry-level position in software development.
What you will learn:
* How to find important bugs quickly
* How to describe software errors clearly
* How to create a testing plan with a minimum of paperwork
* How to design and use a bug-tracking system
* Where testing fits in the product development process
* How to test products that will be translated into other languages
* How to test for compatibility with devices, such as printers
* What laws apply to software quality
IEEE
I enjoyed reading Testing computer software. The text contains numerous highlights Offering practical advice, authoritative figures you can cite to customers and higher management, and entertaining anecdotes to share with coworkers Although some sections need updating, I still think it is a valuable training and reference source for software testers, managers, and developers.
Database & Network Journal
Deep insight and a great deal of experience is contained in this book.2000
Booknews
Covers some 400 types of software errors and how to cope with last minute changes; detect design errors in the user interface; set priority strategies; estimate, plan, and schedule tests; manage test groups--hiring, avoiding traps, dealing with outside testing companies. Annotation c. Book News, Inc., Portland, OR (booknews.com)
Table of Contents:
| Preface | ||
| Notes on the book's structure and layout | ||
| Acknowledgments | ||
| Sect. 1 | Fundamentals | |
| 1 | An example test series | 1 |
| 2 | The objectives and limits of testing | 17 |
| 3 | Test types and their place in the software development process | 27 |
| 4 | Software errors | 59 |
| 5 | Reporting and analyzing bugs | 65 |
| Sect. 2 | Specific Testing Skills | |
| 6 | The problem tracking system | 87 |
| 7 | Test case design | 123 |
| 8 | Testing printers (and other devices) | 143 |
| 9 | Localization testing | 169 |
| 10 | Testing user manuals | 179 |
| 11 | Testing tools | 189 |
| 12 | Test planning and test documentation | 203 |
| Sect. 3 | Managing Testing Projects and Groups | |
| 13 | Tying it together | 255 |
| 14 | Legal consequences of defective software | 303 |
| 15 | Managing a testing group | 343 |
| Appendix: common software errors | 363 | |
| References | 437 | |
| Index | 451 | |
| About the Authors | 480 |
See also: Curye on Inglysch or Growing and Using Cilantro
The Software Project Manager's Bridge to Agility (Agile Software Development Series)
Author: Michele Sliger
When software development teams move to agile methods, experienced project managers often struggle—doubtful about the new approach and uncertain about their new roles and responsibilities. In this book, two long-time certified Project Management Professionals (PMPRs) and Scrum trainers have built a bridge to this dynamic new paradigm. They show experienced project managers how to successfully transition to agile by refocusing on facilitation and collaboration, not “command and control.”
The authors begin by explaining how agile works: how it differs from traditional “plan-driven” methodologies, the benefits it promises, and the real-world results it delivers. Next, they systematically map the Project Management Institute’s classic, methodology-independent techniques and terminology to agile practices. They cover both process and project lifecycles and carefully address vital issues ranging from scope and time to cost management and stakeholder communication. Finally, drawing on their own extensive personal experience, they put a human face on your personal transition to agile--covering the emotional challenges, personal values, and key leadership traits you’ll need to succeed.
Coverage includes
-
Relating the PMBOKR Guide ideals to agile practices: similarities, overlaps, and differences
-
Understanding the role and value of agile techniques such as iteration/release planning and retrospectives
-
Using agile techniques to systematically and continually reduce risk
-
Implementing quality assurance (QA)where it belongs: in analysis, design, defect prevention, and continuous improvement
-
Learning to trust your teams and listen for their discoveries
-
Procuring, purchasing, and contracting for software in agile, collaborative environments
-
Avoiding the common mistakes software teams make in transitioning to agile
-
Coordinating with project management offices and non-agile teams
-
“Selling” agile within your teams and throughout your organization
For every project manager who wants to become more agile.
Part I An Agile Overview 7
Chapter 1 What is "Agile"? 9
Chapter 2 Mapping from the PMBOKR Guide to Agile 25
Chapter 3 The Agile Project Lifecycle in Detail 37
Part II The Bridge: Relating PMBOKR Guide Practices to Agile Practices 49
Chapter 4 Integration Management 51
Chapter 5 Scope Management 67
Chapter 6 Time Management 83
Chapter 7 Cost Management 111
Chapter 8 Quality Management 129
Chapter 9 Human Resources Management 143
Chapter 10 Communications Management 159
Chapter 11 Risk Management 177
Chapter 12 Procurement Management 197
Part III Crossing the Bridge to Agile 215
Chapter 13 How Will My Responsibilities Change? 217
Chapter 14 How Will I Work with Other Teams Who Aren't Agile? 233
Chapter 15 How Can a Project Management Office Support Agile? 249
Chapter 16 Selling the Benefits of Agile 265
Chapter 17 Common Mistakes 285
Appendix A Agile Methodologies 295
Appendix B Agile Artifacts 301
Glossary 321
Bibliography 327
Index 333
No comments:
Post a Comment