Issue 6169: 7.4.1 Multiplicity (uml2-superstructure-ftf) Source: SSA (Mr. Arthur Culbertson, nobody) Nature: Uncategorized Issue Severity: Summary: Presentation Options The BNF for the syntax for the multiplicity string seems to have a couple of things wrong. First, the 'lower' is specified as an 'integer' whereas it is specified to be unlimited natural from Notation part. Second, it does not allow for multiplicities to include a uniqueness designation. The first sentence defining the 'multiplicity' non-terminal only contains <order_designator> and does not include <uniqueness-designator>. Also, if both a uniqueness designation and order designation are specified the BNF should probably specify a delimiter (as in Figure 11). Perhaps the following: multiplicity ::= <multiplicity_range> [ '{' <order_designator> | <uniqueness_designator> | {<order_designator> ',' <uniqueness_designator>} '}' ] In addition, the multiplicity specification for Purchase is different between Figure 11 and 12, the former uses a comma to separate ordered and unique and the latter seems to be missing the comma. Resolution: see above Revised Text: Actions taken: September 3, 2003: received issue March 8, 2005: closed issue Discussion: The issue of the correct BNF for Multiplicity is addressed by the resolution to issue 7135. The issuer is incorrect in saying that the Notation part says that lower is specified as an unlimited integer (see text at the bottom of page 42, which explicitly says that lower is an integer). There is indeed an error in Figure 12 that should be corrected as follows: Superstructure resolution: ?? In figure 12 on page 43 add a comma to the constraint on Customer::purchase right after the “ordered” keyword. Infrastructure re solution: ?? In figure 44 on page 74 add a comma to the constraint on Customer::purchase right after the “ordered” keyword. End of Annotations:===== From: "Culbertson, Arthur" To: "'issues@omg.org'" , "'uml2-superstructure-ftf@omg.org'" Subject: UML 2.0 Superstructure Issues (Part I -Structure) Date: Wed, 3 Sep 2003 10:43:47 -0400 X-Mailer: Internet Mail Service (5.5.2654.52) Dear Sirs: The following are some potential issues that I have found while reviewing Part I - Structure portion of the UML 2.0 Superstructure Specification (document pct/03-08-02) dated August 2003. As some of these issues could impact performance on the UML certification exams, I would appreciate feedback as soon as possible. Thanks, Art Culbertson 2) 7.4.1 Multiplicity Presentation Options The BNF for the syntax for the multiplicity string seems to have a couple of things wrong. First, the 'lower' is specified as an 'integer' whereas it is specified to be unlimited natural from Notation part. Second, it does not allow for multiplicities to include a uniqueness designation. The first sentence defining the 'multiplicity' non-terminal only contains and does not include . Also, if both a uniqueness designation and order designation are specified the BNF should probably specify a delimiter (as in Figure 11). Perhaps the following: multiplicity ::= [ '{' | | { ',' } '}' ] In addition, the multiplicity specification for Purchase is different between Figure 11 and 12, the former uses a comma to separate ordered and unique and the latter seems to be missing the comma.