Issue 18032: Pg. 613, Clause 17.3.4: Notation (uml25-ftf) Source: Lockheed Martin (Mr. Lenny Delligatti, lenny.delligatti(at)lmco.com) Nature: Uncategorized Issue Severity: Significant Summary: Title: Incomplete grammar for “<lifelineident>” in Clause 17.3.4 Summary: This clause specifies the following grammar for “<lifelineident>”: <lifelineident> ::= ([<connectable-element-name>[‘[‘<selector>‘]’]] [: <class_name>][decomposition]) | ‘self’ “<class_name>”, however, is too restrictive for the type. A lifeline may represent an instance of an Actor, not just an instance of a Class. In fact, the metamodel, as written, allows a lifeline to represent an instance of any type of BehavioredClassifier. Here are the relationships: A lifeline represents 0..1 instances of ConnectableElement. ConnectableElement is a type of TypedElement. TypedElement has an association with 0..1 instances of Type. BehavioredClassifier is a type of Classifier, which is a type of Type. BehavioredClassifier has 4 specializations: Class, Actor, UseCase, and Collaboration. Therefore, any of these 4 subtypes may serve as the type of the connectable element that a lifeline represents. But only 2 of these make sense in the context of a lifeline: Class and Actor. So there are really 2 problems that need to be resolved. Recommendations provided below Proposed Resolution: 1) The grammar for “<lifelineident>” needs to be expanded to allow for an actor to serve as the type of the connectable element that a lifeline represents, and 2) A constraint needs to be introduced to allow only two of the four subtypes of BehavioredClassifier to serve as the type of the connectable element that a lifeline represents. Resolution: Revised Text: Actions taken: September 27, 2012: received issue Discussion: End of Annotations:===== s is issue # 18032 Problem: 17.014 Severity: Significant Nature: Grammar Location: Pg. 613, Clause 17.3.4: Notation Title: Incomplete grammar for .. in Clause 17.3.4 Summary: This clause specifies the following grammar for ..: ::= ([[.[..].]] [: ][decomposition]) | .self. .., however, is too restrictive for the type. A lifeline may represent an instance of an Actor, not just an instance of a Class. In fact, the metamodel, as written, allows a lifeline to represent an instance of any type of BehavioredClassifier. Here are the relationships: A lifeline represents 0..1 instances of ConnectableElement. ConnectableElement is a type of TypedElement. TypedElement has an association with 0..1 instances of Type. BehavioredClassifier is a type of Classifier, which is a type of Type. BehavioredClassifier has 4 specializations: Class, Actor, UseCase, and Collaboration. Therefore, any of these 4 subtypes may serve as the type of the connectable element that a lifeline represents. But only 2 of these make sense in the context of a lifeline: Class and Actor. So there are really 2 problems that need to be resolved. Recommendations provided below Proposed Resolution: 1) The grammar for .. needs to be expanded to allow for an actor to serve as the type of the connectable element that a lifeline represents, and 2) A constraint needs to be introduced to allow only two of the four subtypes of BehavioredClassifier to serve as the type of the connectable element that a lifeline represents. Source: Lenny Delligatti X-Forefront-Antispam-Report: CIP:131.107.125.8;KIP:(null);UIP:(null);IPV:NLI;H:TK5EX14MLTC103.redmond.corp.microsoft.com;RD:autodiscover.service.exchange.microsoft.com;EFVD:NLI X-SpamScore: -10 X-BigFish: VS-10(z21cRzc85fhzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1d7338h1de098h17326ah18c673h1de097h1de096h8275bh8275dhz2fh2a8h668h839hd25hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h1b0ah1bceh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1155h) From: Steve Cook To: Ed Seidewitz , "uml25-ftf@omg.org" CC: "'Manfred R. Koethe' (koethe@88solutions.com)" Subject: RE: Problem with the resolution of Issue 18032 on Ballot 7 Thread-Topic: Problem with the resolution of Issue 18032 on Ballot 7 Thread-Index: Ac6HDL1jFv48+iHVTzuoZZ/8wLMy2wAcJSWA Date: Tue, 23 Jul 2013 08:21:04 +0000 Accept-Language: en-GB, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.166.18.105] X-OriginatorOrg: microsoft.com X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% X-Virus-Scanned: amavisd-new at omg.org 18032 should say .merged with 18748.. Manfred, can you correct this in Ballot 7 before it closes please? I can.t imagine that people would want to change their vote on the basis of this, but we should give them a day to do so. From: Ed Seidewitz [mailto:eseidewitz@ivarjacobson.com] Sent: 22 July 2013 20:01 To: uml25-ftf@omg.org Cc: Steve Cook; 'Manfred R. Koethe' (koethe@88solutions.com) Subject: Problem with the resolution of Issue 18032 on Ballot 7 Importance: High I just noticed that the resolution for Issue 18032 says it is merged with Issue 18746. However, there is I cannot find any Issue 18746 on the FTF issues list. Can we quickly correct this before we close the ballot?