Issue 11865: RtAction.isAtomic (marte-ftf) Source: THALES (Mr. Sebastien Demathieu, sebastien.demathieu(at)thalesgroup.com) Nature: Revision Severity: Minor Summary: The meaning of the RtAction.isAtomic should be precisely state. In chapter 13, isAtomic is used in other contexts (e.g. flow ports) with other semantics. Resolution: Provide a precise, non-recursive definition: here, isAtomic means indivisible. Revised Text: On page 548, Section F.7.8, replace Attributes o syncKind: SynchronizationKind [0..1] kind of synchronization used when an action is completed. o isAtomic: Boolean [1] = false indicates whether a real-time action is atomic. o msgSize: NFP_DataSize [0..1] size of a message generated when executing an action. Associations o pRTF: RealTimeFeature [0..1] real-time feature related to a RtAction. Semantics A real-time action can specify a real-time feature such as a deadline or a period. It can also describe the size of the message generated when executing the action, as well as the kind of synchronisation used when the action is completed. Finally, a real-time action may be atomic. With Attributes o syncKind: SynchronizationKind [0..1] kind of synchronization used when the Action executes. o isAtomic: Boolean [1] = false when true, implies that the Action executes as one indivisible unit, non-interleaved with other Actions. o msgSize: NFP_DataSize [0..1] size of a message generated when the Action executes. Associations o pRTF: RealTimeFeature [0..1] real-time feature related to the RtAction. Semantics An RtAction is an Action specialized with the additional aforementioned attributes of "real-time" constraints. On page 550, SectionF.7.12, replace A real-time service can specify real-time features such as a deadline or a period. It can also describe a concurrency policy, an execution policy as well as a synchronization policy. Finally, a real-time service may be atomic. Generalization o Service (from MARTE::GRM::ResourceCore) Attributes o concPolicy: ConcurrencyKind [1] concurrency policy used for the real-time service. o exeKind: ExcutionKind [1] execution policy used for the real-time service. o isAtomic: Boolean [1] = false indicates whether the service execution is considered as atomic. o syncKind: SynchronizationKind [1] synchronization policy used for the real-time service. Associations o pRTF: RealTimeFeature [0..1] real-time feature that can be attached to a real-time service. Semantics A real-time service can specify real-time features such as a deadline or a period (see details of the ArrivalPattern data type introduced in the MARTELib). It can also describe a concurrency policy, an execution policy as well as a synchronization policy. Finally, a real-time service may be atomic. These characteristics are applicable for all the invocations of the service With An RtService can specify the real-time features described by its attributes. Generalization o Service (from MARTE::GRM::ResourceCore) Attributes o concPolicy: ConcurrencyKind [1] concurrency policy used for the real-time service. o exeKind: ExcutionKind [1] execution policy used for the real-time service. o isAtomic: Boolean [1] = false when true, implies that the RtService executes as one indivisible unit, non-interleaved with other RtServices. o syncKind: SynchronizationKind [1] synchronization policy used for the real-time service. Associations o pRTF: RealTimeFeature [0..1] real-time feature that can be attached to a real-time service. Semantics An RtService is a Service specialized with the additional aforementioned attributes of "real-time" constraints. These attributes apply for all the invocations of the RtService. On page 160, Section 13.3.2.6, replace The RtAction stereotype maps the RtAction domain element (section F.7.8, p. 495) denoted in Annex F. Real-time invocation action can specify real-time features such as a deadline or period (see details of the ArrivalPattern data type introduced in the MARTELib). It can also describe the size of the message generated when executing or the kind of synchronization (synchKind attribute). Finally, a real-time action execution may be atomic. Extensions o InvocationAction (from UML::BasicBehaviors). o BehavioralFeature (from UML::Kernel). Attributes o synchKind: SynchronizationKind synchronization mechanism associated to the communication action. o isAtomic: Boolean [1] = false if true, the action execution is atomic. o msgSize: NFP_DataSize size of a message generated when executing an action. With The RtAction stereotype maps the RtAction domain element (section F.7.8, p. 495) denoted in Annex F. InvocationActions and BehavioralFeatures, stereotyped with RtAction, gain the additional following attributes of "real-time" constraints. Extensions o InvocationAction (from UML::BasicBehaviors). o BehavioralFeature (from UML::Kernel). Attributes o synchKind: SynchronizationKind synchronization mechanism associated to the communication action. o isAtomic: Boolean [1] = false when true, implies that the RtAction executes as one indivisible unit, non-interleaved with other RtActions. o msgSize: NFP_DataSize size of a message generated when executing an action. On page 162, Section 13.3.2.10, replace The RtService stereotype maps the RtService domain element (section F.7.12) denoted in Annex F. Real-time service can specify real-time features such as a deadline or period (see details of the ArrivalPattern data type introduced in the MARTE_Library::MARTE_DataTypes). It can also define a concurrency policy as well as an execution policy. Finally, a real-time action execution may be atomic. The RtService stereotype may be applied on one BehavioralFeature independently of the fact that the containing classifier to be either a RtUnit or a PpUnit. Extensions o BehavioralFeature (from UML::Kernel) Attributes o concPolicy: ConcurrencyKind [0..1] concurrency property of the service. o exeKind: ExecutionKind [0..1] execution nature property of the service. o isAtomic: Boolean [1] = false if true, the execution of the service is atomic. o synchKind: SynchronizationKind [0..1] synchronization mechanism of the service. With The RtService stereotype maps the RtService domain element (section F.7.12) denoted in Annex F. BehavioralFeatures, stereotyped with RtService, gain the additional following attributes of "real-time" constraints. The RtService stereotype may be applied on one BehavioralFeature independently of the fact that the containing classifier to be either a RtUnit or a PpUnit. Extensions o BehavioralFeature (from UML::Kernel) Attributes o concPolicy: ConcurrencyKind [0..1] concurrency property of the RtService. o exeKind: ExecutionKind [0..1] execution nature property of the service. o isAtomic: Boolean [1] = false when true, implies that the RtService executes as one indivisible unit, non-interleaved with other RtService. o synchKind: SynchronizationKind [0..1] synchronization mechanism of the RtService. Actions taken: December 21, 2007: received issue February 17, 2010: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 21 Dec 2007 13:40:32 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Sébastien Demathieu Company: Thales mailFrom: sebastien.demathieu@thalesgroup.com Notification: No Specification: UML profile for MARTE Section: 13 FormalNumber: 07-08-04 Version: Beta 1 RevisionDate: 08/2007 Page: 160 Nature: Revision Severity: Minor HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11 Description The meaning of the RtAction.isAtomic should be precisely state. In chapter 13, isAtomic is used in other contexts (e.g. flow ports) with other semantics.