Issue 18031: Location:  Pg. 613, Figure 17.6 -   Incorrect multiplicities in the metamodel in Figure 17.6 (uml25-ftf)
Source: Lockheed Martin (Mr. Lenny Delligatti, lenny_delligatti2(at)omg.org)
Nature: Revision
Severity: Significant
Summary: The multiplicity shown for both ends named “covered” of type “Lifeline” is “*”.  The multiplicity for both of these ends should be “1” to match the metaclass entries for “OccurrenceSpecification” and “StateInvariant”.  Both entries show that these two metaclasses each have an association “covered : Lifeline [1]”.  And “1” is the intuitively correct multiplicity; an instance of OccurrenceSpecification (e.g. send, receive, start, end, destruction) can only be associated with a single lifeline.  And an instance of StateInvariant is placed on a single lifeline.  

Proposed Resolution:

Change the multiplicity for both of the ends “covered : Lifeline” to “1”.  

Resolution: 
Revised Text: 
Actions taken:
September 27, 2012: received issue
Discussion: 

End of Annotations:=====
s is issue # 18031

Problem: 17.013

Severity:  Significant
Nature:  Contradiction
Location:  Pg. 613, Figure 17.6
Title:  Incorrect multiplicities in the metamodel in Figure 17.6
Summary: 
 
The multiplicity shown for both ends named .covered. of type .Lifeline. is .*..  The multiplicity for both of these ends should be .1. to match the metaclass entries for .OccurrenceSpecification. and .StateInvariant..  Both entries show that these two metaclasses each have an association .covered : Lifeline [1]..  And .1. is the intuitively correct multiplicity; an instance of OccurrenceSpecification (e.g. send, receive, start, end, destruction) can only be associated with a single lifeline.  And an instance of StateInvariant is placed on a single lifeline.  
 
Proposed Resolution:
 
Change the multiplicity for both of the ends .covered : Lifeline. to .1..  
 
Source:         Lenny Delligatti