Errata

Building Maintainable Software, C# Edition

Errata for Building Maintainable Software, C# Edition

Submit your own errata for this product.

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, PDF, ePub, Mobi, , Other Digital Version
Page 8
Third donut chart in Figure 1-1

The third donut chart in Figure 1-1 should be the same as the third donut chart on page 26 (Java edition)/page 27 (C# edition), thus with the caption: "unit size quality profile cut-offs for a 4-star system". The cut-offs are thus (from low risk to high risk):
57%
21%
15%
7%

Sylvan Rigal
Sylvan Rigal
 
Aug 04, 2016 
, Printed, PDF, ePub, Mobi, , Other Digital Version
Page 12
Code snippet

Note that since the code snippet on page 12 is an example of a bad practice, it also includes a SQL injection flaw. This is not elaborated upon because the focus of the exercise is to assess the code's maintainability.

Sylvan Rigal
Sylvan Rigal
 
Nov 07, 2016 
Printed, PDF, ePub, Mobi, , Other Digital Version
Page 15
last paragraph

p.15, last paragraph:
Original: "So far our unit contains only 7 lines of code" should be
"So far our unit contains only eight lines of code"

Sylvan Rigal
Sylvan Rigal
 
Jun 08, 2016 
, Printed, PDF, ePub, Mobi, , Other Digital Version
Page 27/42/66/80
Donut chart legend

For clarity and consistency with the threshold tables, the highest categories in the donut chart legends should read:
-Figure 2-2 (Java p.26/C# p.27) should be "61 or more" instead of "61+". The orange category in the second/third charts of this figure should read "31-60" instead of "30-60".
-Figure 3-2 (Java p.40/C# p.42 ) should be "26 or more" instead of "25+"
-Figure 5-1 (Java p.64/C# p.66) should be "7 or more" instead of "7+"
-Figure 6-1 (Java p.76/C# p.80) should be "51 or more" instead of "51+"

Sylvan Rigal
Sylvan Rigal
 
Nov 07, 2016 
Printed, PDF, ePub, Mobi, , Other Digital Version
Page 38
Last line of paragraph below code snippet

p.38, Last line of paragraph below code snippet
Original: "The developer much choose" should be
"The developer must choose"

Sylvan Rigal
Sylvan Rigal
 
Jun 08, 2016 
Printed, PDF, ePub, Mobi, , Other Digital Version
Page 40
code snippet

Note that on p.40 (ยง3.2) we purposely leave the +else+ line in the code snippet to improve code analyzability (that is, removing the +else+ line would not change the code's behavior).

The effect of this added line should be marginal to the actual code maintainability. Also, for the sake of consistency we apply the same coding style as in the code snippet before refactoring.

Sylvan Rigal
Sylvan Rigal
 
Jun 08, 2016 
Printed, PDF, ePub, Mobi, , Other Digital Version
Page 59
Second code snippet

P.59, second, refactored code snippet: the following line:

Point position = r.Position;

is superfluous since the position variable is not used in the unit.

Sylvan Rigal
Sylvan Rigal
 
Jun 08, 2016 
Page 64
1st paragrash

The second sentence is:
"Six of the seven parameters of drawBarChart have been turned into of BarChart class."

I believe you mean "a" instead of "of".
As in "...turned into a BarChart class."


Note from the Author or Editor:
This is correct

Anonymous  Jul 22, 2021 
Printed, PDF, ePub, Mobi, , Other Digital Version
Page 83
Figure 7.1

P.83, figure 7.1
The right title is erroneously the same as the left one.
It should read:
Highly coupled components: hard to change in isolation.

Sylvan Rigal
Sylvan Rigal
 
Jun 08, 2016 
Printed, PDF, ePub, Mobi, , Other Digital Version
Page 120
first paragraph

...assumes that if the hour of the day on a 24-hour clock is lower than 6 p.m., it is night
-->This should be "lower than 6:00, it is night"

Sylvan Rigal
Sylvan Rigal
 
Mar 12, 2018