Legacy Issue Number: 11856
Source: ESEO ( Jerome Delatour)
A simplification of GRM should be envisaged.
GRM defines too many detailled concepts (for instance the Scheduler which seems more
appropriate in the SRM package), these concepts could be defined in
SRM or HRM package or even in SAM package.
The way to define different types of services need to be aligned between GRM, SRM
Reported: MARTE 1.0b1 — Fri, 21 Dec 2007 05:00 GMT
Disposition: Resolved — MARTE 1.0
With respect to the status of the FTF, the resolution of this issue would need too
much time to be resolved in an efficient and satisfying form. So, I (Sébastien
Gérard from CEA LIST) propose to defer it.
Disposition: Deferred This issue has been resolved by resolutions to issues 11411 and 11412. A brief
modification is necessary in the introduction of GRM to comprise it as generic for
also analysis and design. A brief text is to be added to the Introduction of GRM to emphasize its a role of
foundation for the analysis packages (GQAM, SAM and PAM) and the DRM
(SRM and HRM).
Updated: Wed, 11 Mar 2015 01:53 GMT