Issue 14917: Clarify the relationship between GQAM::WorkloadEvent and GRM::UsageDemand (marte-rtf) Source: THALES (Mr. Sebastien Demathieu, sebastien.demathieu(at)thalesgroup.com) Nature: Clarification Severity: Significant Summary: GQAM::BehaviorScenario specializes GRM::ResourceUsage. It seems that GRM::UsageDemand generalizes GQAM::WorkloadEvent. If so, make explicit this generalization relationship and consider the WorkloadEvent.timeEvent, WorkloadEvent.effect and BehaviorScenario.cause as redefined attributes Resolution: This is actuially a very good observation. It does not seem dangerous. A resolution with it is provided. Note for the editor: Please observe that this resolution must be edited in after issue 14906, since this add the “redefined” constraint. Revised Text: Annex F, Section F.10.3 BehaviorScenario eliminate attribute: inputStream: RequestEventStream [1..*] RequestEventStream that initiates it. And insert association: cause: WorkloadEvent [1..*] {redefines workload} The characterization of the events that may initiate this BehaviorScenario. Annex F, Section F.10.20 WorkloadEvent Add the associations: effect: BehaviorScenario[1] {redefines usage} The behaviorScenario that is launched by the workloadEvent timeEvent: Time::TimedEventModel::TimedEvents::TimedEvent [0..1] {redefines event} Indicates a timed event that generates the workloadEvent Also add the generalization: UsageDemand (from MARTE::GRM::ResourceUsages). Change Fig 15.3 by this: <<< see page 114 for graphics>>> Actions taken: December 31, 2009: received issue January 14, 2011: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 31 Dec 2009 08:15:38 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Séstien Demathieu Company: Thales mailFrom: sebastien.demathieu@thalesgroup.com Notification: Yes Specification: MARTE Section: GQAM FormalNumber: 09-11-02 Version: 1.0 RevisionDate: 11/2009 Page: 289 Title: Clarify the relationship between GQAM::WorkloadEvent and GRM::UsageDemand Nature: Clarification Severity: Significant test: 3qw8 B1: Report Issue Description: Date: Mon, 19 Apr 2010 15:42:05 +0200 From: Julio Medina User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) To: marte-ftf , Murray Woodside Subject: GQAM-GRM proposed resolution for 14917 New Inheritance GRM::UsageDemand- GQAM::WorkloadEvent X-OriginalArrivalTime: 19 Apr 2010 13:41:44.0683 (UTC) FILETIME=[0CEC93B0:01CADFC6] X-imss-version: 2.054 X-imss-result: Passed X-imss-scanInfo: M:P L:E SM:0 X-imss-tmaseResult: TT:0 TS:0.0000 TC:00 TRN:0 TV:6.0.1038(17328.007) X-imss-scores: Clean:78.48242 C:2 M:3 S:5 R:5 X-imss-settings: Baseline:1 C:1 M:2 S:2 R:2 (0.0000 0.0000) Hi all, hi Murray, The issue: GQAM::BehaviorScenario specializes GRM::ResourceUsage. It seems that GRM::UsageDemand generalizes GQAM::WorkloadEvent. If so, make explicit this generalization relationship and consider the WorkloadEvent.timeEvent, WorkloadEvent.effect and BehaviorScenario.cause as redefined attributes I think the proposal from Séstien Demathieu of making explicit this inheritance is not that complex and we may introduce it easily. If you agree I can make the paperwork (see the draft resolution in the attached file), but could you please send me the GQAM visio files?. Cheers, Julio 14917_resolved_draft.doc Date: Mon, 19 Apr 2010 11:53:46 -0400 (EDT) From: Murray Woodside Reply-To: cmw@sce.carleton.ca To: Julio Medina cc: marte-ftf Subject: Re: GQAM-GRM proposed resolution for 14917 New Inheritance GRM::UsageDemand- GQAM::WorkloadEvent User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) Are you sure it is permitted to redefine attributes when inheriting in a profile? My memory is, that it is not permitted. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) On Mon, 19 Apr 2010, Julio Medina wrote: Hi all, hi Murray, The issue: GQAM::BehaviorScenario specializes GRM::ResourceUsage. It seems that GRM::UsageDemand generalizes GQAM::WorkloadEvent. If so, make explicit this generalization relationship and consider the WorkloadEvent.timeEvent, WorkloadEvent.effect and BehaviorScenario.cause as redefined attributes I think the proposal from Séstien Demathieu of making explicit this inheritance is not that complex and we may introduce it easily. If you agree I can make the paperwork (see the draft resolution in the attached file), but could you please send me the GQAM visio files?. Cheers, Julio GQAM::BehaviorScenario specializes GRM::ResourceUsage. It seems that GRM::UsageDemand generalizes GQAM::WorkloadEvent. If so, make explicit this generalization relationship and consider the WorkloadEvent.timeEvent, WorkloadEvent.effect and BehaviorScenario.cause as redefined attributes