Omg issue Number

Disposition: Resolved

OMG Issue No: 12418

Title: “GQAM Domain view inheritances from GRM”

Source:

Universidad de Cantabria (Dr. Julio Medina, [e-mail])

Summary:

In the GQAM Domain view GQAM::GQAM_Resources::CommunicationHost should inherit from GRM::ResourceTypes::CommunicationMedia, and GQAM::GQAM_Resources::ExecutionHost should inherit from GRM::ResourceTypes::ComputingResource. This said from a conceptual point of view, seems to indicate that also the corresponding elements in the profile should keep this inheritance relationship with the corresponding elements in GRM. The names of attributes should be consistent or at least related semantically to those in GRM. This may required some minor structural changes since in GQAM platform elements include semantics form various elements in GRM like for example the scheduler as well as the processing resource.

Resolution:

Include in GQAM::GQAM_Resources::CommunicationHost the inheritance from GRM::ResourceTypes::CommunicationMedia. And in GQAM::GQAM_Resources::ExecutionHost inheritance from GRM::ResourceTypes::ComputingResource. Correspondingly update the profile, making GQAM::GaExecHost inherit from GRM::ComputingResource, and GQAM::GaCommHost inherit from GRM::CommunicationMedia.

According to issue 11835 already resolved in ballot 2, some attributes in GQAM::GaCommHost are now inherited from GRM::CommunicationMedia, these attributes are:

• bandwidth: NFP_DataTxRate [0..1] capacity of the communication element when applicable.

• packetT: NFP_Duration [0..1] time to transmit the element used as a communication quantum, usually called a packet, the size in bits of this quantum is described by the attribute elementSize.

• blockT: NFP_Duration [0..1] time the communicationMedia is blocked and cannot transmit due to the transmission of one communication quantum.

• transmMode: MARTE_Library::MARTE_DataTypes::TransmModeKind [0..1] defines the transmission mode, one of the following values: {simplex, half-duplex, full-duplex}.

The only difference is in the name of the attribute “bandwith” which is called “capacity” in GQAM. Since both of them represent the same concept one of the two should prevail; “capacity” is preferred as it is more general. As mentioned, this impact previous resolution of issue 11835, and as a duplicated also issue 11842.

Attributes schedPolicy and isPreemptible in SaExecutionHost and SaExecHost are now redundant since they are inherited transitively from Scheduler.

Revised Text:

6. 
   In section 15.3.2.4 add generalization
   

• CommunicationMedia (from MARTE::GRM)

7. 
   In section 15.3.2.4 remove the attributes:
   

• capacity: NFP_DataTxRate [0..1] capacity of the communication element when applicable.

• packetT: NFP_Duration [0..1] time to transmit the element used as a communication quantum, usually called a packet, the size in bits of this quantum is described by the attribute elementSize.

• blockT: NFP_Duration [0..1] time the communicationMedia is blocked and cannot transmit due to the transmission of one communication quantum.

• transmMode: MARTE_Library::MARTE_DataTypes::TransmModeKind [0..1] defines the transmission mode, one of the following values: {simplex, half-duplex, full-duplex}.

8. 
   In section 15.3.2.7 add generalization
   

• ComputingResource (from MARTE::GRM)

9. 
   Change Figure 15.9 to show these inheritances as well as those from scheduler introduced in ballot1, and not to show the removed attributes. Use this:
   

10. 
    In section F10.5 CommunicationHost add generalization
    

• CommunicationMedia (from MARTE::GRM)

11. 
    In section F.10.5 remove attributes: capacity, packetTime, blockingTime, and transmMode
    
12. 
    In section F.10.8 ExecutionHost add generalization
    

• ComputingResource (from MARTE::GRM)

13. 
    Change Figure 15.5 to show these inheritances as well as those from scheduler introduced in ballot1, and not to show the removed attributes, use this:
    

14. 
    Consistently with resolution of Issue 11835 change Figure 10.8 to show the attributes capacity, packetTime, blockingTime, and transmMode in the definition of the CommunicationMedia concept, use this:
    

15. 
    Consistently with resolution of Issue 11835, in the bulleted paragraph aboveFigure 10.8, add a text presenting the attributes:
    

Old Text:
As shown in Figure 10.8, two kinds of CommunicationResources are defined. A communication media has an attribute for defining the size of the elements transmitted; as expected, this definition is related to the resource base clock. For example, if the communication media represents a bus, and the clock is the bus speed, "element size" would be the width of the bus, in bits. If the communication media represents a layering of protocols, "element size" would be the frame size of the uppermost protocol. A communication endpoint acts as a terminal for connecting to a communication media, and it is characterized by the size of the packet handled by the endpoint. This size may or may not correspond to the media element size.
New Text:
As shown in Figure 10.8, two kinds of CommunicationResources are defined. A communication media has an attribute for defining the size of the elements transmitted; as expected, this definition is related to the resource base clock. For example, if the communication media represents a bus, and the clock is the bus speed, "element size" would be the width of the bus, in bits. If the communication media represents a layering of protocols, "element size" would be the frame size of the uppermost protocol. It has also an attribute indicating the capacity of the communication element when it is applicable. For timing evaluations, it holds also the time it takes to transmit the element used as a communication quantum, usually called a packet, the size in bits of this quantum is described by the attribute elementSize. It may have also the specification of the time the communicationMedia is blocked and cannot transmit due to the transmission of one communication quantum, and the transmission mode available (simplex, half-duplex, or full-duplex). A communication endpoint acts as a terminal for connecting to a communication media, and it is characterized by the size of the packet handled by the endpoint. This size may or may not correspond to the media element size.

16. 
    Consistently with resolution of Issue 11835 change Figure 10.14 to show the attributes capacity, packetT, blockT, and transmMode in the stereotype CommunicationMedia, use this:
    

17. 
    In Section 10.3.2.4, on page 101, use “capacity” in this bullet phrase instead of “bandwith”, which is the name used in issue 11835:
    

• capacity: NFP_DataTxRate [0..1] capacity of the communication element when applicablelink.

18. 
    Remove attributes schedPolicy and isPreemptible in section 16.3.2.5 (page 300) and in section F.11.5 (page 611), they are inherited from scheduler.
    

19. 
    Accordingly change figure 16.6 by this:
    

20. 
    And change Figure 16.9 by this:
    

Disposition: Resolved