Learning UML 2.0
by Russ Miles & Kim Hamilton

The unconfirmed error reports are from readers.  They have not yet been 
approved or disproved by the author or editor and represent solely the
opinion of the reader.

Here's a key to the markup:
        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification

This page was updated February 19, 2008.


UNCONFIRMED  errors and comments from readers: 

{2} Tip ;
"i.e" should read "e.g.", that is "(ie. banking)" should read "(e.g. banking)" as banking is not the only specific domain in which UML can be used, it is only an example.


[18] Figure 1-13;
The last sentence of Section 1.7.2.4, Paragraph 3 reads

"The tagged value note is then attached to the stereotyped element using a dotted
line with a circle at the element end, as shown in Figure 1-13. (This example was
adapted from UML 2.0 in a Nutshell [O'Reilly].)"

But Figure 1-13 does not indicate the circle at the element end of the dotted
line. There is an inconsistency here with what the text says and what the diagram
represents.


(30) Box "How Many Use Cases Should Your Model Have?";
The second line of the box contains

"depends on the of the jobs"

where a word seems to be missing.


[68]  Figure 4-6;
 
Words on figure are in the following order:
Public, Protected, Package, Private
should be:
Public, Package, Protected, Private
 

{74} Figure 4-12;
The last sentence of the first paragraph on page 75 states "If you want to specify that duplicates are allowed, then you need to use the not unique property, as used on the comments attribute in the BlogEntry class." I believe this is referring to Figure 4-12 on page 74 which has no such attribute. It only has the "ordered" attribute. I think 4-12 needs to add a 2nd attribute to the comments attribute called "not unique".


[87] On the second line of the BlogEntry Class;
The class is missing an attribute entry for the BlogEntry Class. The line under the attribute 'name' should contain the following:

private String contents;


(93)  Example 5-4 caption;
"...implementation of the play() operation..." should read "...implementation of the
store(...) and retrieve(...) operations..."


(128) Figure 7-20;
The ref sequence fragment "Select Account Type" should read, "Select Blog Account Type"



[247]  Figures B-4 and B-5 with others following.;
Figures B-4, B-5, B-6 and B-8 have examples of Tagged Values.  However in each of
them the dashed line from the folded rectangle does not end in a circle at the
element as was specified in the final paragraph of p17 and has been acknowledged as
an existing error in figure 1-13.