Issue 11861: Explanation in section 7.3 hard to read (marte-ftf) Source: THALES (Mr. Sebastien Demathieu, sebastien.demathieu(at)thalesgroup.com) Nature: Clarification Severity: Significant Summary: Section 7.3 is very important to understand how to use of MARTE stereotypes in the following chapter. However, the explanation given here is hard to read. I would suggest rephrasing this specific paragraph. Resolution: Rephrase the paragraph conveniently. Revised Text: Replace the paragraph: As stated before, this chapter does not define concrete extensions to UML, but it collects a number of primitive modeling concepts to be use in the domain models of other chapters in this specification. Nevertheless all further concepts defined in this specification may adopt the nature of Classifier or Instance presented here, and this is made according to: their definition, the purpose of the annotation, and the intended semantics. In many cases these concepts are represented in UML by a stereotype annotation on a concrete UML modeling element. When this is the case, the Classifier or Instance intrinsic nature of the UML annotated element may define the corresponding nature, semantics, or concrete variations of the MARTE concept that is intended to be represented with the annotation. As a consequence, explicit different semantics may be defined for each MARTE modeling concept whether it is annotated on an instance or on a classifier; the differentiation is then straightforward, since it is dependent directly on the fundamental nature of the corresponding UML element that is annotated. By: As stated before, this chapter does not define concrete extensions to UML offered as stereotypes to the user. Instead it collects a number of primitive modeling concepts to be use in the domain models of other chapters in this specification. Nevertheless, a certain impact on the representation of modeling elements is envisioned according to their classifier/instance dual nature. The modeling elements defined in this specification may adopt the nature of Classifier or Instance presented here, or both. This quality of being may be of course specifically stated as part of their definition, but it may be also left to the user to be decided according to the purpose of the annotation, and the intended semantics. In most of the cases the concepts defined in the domain view are proposed to be represented in UML by means of a stereotype extending a concrete UML modeling element. When this is the case, the Classifier or Instance intrinsic nature of the UML annotated element may lead to identify the corresponding nature, semantics, or concrete variations of the MARTE concept that is intended to be represented with the annotation. Hence, the explicit different semantics that may be defined for each MARTE modeling concept, when it is considered as an instance or as a classifier, may be inferred directly from the fundamental nature of the corresponding UML element that is annotated. Actions taken: December 21, 2007: received issue February 17, 2010: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 21 Dec 2007 13:17:25 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Sébastien Demathieu Company: Thales mailFrom: sebastien.demathieu@thalesgroup.com Notification: Yes Specification: UML profile for MARTE Section: 7 FormalNumber: 07-08-04 Version: Beta 1 RevisionDate: 08/2007 Page: 29 Nature: Clarification Severity: Significant HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11 Description Section 7.3 is very important to understand how to use of MARTE stereotypes in the following chapter. However, the explanation given here is hard to read. I would suggest rephrasing this specific paragraph.