Software Project Survival Guide

Errata for Software Project Survival Guide




The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Printed
Page ix

Some Material is Review of Rapid Development p. ix. Insert the following text before "Kinds of Projects This Book Covers:" Readers of Rapid Development [B head] If you read Rapid Development, the first part of this book will be about half review for you. Skim Chapters 1 through 5, read the end of Chapter 5 carefully, skim Chapter 6, and then begin reading carefully with Chapter 7.

Microsoft Press  May 06, 2010 
Printed
Page 14

Typographical Error Page 14, question 19: Change: "annonymously" To: "anonymously"

Microsoft Press  Jul 13, 2010 
Printed
Page 32

Typographical Error Page 32, paragraph 1, sentence 2: Change: "...that will need to made..." To: "...that will need to be made..."

Microsoft Press  May 06, 2010 
Printed
Page 45

Incorrect Text Page 45, first line: Change: "relatively" To: "relativity"

Microsoft Press  Jul 13, 2010 
Printed
Page 122

Change In Wording Page 122, paragraph 4, sentence 1: Change: "...under configuration management,..." To: "...under change control,..."

Microsoft Press  May 06, 2010 
Printed
Page 149

Typographical Error Page 149, paragraph 4, sentence 1: Change: "...reuse data, detailed designs, text cases,..." To: "...reuse data, detailed designs, test cases,..."

Microsoft Press  Jul 13, 2010 
Printed
Page 203

Error in Recommended Integration Procedure Table Page 203, Table 14-1: Renumber table as follows: #1 - #5 - as printed in book Developer informally turns code over to testing for test case preparation. Code is reviewed. Developer fixes any problems identified during the review. Fixes are reviewed. Developer integrates final code with the main build. Code is declared "complete"...

Microsoft Press  May 06, 2010 
Printed
Page 205

Comment Regarding Footnote The footnote for Table 14-2 is incorrect as printed, but will become correct as printed once the change on p. 203 is made.

Microsoft Press  Jul 13, 2010 
Printed
Page 265

Incorrect Citations Page 265, notes for pages 60, 61, 62, and 64: Change citations for "Relationships, Models and Management Rules" to: _Manager's Handbook for Software Development, Revision 1_, SEL-84-101, Revision 1, NASA Software Engineering Laboratory, Goddard Space Flight Center, Greenbelt, MD, November 1990.

Microsoft Press  May 06, 2010