Summary

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.

Author Biography

Dorota Huizinga, PhD, is the Associate Dean for the College of Engineering and Computer Science and Professor of Computer Science at California State University, Fullerton. Her publication record spans a wide range of computer science disciplines and her research was sponsored by the National Science Foundation, California State University System, and private industry.

Adam Kolawa, PhD, is the cofounder and CEO of Parasoft, a leading provider of Automated Error Prevention software solutions. Dr. Kolawa is a coauthor of Bulletproofing Web Applications, has contributed to or written more than 100 commentary pieces and technical papers, and has authored numerous scientific papers.

Preface
Features and Organization
Practice Descriptions
Intended audience
Acknowledgements
Permissions
Disclaimer
The Case for Automated Software Defect Prevention
What is ASDP?
What are the goals of ASDP?
People: Stimulated and Satisfied
Product: High Quality
Organization: Increased Productivity and Operational Efficiency
Process: Controlled, Improved, and Sustainable
Project: Managed through Informed Decision Making0
How is ASDP implemented?
Principles
Practices
Policies
Defect Prevention Mindset
Automation
From the waterfall to modern software development process models
Acronyms
Glossary
References
Exercises
Principles of Automated Software Defect Prevention
Introduction
Defect Prevention: Definition and Benefits
Historical Perspective: Defect Analysis and Prevention in Auto Industry - What Happened to Deming?
Principles of Automated Software Defect Prevention
Principle 1: Establishment of Infrastructure: "Build a strong foundation through integration of people and technology"
Principle 2: Application of General Best Practices: "Learn from others? Mistakes"
Principle 3: Customization of Best Practices: "Learn from your own mistakes"
Principle 4: Measurement and Tracking of Project Status: "Understand the past and present to make decisions about the future"
Principle 5: Automation: "Let the computer do it"
Principle 6: Incremental Implementation of ASDP''s Practices and Policies
Automated Defect Prevention based Software Development Process Model
Examples
Focus on Root Cause Analysis of a Defect
Focus on Infrastructure
Focus on Customized Best Practice
Focus on Measurements of Project Status
Acronyms
Glossary
References
Exercises
Initial Planning and Infrastructure
Introduction
Initial Software Development Plan
Product
People
Technology
Process
Best Practices for Creating People Infrastructure
Defining Groups
Determining a Location for Each Group''s Infrastructure
Defining People Roles
Establishing Training Program
Cultivating a Positive Group Culture
Best Practices for Creating Technology Infrastructure
Automated Reporting System
Policy for Use of Automated Reporting System
Minimum Technology Infrastructure
Intermediate Technology Infrastructure
Expanded Technology Infrastructure
Integrating People and Technology
Human Factors and Concerns
Examples
Focus on Developer Ideas
Focus on Reports Generated by the Minimum Infrastructure
Acronyms
Glossary
References
Exercises
Requirements Specification and Management
Introduction
Best Practices for Gathering and Organizing Requirements
Creating the Product Vision and Scope Document
Gathering and Organizing Requirements
Prioritizing Requirements
Developing Use Cases
Creating a Prototype to Elicit Requirements
Creating Conceptual Test Cases
Requirements Documents Inspection
Managing Changing Requirements
Best Practices in Different Environments
Existing Versus New Software Project
In-House Versus Outsourced Development Teams
Policy for Use of the Requirements Management System
The project manager should approve the final version of the vision and scope document, which should be entered into, and tracked in, the requirements management system
The architect should approve the final version of the requirements specification (SRS) document. The requirements from SRS should be entered into, and their changes tracked in, the requirements management system
The architect or lead developer should define the scope and test requirements for each feature to be implemented, and then enter those details in the requirements management system
The developer should crea
Table of Contents provided by Publisher. All Rights Reserved.

Supplemental Materials

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.