OMG Issue No: 11520
Title: the property named "isSynchronous" is misspelled
Source:
Commissariat a l Energie Atomique-CEA/LIST (Mr. Yann Tanguy, yann.tanguy@cea.fr)
Summary:
On the stereotype HwBus in the diagram, the property named "isSynchronous" is mispelled ("isSynchrnous").
Resolution:
Proceed in both Domain Model and Profile Definition.
Revised Text:
-Replace Figs. 14-59 and 14-70 with the following:
Figure 14.59 - HW_Communication package details
Figure 14.70 - HwCommunication package details
Disposition: Resolved
Disposition: Resolved OMG Issue No: 11521
Title: Figure 14.70 - HwCommunication package details
Source:
Commissariat a l Energie Atomique-CEA/LIST (Mr. Yann Tanguy, yann.tanguy@cea.fr)
Summary:
Lack of homogeneity in the enumeration litterals naming (considering the rest of the document) : - litteral should start with lowercase - "undef" should be used instead of "undefined"
Resolution:
Proceed in all the figures affected by this issue.
Revised Text:
-Replace Figs. 14-56, 14-57, 14-63, 14-67, 14-68, 14-74, 14-78, 14-81, 14-82 with the following:
(Note that the datatypes were replaced with tupletypes to follow Issue 11632)
Figure 14.56 - HW_Computing package details
Figure 14.57 - HW_Storage package details (HW_Memory)
Figure 14.63 - HW_Layout package details
Figure 14.67 - HwComputing package details
Figure 14.68 - HwMemory package details (HwStorage)
Figure 14.74 - HwLayout package details
Figure 14.78 - Stereotype application example (SDRAM)
Figure 14.81 - SMP physical view
Figure 14.82 - SMP merged (logical/physical) view
-Modify all the Classes and Stereotype descriptions in Sections 14.2.3.2 Stereotype descriptions, and F.9 DRM::HRM, with enumeration literal starting with lowercase in Enumerations, and "undef" instead of "undefined"
Disposition: Resolved
Disposition: Resolved OMG Issue No: 11522
Title: The type NFP_Price does not exist in the document.
Source:
Commissariat à l Energie Atomique-CEA/LIST (Mr. Yann Tanguy, yann.tanguy@cea.fr)
Summary:
HwComponent stereotype has a property named "price" typed by "NFP_Price". The type NFP_Price does not exist in the document.
Resolution:
To add the nfpType NFP_Price in Annex D.
Revised Text:
-Modify Fig. D-5 using the following one:
(Note that this Figure has been modified by other issues related to Annex D!)
Figure D.5 - MARTE library of pre-declared NFP types
Disposition: Resolved
Disposition: Resolved OMG Issue No: 11526
Title: Section 2/2.2
Source:
WILSON PARDI JUNIOR, UFRGS – DELET, wilsonjr@ieee.org
Summary:
Section: 2/2.2
"The extensionUnits defined in this specification..." should be written as "The Extension Units defined in this specification..."
Resolution:
Text to update according to the previous proposal. DDDDDDwxvcx
Revised Text:
On page #2, replace the existing text "The extensionUnits defined in this specification..." by "The Extension Units defined in this specification..."
Disposition: Resolved
Disposition: Resolved OMG Issue No: 11527
Title: Issue 11527: Section 6/6/2/1
Source:
UFRGS - DELET (WILSON PARDI JUNIOR, wilsonjr@ieee.org)
Summary:
In the first paragraph of section 6.2.1 is written "...it is possible to give some general descriptions of four main sub categories included in the RT/E domain category...". However, five domains are described: - Embedded domain - Reactive domain - Control/Command domain - Intensive data flow computation domain - Best-effort service domain Also, only the 'Intensive data flow computation domain' is sub-sectioned as 6.2.1.1 (how about the other domains?)...
Resolution:
The resolution of this issue consists in making the required editorial changes as described in the next section.
Revised Text:
In the first paragraph of the section 6.2.1, in the fourth lines: change “…descriptions of four main…” into “…descriptions of five main…”Intensive data flow computation domain” as for other as “Embedded domain”.
Apply same style to the section untitled
Disposition: Resolved
Dostları ilə paylaş: |