UML in a Nutshell
by Sinan Si Alhir


Here are the changes made in the 10/99 reprint:


(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


(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


(81) In Figure 4-9, the create () : Skill operation of the Resource 
     class now reads create () : Resource


(101) In Figure 4-31, three occurrences of the word Statrup were 
      misspelled now read Startup.


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


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


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


(148) At the bottom of the page, 

	Attributes ...Must have an equal sign...

Now reads

	Attributes ...May have an equal sign... 


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


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


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


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


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


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


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


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


(226) Also in Table 15-1, <<realizes>> now reads <<realize>>" 


(226) Also in Table 15-1, <<refinement>> now reads <<refine>> 


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


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


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