Issue 12233: Correct the inconsistency between the diagram and the text (marte-ftf) Source: Thematix Partners LLC (Mr. Lonnie VanZandt, lonniev(at)gmail.com) Nature: Revision Severity: Minor Summary: Sentence 1, paragraph 2, on page 295 begins: BEGINQUOTE "GaTimingObserver" specializes "NfpConstraint", and the latter extends UML Constraints... ENDQUOTE However, Figure 16.8, page 295, expresses that GQAM::GaTimingObs [sic] extends not specializes MARTE::NFPs::NfpConstraint. Several recommendations follow: 1. Correct the inconsistency between the diagram and the text. I suspect that the text should say "extends" rather than "specializes". 2. Consistently name the element GQAM::GaTimingObserver. 3. In text which refers to elements, always use a qualified name--it need not be fully qualified when there is a common parent scope in effect for the context of the text--and never use quoted "nicknames" or, worse, arbitrary alternate, similar names. 4. Replace the cited paragraph entirely with a paragraph which describes the Schedulability Analysis Module's profile and which isn't suspiciously similar to a cut-n-paste from the related GQAM material. 5. If Timing Observers move to a more common subprofile outside of GQAM, then refactor this section appropriately. Resolution: Revise figures and text according to the following considerations (each numbered point is related to the corresponding numbered item above): 1. Update figures with the Specialization relationship instead of the Extension relationship between NfpConstraint and GaTimedObserver. This has to be done in both Chapters GQAM and SAM, and in both sections Domain View and UML Representation View. Also, in Figure 16.5, the association ends startObs and endObs are not valid anymore. In the FTF1, they have changed by startEvent and endEvent respectively. 2. GQAM::GaTimingObserver is an old name that was changed in FTF1 by the name GQAM::GaTimedObserver. This has to be updated in all figures and text throughout Chapter SAM. 3. Edit all incorrect aliases for GQAM::GaTimedObserver appropriately. Never use quoted "nicknames". The affected section is only Section 16.3.1. 4. The cited paragraph doesn’t exist elsewhere in the MARTE specification. 5. Timed Observers have not been moved to a more common sub-profile. So, no additional modifications are required. Revised Text: see ptc/2009-05-12 pages 176 - 179 Actions taken: February 15, 2008: received issue October 16, 2009: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 15 Feb 2008 23:31:08 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Lonnie VanZandt Company: ARTiSAN Software mailFrom: lonnievz@artisansw.com Notification: Yes Specification: MARTE Section: 16 FormalNumber: ptc/07-08-04 Version: beta 1 RevisionDate: 08/04/07 Page: 295 Nature: Revision Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; InfoPath.2; .NET CLR 1.1.4322; .NET CLR 3.0.590) Description Sentence 1, paragraph 2, on page 295 begins: BEGINQUOTE "GaTimingObserver" specializes "NfpConstraint", and the latter extends UML Constraints... ENDQUOTE However, Figure 16.8, page 295, expresses that GQAM::GaTimingObs [sic] extends not specializes MARTE::NFPs::NfpConstraint. Several recommendations follow: 1. Correct the inconsistency between the diagram and the text. I suspect that the text should say "extends" rather than "specializes". 2. Consistently name the element GQAM::GaTimingObserver. 3. In text which refers to elements, always use a qualified name--it need not be fully qualified when there is a common parent scope in effect for the context of the text--and never use quoted "nicknames" or, worse, arbitrary alternate, similar names. 4. Replace the cited paragraph entirely with a paragraph which describes the Schedulability Analysis Module's profile and which isn't suspiciously similar to a cut-n-paste from the related GQAM material. 5. If Timing Observers move to a more common subprofile outside of GQAM, then refactor this section appropriately. Date: Tue, 4 Mar 2008 13:27:43 -0500 (EST) From: Murray Woodside Reply-To: cmw@sce.carleton.ca To: marte-ftf@omg.org Subject: Need for Timing Observer The need for the timing observer was noted in the original RFP for Marte, as a mechanism for identifying and attaching parameters to point-to-point delays, between an arbitrarily selected pair of events. There was enough discussion at that time to be sure that UML2 does not provide a suitable other mechanism. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca