Issue 14173: At the start of page 224, a 'Flow' is defined that goes to="id.47" from="id.44". This should be conditional ('FalseFlow' (kdm-rtf) Source: Open Canarias, SL (Mr. E. Victor Sanchez, vsanchez(at)opencanarias.com) Nature: Revision Severity: Minor Summary: At the start of page 224, a 'Flow' is defined that goes to="id.47" from="id.44". This should be conditional ('FalseFlow'), since 'WITH TEST AFTER' is not used in the 'PERFORM' statement. This would be consistent with the 'FalseFlow' defined in 'id.64'. Suggestion: Move 'id.64' up to before the loop starts (after id.44) and remove the unconditional 'Flow' from 'id.44'. This improves action element arrangement with respect to their associated Cobol code snippets. Also, action elements corresponding to Cobol statements subordinated to the inline PERFORM appear at the same indentation level as action element 'id.64'. If this action element is indeed moved up, those dependent action elements should probably become part of its 'codeElement' children. Resolution: Revised Text: Actions taken: August 3, 2009: received issue Discussion: According to this spec(P64), "Package" is subclass of Modules. In that case, what is the base class of Module? (CodeItem is superclass of Module. However, CodeItem is not original UML base element.) Considering above, it seems this "Package" is different from original UML Package. From my understanding, (I think,) if this spec use the Module, Module is a subclass of Package (which is from original UML), and change the name of "Package", which are shown in Page 64 and Page 66, to "Container" (something like that). Disposition: Deferred End of Annotations:===== m: webmaster@omg.org Date: 03 Aug 2009 08:42:47 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Victor Sanchez Company: Open Canarias S.L. mailFrom: vsanchez@opencanarias.com Notification: No Specification: Architecture-Driven Modernization (ADM): Knowledge Discovery Meta-Model (KDM) Section: 18.6.5 FormalNumber: ptc/2009-06-05 Version: 1.2 RevisionDate: 06/05/2009 Page: 224 Nature: Revision Severity: Minor HTTP User Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.12) Gecko/2009070812 Ubuntu/8.04 (hardy) Firefox/3.0.12 Description At the start of page 224, a 'Flow' is defined that goes to="id.47" from="id.44". This should be conditional ('FalseFlow'), since 'WITH TEST AFTER' is not used in the 'PERFORM' statement. This would be consistent with the 'FalseFlow' defined in 'id.64'. Suggestion: Move 'id.64' up to before the loop starts (after id.44) and remove the unconditional 'Flow' from 'id.44'. This improves action element arrangement with respect to their associated Cobol code snippets. Also, action elements corresponding to Cobol statements subordinated to the inline PERFORM appear at the same indentation level as action element 'id.64'. If this action element is indeed moved up, those dependent action elements should probably become part of its 'codeElement' children.