Automated defect prevention [electronic resource] : best practices in software management / Dorota Huizinga, Adam Kolawa.

IT Carlow ebook

IEEE ebook

Includes bibliographical references and index.

Preface. -- Features and Organization. -- Practice Descriptions. -- Intended audience. -- Acknowledgements. -- Permissions. -- Disclaimer. -- 1. The Case for Automated Defect Prevention. -- 1.1 What is ADP? -- 1.2 What are the goals of ADP? -- 1.2.1 People: Stimulated and Satisfied. -- 1.2.2 Product: High Quality. -- 1.2.3 Organization: Increased Productivity and Operational Efficiency. -- 1.2.4 Process: Controlled, Improved, and Sustainable. -- 1.2.5 Project: Managed through Informed Decision Making. -- 1.3 How is ASDP implemented? -- 1.3.1 Principles. -- 1.3.2 Practices. -- 1.3.3 Policies. -- 1.3.4 Defect Prevention Mindset. -- 1.3.5 Automation. -- 1.4 From the waterfall to modern software development process models. -- 1.5 Acronyms. -- 1.6 Glossary. -- 1.7 References. -- 1.8 Exercises. -- 2. Principles of Automated Defect Prevention. -- 2.1 Introduction. -- 2.2 Defect Prevention: Definition and Benefits. -- 2.3 Historical Perspective: Defect Analysis and Prevention in Auto Industry What Happened to Deming? -- 2.4 Principles of Automated Defect Prevention. -- 2.4.1 Principle 1: Establishment of Infrastructure: "Build a strong foundation through integration of people and technology". -- 2.4.2 Principle 2: Application of General Best Practices: "Learn from others mistakes". -- 2.4.3 Principle 3: Customization of Best Practices: "Learn from your own mistakes". -- 2.4.4 Principle 4: Measurement and Tracking of Project Status: "Understand the past and present to make decisions about the future". -- 2.4.5 Principle 5: Automation: "Let the computer do it". -- 2.4.6 Principle 6: Incremental Implementation of ADP s Practices and Policies. -- 2.5 Automated Defect Prevention based Software Development Process Model. -- 2.6 Examples. -- 2.6.1 Focus on Root Cause Analysis of a Defect. -- 2.6.2 Focus on Infrastructure. -- 2.6.3 Focus on Customized Best Practice. -- 2.6.4 Focus on Measurements of Project Status. -- 2.7 Acronyms. -- 2.8 Glossary. -- 2.9 References. -- 2.10 Exercises. -- 3. Initial Planning and Infrastructure. -- 3.1 Introduction. -- 3.2 Initial Software Development Plan. -- 3.2.1 Product. -- 3.2.2 People. -- 3.2.3 Technology. -- 3.2.4 Process. -- 3.3 Best Practices for Creating People Infrastructure. -- 3.3.1 Defining Groups. -- 3.3.2 Determining a Location for Each Group s Infrastructure. -- 3.3.3 Defining People Roles. -- 3.3.4 Establishing Training Program. -- 3.3.5 Cultivating a Positive Group Culture. -- 3.4 Best Practices for Creating Technology Infrastructure. -- 3.4.1 Automated Reporting System. -- 3.4.2 Policy for Use of Automated Reporting System. -- 3.4.3 Minimum Technology Infrastructure. -- 3.4.4 Intermediate Technology Infrastructure. -- 3.4.5 Expanded Technology Infrastructure. -- 3.5 Integrating People and Technology. -- 3.6 Human Factors and Concerns. -- 3.7 Examples. -- 3.7.1 Focus on Developer Ideas. -- 3.7.2 Focus on Reports Generated by the Minimum Infrastructure. -- 3.8 Acronyms. -- 3.9 Glossary. -- 3.10 References. -- 3.

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. T.

Description based on print version record.