Includes bibliographical references and index.

1. The Case for Automated Defect Prevention -- 2. Principles of Automated Defect Prevention -- 3. Initial Planning and Infrastructure -- 4. Requirements Specification and Management -- 5. Extended Planning and Infrastructure -- 6. Architectural and Detailed Design -- 7. Construction -- 8. Testing and Defect Prevention -- 9. Trend Analysis and Deployment -- 10. Managing External Factors -- 11. Case Study: Automation as an Agent of Change -- Appendix A. A Brief Survey of Modern Software Development Process Models -- Appendix B. Mars Polar Lander (MPL): Loss and Lessons by Gordon Hebert -- Appendix C. Service-Oriented Architecture: Example of an Implementation with ADP Best Practices -- Appendix D. AJAX Best Practice: Continuous Testing -- Appendix E. Software Engineering Tools.

Print version record.

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.

John Wiley and Sons Wiley Online Library: Complete oBooks