Issue 12797: What about a System Configuration concept having a set of OperationalModes? (marte-ftf) Source: Fundacion Tecnalia Research and Innovation (Mr. Huascar Espinoza Ph.D., Huascar.Espinoza(at)tecnalia.com) Nature: Revision Severity: Critical Summary: The operationalModes association end from rtUnit to rtBehavior has a multiplicity 0..1. This is not enough to model the OperationalMode as understood by fault-tolerance theory. An rtUnit should be capable to have many operationalModes. In addition, an OperationlMode would be need to be defined at system level too (not rtUnit level only). It seems that a separated stereotype (not rtBehavior as currently) would be necessary for OperationalMode. What about a System Configuration concept having a set of OperationalModes? Resolution: The concept of Mode (or Operational Mode) is central in embedded systems and in dependable embedded systems in particular. Having this concept only as an attribute of the RtUnit concept is indeed insufficient to model the behavioural and structural aspects of mode sensitive architectures. An operational mode can represent different things: - An operational system (or subsystem) state that is managed by reconfiguration mechanisms (e.g., fault-tolerance management middleware) according to fault conditions. - A state of system operation with a given level of QoS that can be handled by resource management infrastructures (e.g., middleware that assign resources at run time according to load demand, timing constraints, or resource usage). - A phase of a system operation e.g., starting, stopping, reconfiguring switchers, in a supervisory control system of an electric grid. We propose to adopt a number of minimum concepts to describe operational modes and their dynamics with UML state machines. Please notice that a UML state machine may be used “as is” to model operational modes and their dynamics. However, the need to unambiguously distinguish modal state machines, specifying the kind of above-mentioned macro-states, from other standard state machines, motivated us for explicitly describing these concepts in the MARTE specification. Furthermore, it seems necessary to characterize certain MARTE concepts with “modal” information. For instance, defining which entities are active in a given mode, specifying how entities behave in a mode transition, or determining what NFP values are valid in a given mode, all require means to refer to the entities proposed in this resolution. This resolution proposes to define this set of concepts related to operational modes in the “Core Elements” chapter. A number of updates are also proposed in other MARTE chapters to refer to the concepts added in “Core Elements”. Revised Text: see ptc/2009-05-12 pages 256 - 272 Actions taken: August 28, 2008: received issue October 16, 2009: closed issue Discussion: End of Annotations:===== vered-To: boldt23@gmail.com Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of omg-list-errors@amethyst.omg.org designates 192.67.184.64 as permitted sender) smtp.mail=omg-list-errors@amethyst.omg.org From: webmaster@omg.org Date: 28 Aug 2008 10:19:57 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Huascar Espinoza Company: CEA mailFrom: huascar.espinoza@cea.fr Notification: Yes Specification: UML MARTE Section: HLAM FormalNumber: 08-06-09 Version: Beta2 RevisionDate: 08-06-09 Page: 150 Nature: Revision Severity: Critical HTTP User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; InfoPath.1) Description The operationalModes association end from rtUnit to rtBehavior has a multiplicity 0..1. This is not enough to model the OperationalMode as understood by fault-tolerance theory. An rtUnit should be capable to have many operationalModes. In addition, an OperationlMode would be need to be defined at system level too (not rtUnit level only). It seems that a separated stereotype (not rtBehavior as currently) would be necessary for OperationalMode. What about a System Configuration concept having a set of OperationalModes? Subject: RE: Issue 12797: Operational Modes Date: Sun, 15 Mar 2009 18:32:41 +0100 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue 12797: Operational Modes Thread-Index: Acmj/rWVSnWr36hBSKC9CmkKNETl3gBk/h3w From: "BERNARD, Yves" To: "ESPINOZA Huascar 218344" , "marte-ftf" Cc: "GERARD Sebastien 166342" X-OriginalArrivalTime: 15 Mar 2009 17:32:41.0388 (UTC) FILETIME=[0AEDF6C0:01C9A594] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id n2FHWLSX017563 Hi Huascar, My feedback after after a first (and quick) reading. As you said modes are macro-states. A system is always in one mode and only one. Then I think that if a ModalBehavior is specified, the classifierBehavior should always be a ModalBehavior. Cheers, Yves -----Message d'origine----- De : ESPINOZA Huascar 218344 [mailto:Huascar.ESPINOZA@cea.fr] Envoyé : vendredi 13 mars 2009 18:11 À : marte-ftf Cc : GERARD Sebastien 166342 Objet : Issue 12797: Operational Modes Hi all, I proposed a resolution for 12797 related to the concept of Operational Mode in: http://www.omgwiki.org/marte-ftf2/doku.php?id=hlam_wg The resolution still needs some refinements, but it is ready to get your feedback during the next two weeks!! Cheers, Huascar -- Huascar ESPINOZA, Ph.D. CEA LIST Model-Driven Engineering for Real-Time Embedded Systems 91191 GIF/YVETTE CEDEX Phone/Fax: +33 1 69 08 45 87 / 20 82 FRANCE This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other then 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. Subject: Issue Modes: 12797 Date: Thu, 9 Apr 2009 16:11:03 +0200 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue Modes: 12797 Thread-Index: Acm5HQU/7j0NEdftS/6o1doZAyMaTQ== From: "ESPINOZA Huascar 218344" To: "marte-ftf" Cc: "GERARD Sebastien 166342" X-OriginalArrivalTime: 09 Apr 2009 14:11:04.0267 (UTC) FILETIME=[04CF89B0:01C9B91D] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id n39EBrIh008599 Hi all, The issue 12797 (Ballot 4) about operational modes has been completed with the descriptions of the Stereotypes, Annex F, Chapter NFPs. Please let me know if you have comments before beginning the voting period. http://www.omgwiki.org/marte-ftf2/lib/exe/fetch.php?id=hlam_wg&cache=cac he&media=12797_resolved_ballot4.doc Regards, Huascar -- Huascar ESPINOZA, Ph.D. CEA LIST Model-Driven Engineering for Real-Time Embedded Systems 91191 GIF/YVETTE CEDEX Phone/Fax: +33 1 69 08 45 87 / 20 82 FRANCE Date: Thu, 9 Apr 2009 11:46:12 -0400 (EDT) From: Murray Woodside Reply-To: cmw@sce.carleton.ca To: ESPINOZA Huascar 218344 cc: marte-ftf , GERARD Sebastien 166342 Subject: Re: Issue Modes: 12797 User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) Huascar, I have looked through it quickly and have some comments: 1. The constraint that a mode behaviour can only be in one state at a time needs to be explicit on the stereotype, since a state machine can be in a set of states, if there are othogonal states. A simple way to do this is to say that orthogonal states are not allowed. 2. The term "operational segment" is not well chosen, it seems to apply a period of time. Since in your solution it always refers to a configuration , you could say "operational configuration" instead. 3. Mode has associations in the domain model but in the profile they are only from the other end... they are not recorded for mode... is this deliberate and well-chosen? It seems to imply there is no navvigation from a mode to the affected elements. 4. Overall I think you have done a great job in putting together a coherent package... even if it doesnt handle everything, it looks very useful. 5. Why is the stereotyping of transitions in a mode behaviour so essential that it is constrained? Why does it matter? I imagine all states in a mode behaviour must be stereoytped mode also... but for them the point is to attach properties that are mode specific. 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 Thu, 9 Apr 2009, ESPINOZA Huascar 218344 wrote: Hi all, The issue 12797 (Ballot 4) about operational modes has been completed with the descriptions of the Stereotypes, Annex F, Chapter NFPs. Please let me know if you have comments before beginning the voting period. http://www.omgwiki.org/marte-ftf2/lib/exe/fetch.php?id=hlam_wg&cache=cac he&media=12797_resolved_ballot4.doc Regards, Huascar -- Huascar ESPINOZA, Ph.D. CEA LIST Model-Driven Engineering for Real-Time Embedded Systems 91191 GIF/YVETTE CEDEX Phone/Fax: +33 1 69 08 45 87 / 20 82 FRANCE Subject: RE: Issue Modes: 12797 Date: Thu, 9 Apr 2009 18:33:29 +0200 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue Modes: 12797 Thread-Index: Acm5KlShW+tQrbtbTve7NpK5jvGbgAAAgzQg From: "ESPINOZA Huascar 218344" To: Cc: "marte-ftf" , "GERARD Sebastien 166342" X-OriginalArrivalTime: 09 Apr 2009 16:33:29.0534 (UTC) FILETIME=[EA2FCDE0:01C9B930] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id n39GXt6k014710 Hi Murray, Thank you for all your feedback, not only now, but in previous versions too! Please see my comments below... -----Message d'origine----- De : Murray Woodside [mailto:cmw@sce.carleton.ca] Envoyé : jeudi 9 avril 2009 17:46 À : ESPINOZA Huascar 218344 Cc : marte-ftf; GERARD Sebastien 166342 Objet : Re: Issue Modes: 12797 Huascar, I have looked through it quickly and have some comments: 1. The constraint that a mode behaviour can only be in one state at a time needs to be explicit on the stereotype, since a state machine can be in a set of states, if there are othogonal states. A simple way to do this is to say that orthogonal states are not allowed. HE--> I put that in the semantics of ModeBehavior, when I said that the set of modes are mutually exclusive, but you're right, this should formalized with a Constraint. There is something, however, that I'm not fully sure: Do we really have to constrain a Mode Behavior to only have one Mode at a time? Anyway, I'll add the constraint. Thank you. 2. The term "operational segment" is not well chosen, it seems to apply a period of time. Since in your solution it always refers to a configuration , you could say "operational configuration" instead. HE--> In fact, the fact that a Mode refers to a configuration is represented by the association of Mode to Configuration. Moreover, more than one Mode can have the same Configuration. So the relationship is not one to one. Instead, a Mode is more related to a State, and so, the reference to an "operational segment" fits better in the sense that the system is working in a given Mode during a temporal segment. 3. Mode has associations in the domain model but in the profile they are only from the other end... they are not recorded for mode... is this deliberate and well-chosen? It seems to imply there is no navvigation from a mode to the affected elements. HE --> Yes, in the profile, the affected elements (entities participating in a Mode) are collected in the related Configuration models. The navigation is done through the Configuration element. 4. Overall I think you have done a great job in putting together a coherent package... even if it doesnt handle everything, it looks very useful. HE--> We intended to provide a basis for modeling "modal" aspects. Further refinements of this base model may be done later. 5. Why is the stereotyping of transitions in a mode behaviour so essential that it is constrained? Why does it matter? I imagine all states in a mode behaviour must be stereoytped mode also... but for them the point is to attach properties that are mode specific. HE--> For the case of Mode, a stereotype is defined to be reference to this Mode unambiguously. For instance, a NFP_Constraint, or a Configuration are related to a Mode. For Mode Transitions, the choice of adding a stereotype may be arguable, but we think that we may need to make reference to a Mode Transition for future needs. For instance, we may say that some system configuration, or quality scenario, is specific to a given transition interval in which a system is going from one mode to other. 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 Thu, 9 Apr 2009, ESPINOZA Huascar 218344 wrote: > > Hi all, > > The issue 12797 (Ballot 4) about operational modes has been completed > with the descriptions of the Stereotypes, Annex F, Chapter NFPs. Please > let me know if you have comments before beginning the voting period. > > http://www.omgwiki.org/marte-ftf2/lib/exe/fetch.php?id=hlam_wg&cache=cac > he&media=12797_resolved_ballot4.doc > > Regards, > Huascar > > -- > Huascar ESPINOZA, Ph.D. > CEA LIST > Model-Driven Engineering for Real-Time Embedded Systems > 91191 GIF/YVETTE CEDEX > Phone/Fax: +33 1 69 08 45 87 / 20 82 > FRANCE Subject: RE : Issue 12797: Operational Modes Date: Tue, 24 Mar 2009 23:07:19 +0100 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue 12797: Operational Modes Thread-Index: Acmj/rWVSnWr36hBSKC9CmkKNETl3gIzjD5p From: "ESPINOZA Huascar 218344" To: "marte-ftf" Cc: "GERARD Sebastien 166342" X-OriginalArrivalTime: 24 Mar 2009 22:09:41.0008 (UTC) FILETIME=[3AB67900:01C9ACCD] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id n2OMA9hY004130 Hi All, If you don't have general observations on Issue 12797 (Operational Modes) of Ballot 3, I will complete it with the Stereotype Description and other details. Regards, Huascar ________________________________ De: ESPINOZA Huascar 218344 Date: ven. 13/03/2009 18:11 À: marte-ftf Cc: GERARD Sebastien 166342 Objet : Issue 12797: Operational Modes Hi all, I proposed a resolution for 12797 related to the concept of Operational Mode in: http://www.omgwiki.org/marte-ftf2/doku.php?id=hlam_wg The resolution still needs some refinements, but it is ready to get your feedback during the next two weeks!! Cheers, Huascar -- Huascar ESPINOZA, Ph.D. CEA LIST Model-Driven Engineering for Real-Time Embedded Systems 91191 GIF/YVETTE CEDEX Phone/Fax: +33 1 69 08 45 87 / 20 82