Errata for UML in a Nutshell

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

now reads SubSpace.

now reads "Classes".

now reads "Type".

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.

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

now reads "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.

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

now reads getStartDate.

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

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.

class now reads create () : Resource

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.

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

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.

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

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

misspelled now read Startup.

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

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)}.

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.

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

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

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.

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

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

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

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.

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.

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.

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.

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.

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.

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

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

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

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.

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

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

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.

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.

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