SOFTWARE QUALITY BOOK EXCERPTS
Automated Defect Prevention: Best Practices in Software Management, Chapter 1 -- The Case for Automated Defect Prevention
Dorota Huizinga and Adam Kolawa
11.15.2007
Rating: -5.00- (out of 5)
As a registered member of SearchSoftwareQuality.com, you're entitled to a complimentary copy of Chapter 1 of Automated Defect Prevention: Best Practices in Software Management written by Dorota Huizinga and Adam Kolawa and published by Wiley IEEE Computer Society Press. "The Case for Automated Defect Prevention" describes this technique and where it fits in with software development. ADP was adapted from an approach used by software vendor Parasoft and is best suited to an iterative development process. This and every chapter contains a basic glossary.
Book description:
This book describes an approach to software management based on establishing an infrastructure that serves as the foundation for the project. This infrastructure defines people roles, necessary technology, and interactions between people and technology. This infrastructure automates repetitive tasks, organizes project activities, tracks project status, and seamlessly collects project data to provide measures necessary for decision making. Most importantly, this infrastructure sustains and facilitates the improvement of human-defined processes.
The methodology described in the book, which is called Automated Defect Prevention (ADP) stands out from the current software landscape as a result of two unique features: its comprehensive approach to defect prevention, and its far-reaching emphasis on automation. ADP is a practical and thorough guide to implementing and managing software projects and processes. It is a set of best practices for software management through process improvement, which is achieved by the gradual automation of repetitive tasks supported and sustained by this flexible and adaptable infrastructure, an infrastructure that essentially forms a software production line.
In defining the technology infrastructure, ADP describes necessary features rather than specific tools, thus remaining vendor neutral. Only a basic subset of features that are essential for building an effective infrastructure has been selected. Many existing commercial and non-commercial tools support these, as well as more advanced features. Appendix E contains such a list.
>> Read Chapter 1: The Case for Automated Defect Prevention.
>> Buy the book
|
|
Rate this Tip
|
To rate tips, you must be a member of SearchSoftwareQuality.com.
Register now
to start rating these tips. Log in if you are already a member.
|
 |
 |
| |
RELATED CONTENT
 |
Software Quality Book Excerpts |
|
Perfect Software, Ch. 8: What Makes a Good Test
|
|
Seven Steps to Mastering Business Analysis, Ch. 1
|
|
Clean Code: A Handbook of Agile Software Craftsmanship, Chapter 1 -- What Is Clean Code?
|
|
The Software Project Manager's Bridge to Agility: Chapter 5, Scope Management
|
|
Software Security Engineering: A Guide for Project Managers -- Chapter 3, Requirements Engineering for Secure Software
|
|
Requirements Management Using IBM Rational RequisitePro: Chapter 1, Requirements Management
|
|
Implementing ITIL Configuration Management: Chapter 3, Determining Scope, Span and Granularity
|
|
Agile Software Development: The Cooperative Game, 2nd Edition -- Chapter 3, Communicating, Cooperating Teams
|
|
Inherent Quality Simplicity, Section V: The Evolution
|
|
Managing the Test People, Chapter 6: Keeping Your Beast Effective
|
|
Methodologies |
|
Clean Code: A Handbook of Agile Software Craftsmanship, Chapter 1 -- What Is Clean Code?
|
|
Agile Software Development: The Cooperative Game, 2nd Edition -- Chapter 3, Communicating, Cooperating Teams
|
|
Inherent Quality Simplicity, Section V: The Evolution
|
|
Outside-in Software Development: A Practical Approach to Building Successful Stakeholder-based Products -- Chapter 1, Introducing Outside-in Development
|
|
The Economics of Open Source Software Development -- Chapter 1, An Introduction
|
|
Model-Driven Software Development: Technology, Engineering, Management -- Chapter 2, MDSD: Basic Ideas and Terminology
|
|
Implementing the IBM Rational Unified Process and Solutions: A Guide to Improving Your Software Development Capability and Maturity -- Chapter 2, Your First Steps
|
|
Scaling Software Agility: Best Practices for Large Enterprises -- Chapter 7, The Essence of Agile
|
|
Real-Life MDA -- Chapter 1, Introduction
|
|
DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.
|
|
|
|
|
|
|
