UML in a Nutshell

Errata for UML 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. 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 16
2nd Paragraph

The sentence The results of a project are know as deliverables or work products should read The results of a project are known as deliverables or work products

Anonymous   
Printed
Page 27
Figure 2-7

SubsSpace should read SubSpace

Anonymous   
Printed
Page 27
Figure 2-7 The word Subsparc in the dashed rectangle

now reads SubSpace.

Anonymous    Apr 01, 1999
Printed
Page 54
Figure 3-9: The word "Objects" in the right-most dashed rectangle

now reads "Classes".

Anonymous    Jan 01, 1999
Printed
Page 56
Figure 3-11: The word "Types" in the right-most dashed rectangle

now reads "Type".

Anonymous    Jan 01, 1999
Printed
Page 63
Bottom of page:

The following should be appended as a third-level bullet after the third-level bullet on page 64 that reads "- Methods focus on the implementation..." A class has responsibilities that define the purpose, obligations, or required capabilities of the class by virtue of the semantics of the class. To satisfy its responsibilities, a class offers various services as determined by a contract. Services are functions or means through which a class satisfies its obligations. A contract is an agreement between a class and other classes. An operation specifies or provides a declarative description (interface/what) of a service/contract or one construct thereof; that is, an interface declares (specifies) a contract. A method realizes or provides a definition (implementation/how) of a service/contract or one construct thereof; that is, an implementation represents one concrete realization of the contract.

Anonymous   
Printed
Page 74
Figure 4-3: There are two "Remove Activity" in the lower

left of the diagram. The second (lower) "Remove Activity" now reads "Update Activity".

Anonymous    Jan 01, 1999
Printed
Page 78
Figure 4-7: Detailed Project Class Diagram: the top-left class

(labeled "Resource") changed to "Project".

Anonymous    Dec 01, 1998
Printed
Page 78
Figure 4-7: The "Resource" class in the upper left of the diagram

now reads "Project".

Anonymous    Jan 01, 1999
Printed
Page 78
Figure 4-7 The setName : (Name : String) operation of the Project

class now reads setName (Name : String) without the colon following the operation name. The getStartData operation of the Project class now reads getStartDate. The getStartData operation of the Activity class now reads getStartDate. The getStartData operation of the Task class now reads getStartDate.

Anonymous    Apr 01, 1999
Printed
Page 78
In Figure 4-7, the setDeliverable (Delv : Integer) operation

of the Activity class now reads setDeliverable (Delv : String) Also, the getDeliverable () : Integer operation of the Activity class now reads getDeliverable () : String In addition, the setDeliverable (Delv : Integer) operation of the Task class now reads setDeliverable (Delv : String) Finally, the getDeliverable () : Integer operation of the Task class now reads getDeliverable () : String

Anonymous    Oct 01, 1999
Printed
Page 80
Figure 4-8 The getStartData operation of the Work Effort class

now reads getStartDate.

Anonymous    Apr 01, 1999
Printed
Page 80
In Figure 4-8, the setDeliverable (Delv : Integer) operation of

the Activity class now reads setDeliverable (Delv : String) Also, the getDeliverable () : Integer operation of the Activity class now reads getDeliverable () : String

Anonymous    Oct 01, 1999
Printed
Page 81
Figure 4-9 The setName : (Name : String) operation of the Skill

class now reads setName (Name : String) without the colon following the operation name. The setDesc : (Desc : String) operation of the Skill class now reads setDesc (Desc : String) without the colon following the operation name. The setName : (Name : String) operation of the Resource class now reads setName (Name : String) without the colon following the operation name. The setProf : (Prof : enum {Expert, Novice}) operation of the Resource-Skill class now reads setProf (Prof : enum{Expert, Novice}) without the colon following the operation name. The setYearsExpr : (YearsExpr : Real) operation of the Resource-Skill class now reads setYearsExpr (YearsExpr : Real) without the colon following the operation name. The setSalary : (Salary : Real) operation of the Salaried class now reads setSalary (Salary : Real) without the colon following the operation name. The setRate : (Rate : Real) operation of the Hourly class now reads setRate (Rate : Real) without the colon following the operation name.

Anonymous    Apr 01, 1999
Printed
Page 81
In Figure 4-9, the create () : Skill operation of the Resource

class now reads create () : Resource

Anonymous    Oct 01, 1999
Printed
Page 82
Figure 4-10 The setName : (Name : String) operation of the Skill

class now reads setName (Name : String) without the colon following the operation name. The setDesc : (Desc : String) operation of the Skill class now reads setDesc (Desc : String) without the colon following the operation name. The setName : (Name : String) operation of the Resource class now reads setName (Name : String) without the colon following the operation name. The setProf (Prof : enum {Expert, Novice} operation of the Resource-Skill class now reads setProf (Prof : enum {Expert, Novice}) with a closing parentheses.

Anonymous    Apr 01, 1999
Printed
Page 90
Figure 4-19: The "Find 1st Activity ("Scope")" message just above the

"Find 2nd Activity ("AnalysisDesign")" message now reads "Remove 1st Activity ("Scope")" (In other words, changed "Find" to "Remove".

Anonymous    Jan 01, 1999
Printed
Page 96
Figure 4-26

Message sequence number 1.3 now reads 1.5. Message sequence number 1.4 now reads 1.3. Message sequence number 1.5 now reads 1.4.

Anonymous    Jan 01, 1999
Printed
Page 98
Figure 4-28 Message sequence number 2.1 / 1.3 now reads 2.2 / 1.3

Anonymous    Apr 01, 1999
Printed
Page 99
Figure 4-29 Message sequence number 1.8 / 2.9 now reads 1.9 / 2.9

A new Message: 2.17 / 1.18 : Backup 2nd ("Test") Task Data has been added after message sequence number 2.16 / 1.17.

Anonymous    Apr 01, 1999
Printed
Page 101
Figure 4-31 Startup Backup System / Disable P&RMS Backup Utilities

now reads Shutdown Backup System / Disable P&RMS Backup Utilities

Anonymous    Apr 01, 1999
Printed
Page 101
In Figure 4-31, three occurrences of the word Statrup were

misspelled now read Startup.

Anonymous    Oct 01, 1999
Printed
Page 106
At the bottom of the page,

The term 'project' references the Project class of an Activity object... Now reads The term 'project' references the Project class object of or linked with an Activity object...

Anonymous    Oct 01, 1999
Printed
Page 107
In Figure 4-37, the {forAll (t1, t2 | t1<>t2 implies

t1.activity=t2.activity implies) t1.Number<>t2.Number()} constraint string now reads {allInstances->forAll (t1, t2 | t1<>t2 implies t1.activity=t2.activity implies t1.Number<>t2.Number)}.

Anonymous    Oct 01, 1999
Printed
Page 112
Third paragraph

Associations relate classes, and links relate objects, as depicted in Figure 5-1 using ... should read Associations relate classes, and links relate objects, as depicted in Figure 5-2 using ... Also the Figure 5-1 in the next sentence should also read Figure 5-2.

Anonymous   
Printed
Page 135
Bottom of page, added the following first-level (non-nested) bullet to

the end of the Type-Instance Correspondence section: "The stereotype of an instancelike element must match the stereotype of its typelike element (Chapter 15).".

Anonymous    Jan 01, 1999
Printed
Page 144
In the middle of the page, the following first-level (non-nested)

bullets should be added to the middle of the Types section: "Types ... May have an attribute compartment." "Types ... May have associations." "Types ... May have operations."

Anonymous   
Printed
Page 146
In Figure 7-7, the bind is a dependency association rather than

a realizes generalization relationship. That is, it is now denoted as a dashed arrow with an open arrowhead rather than a large hollow triangle arrowhead.

Anonymous    Oct 01, 1999
Printed
Page 148
At the bottom of the page,

Attributes ...Must have an equal sign... Now reads Attributes ...May have an equal sign...

Anonymous    Oct 01, 1999
Printed
Page 164
Middle of page

"If the actor simply participates in the use case..." now reads "If the actor initiates the use case ...".

Anonymous    Jan 01, 1999
Printed
Page 174
At the top of the page, the following second-level (nested)

bullet was added to the Messages section, at the beginning of the "May be synchronous (Figure 9-7)" bullet: "Are denoted as filled solid arrowheads.".

Anonymous    Oct 01, 1999
Printed
Page 174
In the middle of the page,

The return message may be omitted since it is implicit at the end of an activation, or it may be shown on the message line. Now reads The return message may be omitted since it is implicit at the end of an activation, or it may be shown on the message line as a dashed arrow with a stick arrowhead.

Anonymous    Oct 01, 1999
Printed
Page 174
In the middle of page the following second-level (nested)

bullet was added to the Messages section, at the beginning of the "May be asynchronous (Figure 9-8)" bullet: Are denoted as half stick arrowheads.

Anonymous    Oct 01, 1999
Printed
Page 184
In the middle of the page, the following second-level (nested)

bullet was added to the Message Flows section, at the beginning of the "May be simple (Figure 10-7)" bullet: Are denoted as stick arrowheads.

Anonymous    Oct 01, 1999
Printed
Page 184
At the bottom of the page, the following second-level (nested)

bullet was added to the Message Flows section, at the beginning of the "May be synchronous (Figure 10-8)" bullet: Are denoted as filled solid arrowheads.

Anonymous    Oct 01, 1999
Printed
Page 185
In the middle of the page, the following second-level (nested)

bullet was added to the Message Flows section, at the beginning of the "May be asynchronous (Figure 10-9)" bullet: Are denoted as half stick arrowheads.

Anonymous    Oct 01, 1999
Printed
Page 188

final bullet in top section. This currently reads: May have the various expressions (...) they utilize be expressed using pseudocode or another language. should be: May have the various expressions (...) they utilize expressed using pseudocode or another language.

Anonymous   
Printed
Page 198
Bottom of page

"Actions associated with do events must ..." now reads "Activities associated with do events must ...".

Anonymous    Jan 01, 1999
Printed
Page 200
Bottom of page

"Actions are atomic computational procedures ..." now reads "Actions are atomic (non-interruptible) computational procedures ...".

Anonymous    Jan 01, 1999
Printed
Page 200
Bottom of page

"Activities are nonatomic and ..." now reads "Activities are nonatomic (interruptible) and ...".

Anonymous    Jan 01, 1999
Printed
Page 206
6th Bullet

May have the various expressions (conditions, etc) they utilize be expressed using pseudocode or another language. should be: May have the various expressions (conditions, etc) they utilize expressed using pseudocode or another language.

Anonymous   
Printed
Page 213
In the middle of the page

Call relationships (Figure 13-4) are associations between components. They are used to model calling dependencies... Now reads Call relationships (Figure 13-4) are associations between components. They are used to model calling or communication dependencies...

Anonymous    Oct 01, 1999
Printed
Page 226
In Table 15-1

<<process>> ... It is a thread with a representation of control (code). Now reads <<process>> ... It is a thread with a representation of control (code), and may be composed of threads.

Anonymous    Oct 01, 1999
Printed
Page 226
Also in Table 15-1, <<realizes>> now reads <<realize>>"

Anonymous    Oct 01, 1999
Printed
Page 226
Also in Table 15-1, <<refinement>> now reads <<refine>>

Anonymous    Oct 01, 1999
Printed
Page 227
And finally, in Table 15-1, the following entry was added

to the Standard Stereotypes table: Subsystem; Package; The package is a subsystem. It has one or more public interfaces and a private implementation that realizes the interfaces. It must have at least one public interface and must not make any of its implementation publicly accessible.

Anonymous    Oct 01, 1999
Printed
Page 243
In the middle of the page,

Expressions ...May be attached to model elements. These expressions specify conditions that must be maintained as true for a model element and its instances. Now reads Expressions ...May be attached to model elements. These expressions specify conditions that must be maintained as true for all instances of the model elements.

Anonymous    Oct 01, 1999
Printed
Page 250-251
At the bottom of page 250,

...the types defined in a model. The features of... Now reads ...the types defined in a model. The OclType type allows access to the meta-level of the model. The features of...

Anonymous    Oct 01, 1999