Issue 11619: Section: 14/2 (marte-ftf) Source: THALES (Mr. Sebastien Demathieu, sebastien.demathieu(at)thalesgroup.com) Nature: Revision Severity: Minor Summary: In HRM, a stereotype called HwResource is used in the HwLogical subpackage to provide a logical representation of a hardware resource. At the same time, a stereotype with the name is used in the HwPhysical subpackage to provide a physical representation of a hardware resource. Although it is legal in this context, defining two stereotypes with the same names that have different semantics may create confusion in a user's mind. I would suggest renaming HwResource into HwLogicalResource / HwPhysicalResource. The same thing applies for HwLogical::HwResourceService and HwPhysical::HwResourceService. Resolution: Revised Text: Actions taken: October 16, 2007: received issue February 17, 2010: closed issue Discussion: HwLogical and HwPhysical both address the issue of hardware modeling, proposing two different abstraction levels for hardware modeling. It means that if two stereotypes (one defined in each package) have the same name, they do not fundamentally differ from a semantic view point. They just reflect a level of detail that is consistent with the abstraction level that is addressed by the package. In this context, it is not necessary to define a particular name for each stereotype. This remark concerns both HwResource and HwReso End of Annotations:===== m: webmaster@omg.org Date: 16 Oct 2007 08:45:04 -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: 14/2 FormalNumber: realtime/07-08-04 Version: Beta 1 RevisionDate: 08/2007 Page: 223 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 In HRM, a stereotype called HwResource is used in the HwLogical subpackage to provide a logical representation of a hardware resource. At the same time, a stereotype with the name is used in the HwPhysical subpackage to provide a physical representation of a hardware resource. Although it is legal in this context, defining two stereotypes with the same names that have different semantics may create confusion in a user's mind. I would suggest renaming HwResource into HwLogicalResource / HwPhysicalResource. The same thing applies for HwLogical::HwResourceService and HwPhysical::HwResourceService.