UML 2.0 in a Nutshell by Dan Pilone, Neil Pitman 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 : important language/formatting problem (page-number): language change or minor formatting problem ?page-number?: reader question or request for clarification This page was updated May 23, 2008. UNCONFIRMED errors and comments from readers: [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." {36} First paragraph in section "Database Schemas"; "By mapping [...] table rows to attributes" should probably read "By mapping [...] table columns to attributes". [55] Figure 4-14; The <> 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 <>: "A usage dependency denoting that the client classifier creates instances of the supplier classifier." [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: {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 [169] Figure 11-6; EJBPrimaryKey stereotype model repeats the tagged values of EJBCmpField instead of introducing SequenceName and AutoGenerated. (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) ...