Issue 17443: SysML Issue Lower bounds on multiplicity not consistent with diagram (sysml-rtf) Source: Lockheed Martin (Mr. Michael Jesse Chonoles, michael_chonoles2(at)omg.org) Nature: Uncategorized Issue Severity: Summary: In SysML 1.3 11.3.1.1 Activity constraints “The lower multiplicity at the part end must be zero.” The diagram above Figure 11.1 on the previous page does not indicate 0 as the lower end. The default for a composition relationship at the part end is 1..1 and does not include 0. However, as you fix the diagram consider eliminating the constraint 3. I believe this constraint has been eliminated from UML 2.5 (in the works). The proper constraint is something like. (Conrad will know what’s in the UML spec). If the part end action starts running when the parent activity is started, and continues until the parent activity is ended, then the minimum multiplicity is non-zero. Otherwise, the lower multiplicity at the part end must be zero. Whether the constraint is fixed or not, the diagram must include a lower end of zero. Recommended fix, eliminate the constraint and fix the diagram 11.3.1.4.1 Constraint 3 Similar to above. The BDD in Figure 11.5 would need to explicitly be marked to allow for 0. This constraint was not changed in UML. Recommend the diagram be fixed Resolution: Revised Text: Actions taken: June 18, 2012: received issue Discussion: End of Annotations:===== te: Mon, 18 Jun 2012 13:29:12 +0000 From: "Chonoles, Michael J" Subject: SysML Issue Lower bounds on multiplicity not consistent with diagram X-Originating-IP: [158.186.156.95] To: "issues@omg.org" , "sysml-rtf@omg.org" Thread-Topic: SysML Issue Lower bounds on multiplicity not consistent with diagram Thread-Index: Ac1NVaypsV0P12vfTvee0weg+ar2DA== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.260,0.0.0000 definitions=2012-06-18_01:2012-06-18,2012-06-18,1970-01-01 signatures=0 In SysML 1.3 11.3.1.1 Activity constraints .The lower multiplicity at the part end must be zero.. The diagram above Figure 11.1 on the previous page does not indicate 0 as the lower end. The default for a composition relationship at the part end is 1..1 and does not include 0. However, as you fix the diagram consider eliminating the constraint 3. I believe this constraint has been eliminated from UML 2.5 (in the works). The proper constraint is something like. (Conrad will know what.s in the UML spec). If the part end action starts running when the parent activity is started, and continues until the parent activity is ended, then the minimum multiplicity is non-zero. Otherwise, the lower multiplicity at the part end must be zero. Whether the constraint is fixed or not, the diagram must include a lower end of zero. Recommended fix, eliminate the constraint and fix the diagram 11.3.1.4.1 Constraint 3 Similar to above. The BDD in Figure 11.5 would need to explicitly be marked to allow for 0. This constraint was not changed in UML. Recommend the diagram be fixed Michael Jesse Chonoles LMCO