Issue 11620: Section: 15/3 (marte-ftf) Source: THALES (Mr. Sebastien Demathieu, sebastien.demathieu(at)thalesgroup.com) Nature: Revision Severity: Minor Summary: The stereotype <<gaEventTrace>> defines stereotype attributes: content, format, location that are not defined in the domain model (p. 263). I would suggest adding a definition of these attributes in the EventTrace domain class. Resolution: Add definitions to the text of the domain model Revised Text: para 3 p 263, before: One of these options is used and the others are undefined. The arrivalPattern alternatives are described elsewhere, but they include PeriodicPattern, often used for schedulability, and Open and Closed patterns often used for performance analysis, and a variety of less regular patterns. after: In practice, one of these options is used and the others are left undefined. The arrivalPattern alternatives are described in Appendix D, but they include the PeriodicPattern, often used for schedulability, the Open and Closed patterns often used for performance analysis, and some less regular patterns. EventTrace has attributes for location (the file location or URL), format (a description of the trace record format) and content (for the trace data itself). Actions taken: October 16, 2007: received issue February 17, 2010: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 16 Oct 2007 09:45:26 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Sébastien Demathieu Company: Thales mailFrom: sebastien.demathieu@thalesgroup.com Notification: Yes Specification: A UML Profile for MARTE Section: 15/3 FormalNumber: realtime/07-08-04 Version: Beta 1 RevisionDate: 08/2007 Page: 271 Nature: Revision Severity: Minor HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7 Description The stereotype <> defines stereotype attributes: content, format, location that are not defined in the domain model (p. 263). I would suggest adding a definition of these attributes in the EventTrace domain class.