Issue 14808: GQAM::RequestedService metaclass has no definition (marte-rtf) Source: THALES (Mr. Sebastien Demathieu, sebastien.demathieu(at)thalesgroup.com) Nature: Clarification Severity: Minor Summary: GQAM::RequestedService metaclass has no definition in Annex F. Resolution: A subsection must be inserted after F.10.13 with the definition. Also, Fig 15.3 is missing the attributes of Step which define the requests, and these should be added. Revised Text: (A) New subsection F.10.14 as follows: 15.3.2.11 RequestedService A RequestedService is an Operation by some class or interface, which is requested during the execution of a Step. This supports invocation of software services by components which are defined in other models. The RequestedService can in turn have details provided through the attributes it inherits from Step. An ordered list of RequestedServices may be specified, with a correspondingly ordered list servCount of mean numbers of requests made during the step. Generalizations • GaStep Associations • None Attributes • None Constraints • None (B) Fig 15.3 In the box for Step, two additional attributes need to be defined: serviceDemand:RequestedService [*] {ordered} serviceCount:NFP_Real [*] {ordered} (C) There is a spelling mistake in Figure 15.7, in the box for Step, servDeman should be replaced by servDemand. Actions taken: November 20, 2009: received issue January 14, 2011: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 20 Nov 2009 03:06:05 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: SĂ©stien Demathieu Company: Thales mailFrom: sebastien.demathieu@thalesgroup.com Notification: Yes Specification: UML profile for MARTE Section: F10.15 FormalNumber: MARTE Beta 3 Version: MARTE Beta 3 RevisionDate: 2009 Page: 713 Title: GQAM::RequestedService metaclass has no definition Nature: Clarification Severity: Minor test: 3qw8 B1: Report Issue Description: Subject: [MARTE v1.1 RTF] About #14808 Date: Tue, 13 Apr 2010 09:02:11 +0200 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [MARTE v1.1 RTF] About #14808 Thread-Index: Acra1z0L2mXV74LPQUqOmytBjnaS/A== From: "BERNARD, Yves" To: X-OriginalArrivalTime: 13 Apr 2010 07:02:11.0647 (UTC) FILETIME=[3D6714F0:01CADAD7] Hi, I don.t see the added value of the RequestedService Class, which has exactly the same attributes, associations, and constraints than GaStep. I believe that typing the serviceDemand attribute of GaStep by GaStep would be convenient and would simplify the domain model. I suggest voting No for this resolution and to provide a new one for ballot 2. Yves The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. Date: Wed, 14 Apr 2010 14:30:45 -0400 (EDT) From: Murray Woodside Reply-To: cmw@sce.carleton.ca To: "BERNARD, Yves" cc: marte-rtf@omg.org Subject: Re: [MARTE v1.1 RTF] About #14808 User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) Yves, you are quite correct. The difference is that PaStep is intended to stereotype beheviour entities, and RequestedService is intended to stereotype operations at an interface, say in a component diagram. Therefore there is a difference between the two... ReqeustedService can extend Operation, Step cannot. Unfortunately if it inherits from Step (desirable to control complexity, and because otherwise it needs to be the same) then RequestedService also can be applied to behaviour... a stereotype cannot disable any properties it inherits. We could do what you suggest. Then Step must be modified to apply also to Operation. 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 Tue, 13 Apr 2010, BERNARD, Yves wrote: Hi, I don¢t see the added value of the RequestedService Class, which has exactly the same attributes, associations, and constraints than GaStep. I believe that typing the serviceDemand attribute of GaStep by GaStep would be convenient and would simplify the domain model. I suggest voting No for this resolution and to provide a new one for ballot 2. Yves The information in this e-mail is confidential. The contents may not be disclosed or used by anyone ot her than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you s hould take whatever measures you deem to be appropriate to ensure that this message and any attachment s are virus free. GQAM::RequestedService metaclass has no definition in Annex F.