Issue 6074: Multiplicities diagram in section 7.4 (uml2-superstructure-ftf)
Source:  (, )
Nature: Clarification
Severity: Minor
Summary: The Multiplicities diagram in section 7.4 defines two associations with ValueSpecification, namely upperValue and lowerValue. However, the constraints stated in section 7.4.1 for MultiplicityElement, are defined in terms of upperBound() and lowerBound()

Resolution: 
Revised Text: 
Actions taken:
August 19, 2003: received issue
March 9, 2005: closed issue
Discussion: 
Discussion:
However, the terms upperBound() and lowerBound() represent auxiliary
operations that reference upperValue and lowerValue respectively. These
functions were necessary to deal with the case where these multiplicities may not
be specified explicitly. There is no problem here.
Disposition: Closed, no change
End of Annotations:=====
From: webmaster@omg.org 
Date: 19 Aug 2003 19:36:20 -0400 
To: <juergen@omg.org> 
Subject: Issue/Bug Report 


--------------------------------------------------------------------------------

Name: Javier Estrada 
Company: DeveloPeer Inc. 
mailFrom: jestrada@developeer.com 
Notification: Yes 
Specification: UML 2.0 Superstructure Final Adopted specification 
Section: 7.4 
FormalNumber: ptc/03-08-02 (UML 2.0 Superstructure Final Adopted specification) 
Version: 2.0 
RevisionDate: 03-08-02 
Page: 40-41 
Nature: Clarification 
Severity: Minor 
HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322) 
Description



OMG Issue No: 6074
Title:	Multiplicities diagram in section 7.4
Source:	
???
Summary:
The Multiplicities diagram in section 7.4 defines two associations with ValueSpecification, namely upperValue and lowerValue. However, the constraints stated in section 7.4.1 for MultiplicityElement, are defined in terms of upperBound() and lowerBound()
Discussion:
However, the terms upperBound() and lowerBound() represent auxiliary operations that reference upperValue and lowerValue respectively. These functions were necessary to deal with the case where these multiplicities may not be specified explicitly. There is no problem here.
Disposition:	Closed, no change
The Multiplicities diagram in section 7.4 defines two associations with ValueSpecification, namely upperValue and lowerValue. However, the constraints stated in section 7.4.1 for MultiplicityElement, are defined in terms of upperBound() and lowerBound()