I've read this book from cover to cover. I've read many books on software development, software processes, best practices, qualitative approaches, and quantitative approaches, many from SEI. This book has to be one of the top two. For software professionals in leadership positions facing today's pre
Automated Defect Prevention: Best Practices in Software Management
β Scribed by Dorota Huizinga, Adam Kolawa
- Publisher
- Wiley-IEEE Computer Society Pr
- Year
- 2007
- Tongue
- English
- Leaves
- 454
- Edition
- 1
- Category
- Library
No coin nor oath required. For personal study only.
β¦ Synopsis
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.
π SIMILAR VOLUMES
I had a chance to read this book thanks to lots of snow here in the Mid-Atlantic region. It is easy to read, with good examples. There were some very useful graphics and charts throughout the book. Chapter 3 on economics was good, but could have been better, and I wish there were more case studie
This practical, hands-on guide captures, categorizes, and builds a process of best practices to help avoid creating defects during the development processβrather than fixing them after extensive analysis. While there are various proprietary and competing standards for reducing software defects, thes
This book is a result of the European Experience Exchange (EUREX) project sponsored by the European Systems and Software Initiative for Software Best Practice in Europe. The EUREX project analyzed the industrial and economic impact and the similarities and differences between and among more than 300
<p>This book is a result of the European Experience Exchange (EUREX) project sponsored by the European Systems and Software Initiative for Software Best Practice in Europe. The EUREX project analyzed the industrial and economic impact and the common aspects and differences between and among more tha