Rapid Development

Errata for Rapid Development




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 41

Clarification needed On page 41, the first two sentences of the Heroics section require clarification. Change: "Some software developers place a high emphasis on project heroics (Bach 1995). But I think that they do more harm than good." To: "Some developers place a high emphasis on project heroics and think that the certain kinds of heroics can be beneficial (Bach 1995). But I think that emphasizing heroics in any form usually does more harm than good."

Microsoft Press  May 06, 2010 
Printed
Page 55

project should be product On page 55, the second sentence of theEstimation and Scheduling section refers to a project rather than a product. Change: "They first estimate the size of the project, then they estimate the effort needed to build a product of that size, and then they estimate a schedule based on the effort estimate." To: "They first estimate the size of the product, then they estimate the effort needed to build a product of that size, and then they estimate a schedule based on the effort estimate."

Microsoft Press  Jul 13, 2010 
Printed
Page 60

Clarification needed On page 60, the first sentence after Figure 4-2 is inaccurate. Change: "This is the same kind of chart that I presented in the"Classic Mistakes” chapter, and it describes the same lesson." To: "This is the same chart that I presented in the "Classic Mistakes" chapter, and it provides a specific example of the general classic mistakes lesson."

Microsoft Press  May 06, 2010 
Printed
Page 128

6-10 should be 6-11 On page 128, the second sentence after Figure 6-11 refers to Figure 6-10 rather than 6-11. Change: "Look at how much of the curve in Figure 6-10 is to the right of the planned-schedule line on typical projects." To: "Look at how much of the curve in Figure 6-11 is to the right of the planned-schedule line on typical projects."

Microsoft Press  Jul 13, 2010 
Printed
Page 168

Label Error On page 168, in Figure 8-2, the upper graph labels on the right hand side are mixed up. From top to bottom, the graph labels should read as follows: " 1.6x 1.25x 1.15x 1.1x 1.0x 0.9x 0.85x 0.8x 0.6x "

Microsoft Press  May 06, 2010 
Printed
Page 186

Additional clarification needed On page 186, the first sentence of the Efforts section requirs additional clarification. Change: "The efforts are given in developer man-months to two or three significant digits." To: "The efforts are given in development-team man-months (including management and QA) to two or three significant digits"

Microsoft Press  Jul 13, 2010 
Printed
Page 572

20.2 should be 21.2 On page 572, the first cross-reference refers to thw wrong section. Change: "For more on using prototyping time effectively, see"Inefficient use of prototyping time” in Section 20.2." To: "For more on using prototyping time effectively, see"Inefficient use of prototyping time” in Section 21.2."

Microsoft Press  May 06, 2010 
Printed
Page 613

Add Citation The following citation should be added to page 613. DeMarco, Tom. 1995. Why Does Software Cost So Much? Dorset House.

Microsoft Press  Jul 13, 2010 
Printed
Page 618

January should be September On page 618, the bibliography entry for Millington, Don, and Jennifer Stapleton contains an incorrect month. Change: "Millington, Don, and Jennifer Stapleton. 1995."Developing a RAD Standard.” IEEE Software, January: 54–55." To: "Millington, Don, and Jennifer Stapleton. 1995."Developing a RAD Standard.” IEEE Software, September: 54–55."Microsoft Press is committed to providing informative and accurate books. All comments and corrections listed above are ready for inclusion in future printings of this book. If you have a later printing of this book, it may already contain most or all of the above corrections.

Microsoft Press  May 06, 2010