The Road Map to Software Engineering: A Standards-Based Guide
January 2006, Wiley-IEEE Computer Society Press
List of Tables.
PART I: BACKGROUND.
Chapter 1. Introduction.
Chapter 2. Standards-Makers.
Chapter 3. Principles of the S2ESC Collection.
Chapter 4. Organizing a Standards Collection.
PART II: A KNOWLEDGE-ORIENTED VIEW.
Chapter 5. Overview of the Software Engineering Body of Knowledge.
Chapter 6. Knowledge Area: Software Requirements.
Chapter 7. Knowledge Area: Software Design.
Chapter 8. Knowledge Area: Software Construction.
Chapter 9. Knowledge Area: Software Testing.
Chapter 10. Knowledge Area: Software Maintenance.
Chapter 11. Knowledge Area: Software Configuration Management.
Chapter 12. Knowledge Area: Software Engineering Management.
Chapter 13. Knowledge Area: Software Engineering Process.
Chapter 14. Knowledge Area: Software Engineering Tools and Methods.
Chapter 15. Knowledge Area: Software Quality.
Chapter 16. Related Disciplines.
Chapter 17. Other IEEE Software Engineering Standards.
PART 3: A PROCESS-ORIENTED VIEW.
Chapter 18. History and Concepts.
Chapter 19. Software Life Cycle Processes.
Chapter 20. System Life Cycle Processes.
Appendix A: Standards Described in This Book.
Appendix B: Abbreviations and Acronyms.
- Provides software engineer professionals with a book whose topical organization assists readers in finding "gaps" in their own knowledge areas and addressing those gaps by consulting the normative literature
- Provides students and their instructors with a compendium of "industrial-strength" approaches set in the context of the knowledge a student should seek to attain.
"Moore's book is exactly what his title says...consider it a valuable index and commentary—the Cliff Notes" for IEEE standards." (CHOICE, June 2006)
"For readers who want a book about standards and how they can be used in a software engineering context, this is the book to have." (Software Quality Professional, June 2006)
"...an excellent source for [software engineering practitioners]...helping them to locate the standards pertinent to questions they face in real projects." (Computing Reviews.com, May 22, 2006)