Errata

Learning UML 2.0

Errata for Learning UML 2.0

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
Page 27
Figure 2-8 caption

"explicitly showning" should read "explicitly showing"

 Anonymous    Sep 01, 2007
Printed
Page 33
3rd paragraph

"...connection to the Author Contact Details Database actor." should read
"...connection to the Author Credentials Database actor."

 Anonymous    Sep 01, 2007
Printed
Page 33
2nd paragraph

"use case at the head of the dotted arrow" should read "use case at the tail of the
dotted arrow"

 Anonymous    Sep 01, 2007
Printed
Page 41
1st paragraph

"...starting point to for the rest..." should read "...starting point for the
rest..."

 Anonymous    Sep 01, 2007
Printed
Page 47
Figure 3-4

The Dry action is contained in a non-rounded rectangle. It should be contained in a
rounded rectangle.

 Anonymous   
Printed
Page 48
4th sentence

The text says [wordCount >= 100] --- it should say [wordCount >= 1000]

 Anonymous    Sep 01, 2007
Printed
Page 49
Last paragraph

"...workflow can by sped up..." should read "...workflow can be sped up..."

 Anonymous    Sep 01, 2007
Printed
Page 53
Figure 3-14

The activity name reads "Prepared motherboard"
It should read "Prepare motherboard"

 Anonymous   
Printed
Page 62
Figure 3-27

The dash-lined rectangle should be rounded.

 Anonymous   
Printed
Page 69
3rd paragraph

"...if you want allow specialized..." should read "...if you want to allow
specialized..."

 Anonymous    Sep 01, 2007
Printed
Page 82
Design Pattern sidenote

"Another great example of when static attributes and operations are used when you
want to..." should read "Another great example of when static attributes and
operations are used is when you want to..."

 Anonymous    Sep 01, 2007
Printed
Page 82
4th paragraph

"...diagram type that loosly shows..." should read "...diagram type that loosely
shows..."

 Anonymous    Sep 01, 2007
Printed
Page 87
Figure 5-5 caption

"...is associated with an Author..." should read "...is associated with a
Category..."

 Anonymous    Sep 01, 2007
Printed
Page 89
"Note" on generalization

the last sentence reads
"Although it's true to say that a guitarist is a musician, it is not true to say that all guitarists are musicians."

While this statement might in fact be true, it does not show the meaning of generalization - as is intended, so I assume it should actually read:

"Although it's true to say that a guitarist is a musician, it is not true to say that all musicians are guitarists."

(change positions of musicians and guitarists)

 Anonymous    Sep 01, 2007
Printed
Page 131
2nd paragraph

"...for an interaction can take place." should read, "...for an interaction to take place."

 Anonymous    Sep 01, 2007
Printed
Page 135
1st paragraph

"When the guard condition evaluates to true..." should read, "If the guard condition evaluates to true..."

 Anonymous    Sep 01, 2007
Printed
Page 135
Figure 8-7 caption

"a. messageB() will be invoked..." should read, "2a. messageB() will be invoked..."

 Anonymous    Sep 01, 2007
Printed
Page 159
Figure 9-16 caption

"...sequence diagram's major participant's..." should read, "...sequence diagram's major participants..."

 Anonymous    Sep 01, 2007
Printed
Page 219
Figure 14-14

"entry/unshealth sword" should read "entry/unsheath sword"

 Anonymous   
Printed
Page 219
Figure 14-15

"entry/unshealth sword" should read "entry/unsheath sword"

 Anonymous   
Printed
Page 219
Figure 14-16

"entry/unshealth sword" should read "entry/unsheath sword"

 Anonymous