Errata

Errata for UML 2.0 in a Nutshell

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.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version	Location	Description	Submitted by	Date submitted
Printed	Page Back Cover First paragraph, line 3	The sentence after the question mark states: The Universal Modeling Language (UML) ... correct sentence should read The Unified Modeling Language (UML) ...	Anonymous
Printed	Page 6 2nd paragraph	The third sentence reads... "Conceptually, composite structure diagrams link... they don't emphasize... or the implementation detail that composite structures do." It should read... "Conceptually, composite structure diagrams link... they don't emphasize... or the implementation detail that component diagrams do."	Anonymous
Printed	Page 36 First paragraph in section "Database Schemas"	"By mapping [...] table rows to attributes" should probably read "By mapping [...] table columns to attributes".	Anonymous
Printed	Page 55 Figure 4-14	The <<create>> dependency is pointing in the wrong direction. See the official UML Superstructure 07-11-02 document page 190, Figure 9.27 for a very similar example. Also, from page 694, regarding <<create>>: "A usage dependency denoting that the client classifier creates instances of the supplier classifier."	Anonymous
Printed	Page 57 2nd paragraph	It says "any other classifier may be used ...as long as it can provide the message font" but there is no message or font in the example.	Christopher Nelson	Mar 08, 2014
Printed	Page 100 Figure 8.17	There is a transition from Message Queued to Sender Approved which skips sender validation. I realize this is a simplified diagram, but it is either wrong or over simplified. It could be corrected by either moving the MAIL FROM transition out of Message Queued into the choice or removing it and adding a spontaneous transition from Message Queued to Connected. That would likely also require allowing Connected to handle QUIT.	Christopher Nelson	Mar 14, 2014
Printed	Page 106 In fig. 9-3	In the figure it shows some pseudocode for calculating the final invoice total. It does this by adding up each item and then multiplying the subtotal by the tax rate. However the tax is not only added onto the one item added it is also added onto the previously added items also and therefore compounds the tax that is applied.	Anonymous	Jan 07, 2011
Printed	Page 144 See below - obtained from Errata page (image not found)	The following link, from the Errata page, does not appear to work. No image is displayed:	Anonymous
Printed	Page 144 Figure 10-22	Figure 10-22 is incorrect. The correct figure 10-22 can be found here - http://examples.oreilly.com/9780596007959/ch10-figure022.png	Anonymous
Printed	Page 169 Figure 11-6	EJBPrimaryKey stereotype model repeats the tagged values of EJBCmpField instead of introducing SequenceName and AutoGenerated.	Anonymous
PDF	Page 198 First example	I think getHonorsStudentselse is a mistake: if self.courseLevel > 4000 then salary > 80000.00 getHonorsStudentselse salary < 80000.00 endif should probably read if self.courseLevel > 4000 then salary > 80000.00 else salary < 80000.00 endif	Anonymous	Oct 21, 2010
ePub	Page 342 Figure 10-21	Many of the sequence diagrams are unreadable in the ePub version.	Anonymous	May 16, 2013
PDF	Page 343 Figure 10-22	Figure 10-22 in the PDF version is absolutely incorrect and doesn't correspond to the text, or the same diagram in the ePub version.	Anonymous	May 16, 2013