Issue 11781: NFP: value syntax (marte-ftf) Source: Fundacion Tecnalia Research and Innovation (Mr. Huascar Espinoza Ph.D., Huascar.Espinoza(at)tecnalia.com) Nature: Enhancement Severity: Significant Summary: [NFP: value syntax] It may be useful to have a shorter (graphical) notation for NFP types including the value and unit slots only, e.g., ‘(55, kHz)’, or still ’55 kHz’, instead of the notation ‘(55, -, kHz, max, -, est, -)’ with all the qualifiers. This will enhance the graphical models readability. While this feature may be only a tool-specific mechanism, which could propose a graphical view (short notation) of the repository notation (full notation), it would be useful to standardize this notation in the MARTE spec. Resolution: We include this syntax (value-unit) only as a tool-specific feature to show NFP values in graphical models. This means that the syntax defined in VSL is still valid for NFP values (tuple notation). The reason is that the model repository needs to keep all the required NFP value information (value, unit, plus other qualifiers). Revised Text: It is important to note that such a shorter (graphical) textual notation will be normative, in the sense that it is valid. However, it is not mandatory. -Insert a new Section between 8.3.2 and 8.3.3: "8.3.3 Graphical Syntax of NFP Value Specification In this section, we define an alternative graphical syntax for value specifications having NfpType as data type. This syntax consists of a pair of a value and a unit: <nfp-value> ::= <value-specification> [' ' <unit-enumeration>] The following are typical examples: 5 ms # a duration value 50 kHz # a frequency value Note that this notation is for the graphical view of models only. The tuple notation (see Section B.3.3.9) is still valid for NFP values (NfpType inherits from VSL::TupleType), both in graphical models and in the repository as well. For instance, the NFP value: '50 kHz' can be specified in the model repository as: '(50, -, kHz, max, -, est, -)' or '(value=50, expr=null, unit=kHz, statQ=max, dir=null, source=est, precision=null)' The main rationale of the "value-unit" notation is readability of graphical models. Specific tools could provide more flexibility in the graphical notation. For instance, users may be able to customize the elements of a tuple in a NFP value specification that should be displayed. However, because of its common usage in engineering models in general, the "value-unit" notation is normative (although not mandatory) in MARTE." -Change Fig. 8.9 by the following one: Figure 8.9 - Example of user model for analysis with NFP annotations Actions taken: December 7, 2007: received issue February 17, 2010: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 07 Dec 2007 09:46:39 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Dr. Huascar Espinoza Company: CEA LIST mailFrom: huascar.espinoza@cea.fr Notification: Yes Specification: UML Profile for MARTE Section: NFP FormalNumber: ptc/07-08-04 Version: Beta 1 RevisionDate: 08/04/07 Page: 46 Nature: Enhancement Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727; InfoPath.1) Description [NFP: value syntax] It may be useful to have a shorter (graphical) notation for NFP types including the value and unit slots only, e.g., .(55, kHz)., or still .55 kHz., instead of the notation .(55, -, kHz, max, -, est, -). with all the qualifiers. This will enhance the graphical models readability. While this feature may be only a tool-specific mechanism, which could propose a graphical view (short notation) of the repository notation (full notation), it would be useful to standardize this notation in the MARTE spec. Subject: MARTE Issue 11781 : short notation with 'value' and 'unit' only Date: Thu, 14 Feb 2008 12:12:11 +0100 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MARTE Issue 11781 : short notation with 'value' and 'unit' only thread-index: Achu+nHjnfj9eQdyR4mMifMqF4w9cA== From: "ESPINOZA Huascar 218344" To: Cc: "GERARD Sebastien 166342" , Sébastien Demathieu , "MRAIDHA Chokri 176997" , X-OriginalArrivalTime: 14 Feb 2008 11:12:11.0598 (UTC) FILETIME=[722536E0:01C86EFA] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id m1EBCh89029516 Hi all, Issue 11781 (copied below) asks for having a shorter notation for NFP values, with value and unit only, ONLY FOR A GRAPHICAL VIEW. This means that a NFP value with the following two alternative notations in the "repository" (repository here is the 'model' file): myFrequency= (value=55, unit=kHz, statQ=max, source=est) myFrequency= (55, -, kHz, max, -, est, -) will be able to be shown in the Graphical view in a shorter notation: myFrequency= 55 KHz Note that the complete information is still in the repository (e.g., body of an OpaqueExpression). The goal: make graphical models more readable. This is indeed a tool-specific problem. However, I'd like to use this notation extensively in MARTE examples. -->So it seems reasonable to formalize this graphical notation (as one alternative for tools) in the MARTE spec. >From my viewpoint, this shorter graphical notation should be adopted because it will have an important added value to MARTE model comprehensibility. However, before sending an initial resolution, I'd like to know your opinion. Best regards, -- Huascar ESPINOZA, Ph.D. CEA Saclay DRT/DTSI/SOL/LISE 91191 GIF/YVETTE CEDEX Phone/Fax: +33 1 69 08 45 87 / 20 82 France ____________________ OMG Issue No: 11781 Title: NFP: value syntax (adopt a compact graphic notation for NfpType values: value + unit) Summary: [NFP: value syntax] It may be useful to have a shorter (graphical) notation for NFP types including the value and unit slots only, e.g., '(55, kHz)', or still '55 kHz', instead of the notation '(55, -, kHz, max, -, est, -)' with all the qualifiers. This will enhance the graphical models readability. While this feature may be only a tool-specific mechanism, which could propose a graphical view (short notation) of the repository notation (full notation), it would be useful to standardize this notation in the MARTE spec. Proposed Resolution: This may be only a tool specific feature to show nfp values in graphical models, because the repository need to keep all the nfp value information (other qualifiers). However, it would be a good idea to describe this feature and show in examples. This will enhance the readability of UML models. Date: Thu, 14 Feb 2008 06:57:36 -0500 (EST) From: Murray Woodside Reply-To: cmw@sce.carleton.ca To: ESPINOZA Huascar 218344 Cc: marte-ftf@omg.org Subject: Re: MARTE Issue 11781 : short notation with 'value' and 'unit' only Huascar, I am strongly in favour. I remember Bran commenting early on that the clumsy value notation in SPT was a barrier to usage. A standardized shorthand has value in readbility across tools. 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, 14 Feb 2008, ESPINOZA Huascar 218344 wrote: Hi all, Issue 11781 (copied below) asks for having a shorter notation for NFP values, with value and unit only, ONLY FOR A GRAPHICAL VIEW. This means that a NFP value with the following two alternative notations in the "repository" (repository here is the 'model' file): myFrequency= (value=55, unit=kHz, statQ=max, source=est) myFrequency= (55, -, kHz, max, -, est, -) will be able to be shown in the Graphical view in a shorter notation: myFrequency= 55 KHz Note that the complete information is still in the repository (e.g., body of an OpaqueExpression). The goal: make graphical models more readable. This is indeed a tool-specific problem. However, I'd like to use this notation extensively in MARTE examples. -->So it seems reasonable to formalize this graphical notation (as one alternative for tools) in the MARTE spec. From my viewpoint, this shorter graphical notation should be adopted because it will have an important added value to MARTE model comprehensibility. However, before sending an initial resolution, I'd like to know your opinion. Best regards, -- Huascar ESPINOZA, Ph.D. CEA Saclay DRT/DTSI/SOL/LISE 91191 GIF/YVETTE CEDEX Phone/Fax: +33 1 69 08 45 87 / 20 82 France ____________________ OMG Issue No: 11781 Title: NFP: value syntax (adopt a compact graphic notation for NfpType values: value + unit) Summary: [NFP: value syntax] It may be useful to have a shorter (graphical) notation for NFP types including the value and unit slots only, e.g., '(55, kHz)', or still '55 kHz', instead of the notation '(55, -, kHz, max, -, est, -)' with all the qualifiers. This will enhance the graphical models readability. While this feature may be only a tool-specific mechanism, which could propose a graphical view (short notation) of the repository notation (full notation), it would be useful to standardize this notation in the MARTE spec. Proposed Resolution: This may be only a tool specific feature to show nfp values in graphical models, because the repository need to keep all the nfp value information (other qualifiers). However, it would be a good idea to describe this feature and show in examples. This will enhance the readability of UML models. Date: Thu, 14 Feb 2008 18:53:03 +0100 From: Sébastien Demathieu Organization: Thales Research & Technology User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) To: cmw@sce.carleton.ca, ESPINOZA Huascar 218344 Cc: marte-ftf@omg.org Subject: Re: MARTE Issue 11781 : short notation with 'value' and 'unit' only X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id m1EHrrKQ011319 Hi Huascar, That makes sense to me too. In the VSL parser we worked on, we also introduced another shorthand notation to allow expressions like "(55.0, kHz)". In this case, it implicitly refers to "(value=55.0, unit=kHz)". I would suggest supporting this as well. Thanks, Sébastien Murray Woodside a écrit : Huascar, I am strongly in favour. I remember Bran commenting early on that the clumsy value notation in SPT was a barrier to usage. A standardized shorthand has value in readbility across tools. 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, 14 Feb 2008, ESPINOZA Huascar 218344 wrote: Hi all, Issue 11781 (copied below) asks for having a shorter notation for NFP values, with value and unit only, ONLY FOR A GRAPHICAL VIEW. This means that a NFP value with the following two alternative notations in the "repository" (repository here is the 'model' file): myFrequency= (value=55, unit=kHz, statQ=max, source=est) myFrequency= (55, -, kHz, max, -, est, -) will be able to be shown in the Graphical view in a shorter notation: myFrequency= 55 KHz Note that the complete information is still in the repository (e.g., body of an OpaqueExpression). The goal: make graphical models more readable. This is indeed a tool-specific problem. However, I'd like to use this notation extensively in MARTE examples. -->So it seems reasonable to formalize this graphical notation (as one alternative for tools) in the MARTE spec. From my viewpoint, this shorter graphical notation should be adopted because it will have an important added value to MARTE model comprehensibility. However, before sending an initial resolution, I'd like to know your opinion. Best regards, -- Huascar ESPINOZA, Ph.D. CEA Saclay DRT/DTSI/SOL/LISE 91191 GIF/YVETTE CEDEX Phone/Fax: +33 1 69 08 45 87 / 20 82 France ____________________ OMG Issue No: 11781 Title: NFP: value syntax (adopt a compact graphic notation for NfpType values: value + unit) Summary: [NFP: value syntax] It may be useful to have a shorter (graphical) notation for NFP types including the value and unit slots only, e.g., '(55, kHz)', or still '55 kHz', instead of the notation '(55, -, kHz, max, -, est, -)' with all the qualifiers. This will enhance the graphical models readability. While this feature may be only a tool-specific mechanism, which could propose a graphical view (short notation) of the repository notation (full notation), it would be useful to standardize this notation in the MARTE spec. Proposed Resolution: This may be only a tool specific feature to show nfp values in graphical models, because the repository need to keep all the nfp value information (other qualifiers). However, it would be a good idea to describe this feature and show in examples. This will enhance the readability of UML models. Subject: RE: MARTE Issue 11781 : short notation with 'value' and 'unit' only Date: Thu, 14 Feb 2008 17:57:20 -0000 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MARTE Issue 11781 : short notation with 'value' and 'unit' only Thread-Index: Achu+nHjnfj9eQdyR4mMifMqF4w9cAAN7t4g From: "VanZandt, Lonnie" To: "ESPINOZA Huascar 218344" , Cc: "GERARD Sebastien 166342" , Sébastien Demathieu , "MRAIDHA Chokri 176997" , X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id m1EHv8wi012178 On a practical level, how will the tool know which fields to show in the graphical views? Rather than making "unit" and "value" magically special, we may want to decorate the fields such that one can arbitrarily indicate which should be displayed graphically. Or is this perhaps too much featuritis? I definitely agree that the capability will be desirable: diagrams of heavily stereotyped elements quickly become practically unreadable by anything but an analysis engine. Poor humans find the diagrams unusable. -----Original Message----- From: ESPINOZA Huascar 218344 [mailto:Huascar.ESPINOZA@cea.fr] Sent: Thursday, February 14, 2008 4:12 AM To: marte-ftf@omg.org Cc: GERARD Sebastien 166342; Sébastien Demathieu; MRAIDHA Chokri 176997; cmw@sce.carleton.ca Subject: MARTE Issue 11781 : short notation with 'value' and 'unit' only Hi all, Issue 11781 (copied below) asks for having a shorter notation for NFP values, with value and unit only, ONLY FOR A GRAPHICAL VIEW. This means that a NFP value with the following two alternative notations in the "repository" (repository here is the 'model' file): myFrequency= (value=55, unit=kHz, statQ=max, source=est) myFrequency= (55, -, kHz, max, -, est, -) will be able to be shown in the Graphical view in a shorter notation: myFrequency= 55 KHz Note that the complete information is still in the repository (e.g., body of an OpaqueExpression). The goal: make graphical models more readable. This is indeed a tool-specific problem. However, I'd like to use this notation extensively in MARTE examples. -->So it seems reasonable to formalize this graphical notation (as one alternative for tools) in the MARTE spec. >From my viewpoint, this shorter graphical notation should be adopted because it will have an important added value to MARTE model comprehensibility. However, before sending an initial resolution, I'd like to know your opinion. Best regards, -- Huascar ESPINOZA, Ph.D. CEA Saclay DRT/DTSI/SOL/LISE 91191 GIF/YVETTE CEDEX Phone/Fax: +33 1 69 08 45 87 / 20 82 France ____________________ OMG Issue No: 11781 Title: NFP: value syntax (adopt a compact graphic notation for NfpType values: value + unit) Summary: [NFP: value syntax] It may be useful to have a shorter (graphical) notation for NFP types including the value and unit slots only, e.g., '(55, kHz)', or still '55 kHz', instead of the notation '(55, -, kHz, max, -, est, -)' with all the qualifiers. This will enhance the graphical models readability. While this feature may be only a tool-specific mechanism, which could propose a graphical view (short notation) of the repository notation (full notation), it would be useful to standardize this notation in the MARTE spec. Proposed Resolution: This may be only a tool specific feature to show nfp values in graphical models, because the repository need to keep all the nfp value information (other qualifiers). However, it would be a good idea to describe this feature and show in examples. This will enhance the readability of UML models. Subject: RE : MARTE Issue 11781 : short notation with 'va lue' and 'unit' only Date: Thu, 14 Feb 2008 19:14:48 +0100 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MARTE Issue 11781 : short notation with 'value' and 'unit' only thread-index: Achu+nHjnfj9eQdyR4mMifMqF4w9cAAN7t4gAADTnMM= From: "ESPINOZA Huascar 218344" To: "VanZandt, Lonnie" , Cc: "GERARD Sebastien 166342" , Sébastien Demathieu , "MRAIDHA Chokri 176997" , X-OriginalArrivalTime: 14 Feb 2008 18:17:01.0718 (UTC) FILETIME=[CB70DB60:01C86F35] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id m1EIH5Mq016981 Hi Lonnie, This can be easily done because the nfpType has three attributes: valueAttrib, unitAttrib, exprAttrib, (all three typed by UML::Property) which refer to the Properties of the nfpType. This will do special to those properties. For more examples, please see the NFP chapter. Regards, Huascar ________________________________ De: VanZandt, Lonnie [mailto:lonnie.vanzandt@artisansw.com] Date: jeu. 14/02/2008 18:57 À: ESPINOZA Huascar 218344; marte-ftf@omg.org Cc: GERARD Sebastien 166342; Sébastien Demathieu; MRAIDHA Chokri 176997; cmw@sce.carleton.ca Objet : RE: MARTE Issue 11781 : short notation with 'value' and 'unit' only On a practical level, how will the tool know which fields to show in the graphical views? Rather than making "unit" and "value" magically special, we may want to decorate the fields such that one can arbitrarily indicate which should be displayed graphically. Or is this perhaps too much featuritis? I definitely agree that the capability will be desirable: diagrams of heavily stereotyped elements quickly become practically unreadable by anything but an analysis engine. Poor humans find the diagrams unusable. -----Original Message----- From: ESPINOZA Huascar 218344 [mailto:Huascar.ESPINOZA@cea.fr] Sent: Thursday, February 14, 2008 4:12 AM To: marte-ftf@omg.org Cc: GERARD Sebastien 166342; Sébastien Demathieu; MRAIDHA Chokri 176997; cmw@sce.carleton.ca Subject: MARTE Issue 11781 : short notation with 'value' and 'unit' only Hi all, Issue 11781 (copied below) asks for having a shorter notation for NFP values, with value and unit only, ONLY FOR A GRAPHICAL VIEW. This means that a NFP value with the following two alternative notations in the "repository" (repository here is the 'model' file): myFrequency= (value=55, unit=kHz, statQ=max, source=est) myFrequency= (55, -, kHz, max, -, est, -) will be able to be shown in the Graphical view in a shorter notation: myFrequency= 55 KHz Note that the complete information is still in the repository (e.g., body of an OpaqueExpression). The goal: make graphical models more readable. This is indeed a tool-specific problem. However, I'd like to use this notation extensively in MARTE examples. -->So it seems reasonable to formalize this graphical notation (as one alternative for tools) in the MARTE spec. >From my viewpoint, this shorter graphical notation should be adopted because it will have an important added value to MARTE model comprehensibility. However, before sending an initial resolution, I'd like to know your opinion. Best regards, -- Huascar ESPINOZA, Ph.D. CEA Saclay DRT/DTSI/SOL/LISE 91191 GIF/YVETTE CEDEX Phone/Fax: +33 1 69 08 45 87 / 20 82 France ____________________ OMG Issue No: 11781 Title: NFP: value syntax (adopt a compact graphic notation for NfpType values: value + unit) Summary: [NFP: value syntax] It may be useful to have a shorter (graphical) notation for NFP types including the value and unit slots only, e.g., '(55, kHz)', or still '55 kHz', instead of the notation '(55, -, kHz, max, -, est, -)' with all the qualifiers. This will enhance the graphical models readability. While this feature may be only a tool-specific mechanism, which could propose a graphical view (short notation) of the repository notation (full notation), it would be useful to standardize this notation in the MARTE spec. Proposed Resolution: This may be only a tool specific feature to show nfp values in graphical models, because the repository need to keep all the nfp value information (other qualifiers). However, it would be a good idea to describe this feature and show in examples. This will enhance the readability of UML models. Subject: Issue 11781 Date: Mon, 17 Mar 2008 14:40:07 +0100 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue 11781 Thread-Index: AciIHMysrV9ds3TBRry66jyKmYB4owAF1rfg From: "ESPINOZA Huascar 218344" To: X-OriginalArrivalTime: 17 Mar 2008 13:40:08.0822 (UTC) FILETIME=[6A9A1960:01C88834] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id m2HDeT2D021666 Hi again, Resolution proposal for Issue 11781 (NFP) has been published (http://www.omgwiki.org/marte/lib/exe/fetch.php?id=nfp_wg&cache=cache&me dia=11781_resolved_ballot1.doc ). In short: "...we define an alternative graphical syntax for value specifications having NfpType as data type. This syntax consists of a pair of a value and a unit.." 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