Errata

Print Print Icon

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 "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



Version Location Description Submitted By Corrected
Printed Page 20
1st paragraph, which continues from the previous page;

"Figure 2-6 shows a specific class for each of the three objects shown earlier in Figures 2-4 and 2-5."

NOW READS:
"Figure 2-6 shows a specific object for each of the three classes shown earlier in Figures 2-4 and 2-5."

 Anonymous  Nov 2003
Printed Page 30
In the diagram

The link from Falcon:project - Execute - :Team
has an triangle pointing from Falcon:project to :Team
It should be pointing from :Team to Falcon:project

 Anonymous 
Printed Page 31
Header of third paragraph

"A communicate association" should read "A communication association"

(First Edition, July 2003)

 Anonymous 
Printed Page 31
paragraph under A dependency relationship

"...to a suppler component..."
should read:
"...to a supplier component..."

 Anonymous 
Printed Page 33
Indented portion of the first full paragraph on page 33

"When creating a project, a project managers use a user interface..."
Should be:
"When creating a project, a project manager uses a user interface..."

 Anonymous 
Printed Page 35
Figure 2-21

3:Enter Manager Name
should be
3:Enter Project Name

 Anonymous 
Printed Page 35
Figure 2-21

Figure 2-21 IS NOW LABELED "Collaboration diagram".

 Anonymous  Nov 2003
Printed Page 36
Figure 2-22

Figure 2-22 IS NOW LABELED "State diagram".

page 191
http://www.klasse.nl/ocl/index.htm

NOW READS:
http://www.klasse.nl/ocl/index.html

page 219
"followingsteps"

NOW READS:
"following steps"

 Anonymous  Nov 2003
Printed Page 66
Last paragraph, under section heading "Rolenames"

In paragraph discussing 'link end rolenames', an incorrect example is used.
Specifically, the example discusses 'association name' instead of 'rolename' and the
two are not the same.
The first sentence states "A link end's rolename must match its association end's
rolename". So far, so good.

Then the paragraph continues, stating "The specific association used is
ResponsibleFor..." and contiunes explaining the association name.

The example should be changed to match the subject of the paragraph and section.
Since the only rolenames shown on Figure 3-19 are "input" and "output", the example
should probably discuss how the ProblemStatement is seen as an input to the Project
and the System is seen as an output of the system.

 Anonymous 
Printed Page 159
figure 8-4

The following changes should be made to Figure 8-4:

"Enters Report Criteria" should be "Enters Data"
"System Generates Report" should be "System Generates Information"
"Printer Prints Report" should be "Printer Prints Information'

 Anonymous