Difference between pages "File:ClipCapIt-210224-160016.PNG" and "TASTE DataView/IV/DV/CV Graphical Editor"

From TASTE
(Difference between pages)
Jump to: navigation, search
(This file was uploaded from the clipboard (Category:Clipboard upload).)
 
(Created page with "= Introduction = The TASTE 2.0 editor is a new graphical editor that replaces the three pre-existing ones in the TASTE tool-chain. The concerned tools are the Interface View...")
 
Line 1: Line 1:
This file was uploaded from the clipboard ([[Category:Clipboard upload]]).
+
= Introduction =
 +
 
 +
The TASTE 2.0 editor is a new graphical editor that replaces the three pre-existing ones in the TASTE tool-chain. The concerned tools are the Interface View editor (IV), the Deployment View editor (DV) and the Concurrency View editor (CV). The tool provides the following functionalities for the TASTE modelling activities:
 +
 
 +
* Full integration of the IV-DV activities within a single tool
 +
* Enhanced support for reuse of IV models and components
 +
* Updated real-time analysis tools for the CV, including the most recent version of the Cheddar scheduling analysis framework and of the Marzhin AADL simulator.
 +
 
 +
The TASTE modelling workflow is thus significantly simplified as shown in Figure [[#img-taste-workflow|???]].
 +
 
 +
[[File:tasteWorkflow.png|TASTE workflow]]
 +
 
 +
The TASTE editor uses various background technologies:
 +
 
 +
* GMP (Graphic Model Processing): generic graphical framework developed by Ellidiss Technologies.
 +
* LMP (Logic Model Processing): generic model transformation and AADL toolbox developed by Ellidiss Technologies.
 +
* [http://beru.univ-brest.fr/~singhoff/cheddar Cheddar] : real-time scheduling analysis tool developed by the University of Brest and Ellidiss Technologies.
 +
* Marzhin : AADL run-time simulator developed by Virtualys and Ellidiss Technologies.
 +
* [http://www.openaadl.org/ocarina.html Ocarina] : AADL compiler and code generator developed by ISAE.
 +
 
 +
= Installation =
 +
 
 +
The TASTE editor are embedded into the standard TASTE tool-chain distribution. The current TASTE tool-chain distribution is available at the following address:
 +
 
 +
http://download.tuxfamily.org/taste/TASTE-VM-10-64bit.ova
 +
 
 +
It consists of a LinuxVMWare image that can be run with a VMWare player. There is no specific installation procedure regarding the TASTE editors.
 +
 
 +
Various customizations are available for the TASTE editors. In particular, the IVConfig.ini, DVConfig.ini, AIConfig.ini and TasteConfig.ini files within the config directory may be used to apply a few user configurations.
 +
 
 +
Please note that the use of the TASTE editors is subject to the General Clauses and Conditions (GCC) applying to contracts placed by the European Space Agency (ESA). Dedicated distribution and end-user licences are also applicable for the TASTE editor and the use of the corresponding background technologies. Refer to the License.pdf file located in the doc directory of the TASTE editor distribution.
 +
 
 +
For any technical or commercial question related to the TASTE editors that are described in this manual, please contact the Ellidiss support team:
 +
 
 +
[mailto:taste@ellidiss.com taste@ellidiss.com]
 +
 
 +
= Overview of the TASTE graphical editor =
 +
 
 +
The new TASTE graphical editor now consists of a single window that encompasses:
 +
 
 +
* A main menu and button bar. The button bar is updated upon the current modelling or verification activity, as defined by the selection tab.
 +
* A models browser where the overall project hierarchy and organization is displayed in a deployable tree structure. This browser may be hidden from the View main menu.
 +
* A set of selection tabs to enable one of the proposed TASTE modelling or verification activity, and update the content of the working area.
 +
* A working area, showing either:
 +
** A textual editor where the ASN.1 and ACN representations of a TASTE DataView model can be edited, or
 +
** A box-arrow editor where a graphical representation of a TASTE Interface View or Deployment View model can be edited, or
 +
** A read-only area showing the results of the timing analysis of a TASTE Concurrency View model, or
 +
** A read-only textual editor that displays the generated textual AADL code
 +
* A log view where main editing operations are logged. This log view is hidden by default and can be made visible from the View main menu.
 +
* A status bar showing system information, warning and error messages
 +
 
 +
[[File:tasteOverview.png|TASTE Overview]]
 +
 
 +
= About TASTE AADL models =
 +
 
 +
The TASTE models that can be loaded into and saved from the TASTE editor are serialised in AADL format. The AADL language is a SAE international standard that is used to model and analyse the architecture of safety critical real time systems. More information about AADL can be found at:
 +
 
 +
http://www.openaadl.org/
 +
 
 +
For the purpose of TASTE models serialisation, only a subset of the AADL language is used, and the TASTE entities are associated with specific AADL constructs that have been defined to ensure a correct semantic mapping. A TASTE project makes use of several kinds of models. Each of them is associated with a dedicated AADL subset. These models are:
 +
 
 +
* DataView: automatically generated from ASN.1 source code.
 +
* Interface View: automatically generated from the Interface View diagram.
 +
* Hardware Library: provided by the Ocarina environment.
 +
* Deployment View: automatically generated from the Deployment View diagram.
 +
* Concurrency View: automatically generated by the TASTE Build Support utility.
 +
* Customised Properties: specified by the TASTE_IV_Properties and TASTE_DV_Properties files located in the config directory of the TASTE editor distribution.
 +
 
 +
All the AADL files that are involved in a TASTE project are either provided or automatically generated. It is thus not necessary – and even not recommended - for a TASTE end-user to edit the AADL models. Directly editing the provided or generated AADL files may lead to load errors and model corruption.
 +
 
 +
Within the TASTE editor, the AADL files can be loaded either in a generic way from the File main menu (Load), or for a particular kind of model from the contextual menus of the models browser (Load DataView, Load IV, Load DV, Load CV). The generic load process only works for AADL files that have been produced by version 2.0 or greater of the TASTE editor. Older files can be made compatible by adding a comment line at the beginning of the AADL file to specify which kind of TASTE model is concerned:
 +
 
 +
<pre>-- type dataview
 +
-- type interfaceview
 +
-- type deploymentview
 +
-- type concurrencyview
 +
-- type hwlibrary</pre>
 +
Note that only one model of each kind can be loaded at a time. A new load action will replace the previously loaded model. When it is required to have access to several models of the same kind, the import menu must be used instead. This is in particular the case for reusing components from another Interface View model.
 +
 
 +
Also note that loading an IV model automatically loads the referenced DataView. Similarly, loading a DV model automatically loads the referenced HW Library and IV, as well as the DataView referenced by this IV. When a new DataView is explicitly or implicitly loaded, it is merged with the already loaded ones. This action may raise an error when the ASN.1 toolbox is not available (i.e. outside the TASTE VM), but does not prevent the DataView to be used for modelling activities.

Revision as of 15:02, 24 February 2021

Introduction

The TASTE 2.0 editor is a new graphical editor that replaces the three pre-existing ones in the TASTE tool-chain. The concerned tools are the Interface View editor (IV), the Deployment View editor (DV) and the Concurrency View editor (CV). The tool provides the following functionalities for the TASTE modelling activities:

  • Full integration of the IV-DV activities within a single tool
  • Enhanced support for reuse of IV models and components
  • Updated real-time analysis tools for the CV, including the most recent version of the Cheddar scheduling analysis framework and of the Marzhin AADL simulator.

The TASTE modelling workflow is thus significantly simplified as shown in Figure ???.

TASTE workflow

The TASTE editor uses various background technologies:

  • GMP (Graphic Model Processing): generic graphical framework developed by Ellidiss Technologies.
  • LMP (Logic Model Processing): generic model transformation and AADL toolbox developed by Ellidiss Technologies.
  • Cheddar : real-time scheduling analysis tool developed by the University of Brest and Ellidiss Technologies.
  • Marzhin : AADL run-time simulator developed by Virtualys and Ellidiss Technologies.
  • Ocarina : AADL compiler and code generator developed by ISAE.

Installation

The TASTE editor are embedded into the standard TASTE tool-chain distribution. The current TASTE tool-chain distribution is available at the following address:

http://download.tuxfamily.org/taste/TASTE-VM-10-64bit.ova

It consists of a LinuxVMWare image that can be run with a VMWare player. There is no specific installation procedure regarding the TASTE editors.

Various customizations are available for the TASTE editors. In particular, the IVConfig.ini, DVConfig.ini, AIConfig.ini and TasteConfig.ini files within the config directory may be used to apply a few user configurations.

Please note that the use of the TASTE editors is subject to the General Clauses and Conditions (GCC) applying to contracts placed by the European Space Agency (ESA). Dedicated distribution and end-user licences are also applicable for the TASTE editor and the use of the corresponding background technologies. Refer to the License.pdf file located in the doc directory of the TASTE editor distribution.

For any technical or commercial question related to the TASTE editors that are described in this manual, please contact the Ellidiss support team:

taste@ellidiss.com

Overview of the TASTE graphical editor

The new TASTE graphical editor now consists of a single window that encompasses:

  • A main menu and button bar. The button bar is updated upon the current modelling or verification activity, as defined by the selection tab.
  • A models browser where the overall project hierarchy and organization is displayed in a deployable tree structure. This browser may be hidden from the View main menu.
  • A set of selection tabs to enable one of the proposed TASTE modelling or verification activity, and update the content of the working area.
  • A working area, showing either:
    • A textual editor where the ASN.1 and ACN representations of a TASTE DataView model can be edited, or
    • A box-arrow editor where a graphical representation of a TASTE Interface View or Deployment View model can be edited, or
    • A read-only area showing the results of the timing analysis of a TASTE Concurrency View model, or
    • A read-only textual editor that displays the generated textual AADL code
  • A log view where main editing operations are logged. This log view is hidden by default and can be made visible from the View main menu.
  • A status bar showing system information, warning and error messages

TASTE Overview

About TASTE AADL models

The TASTE models that can be loaded into and saved from the TASTE editor are serialised in AADL format. The AADL language is a SAE international standard that is used to model and analyse the architecture of safety critical real time systems. More information about AADL can be found at:

http://www.openaadl.org/

For the purpose of TASTE models serialisation, only a subset of the AADL language is used, and the TASTE entities are associated with specific AADL constructs that have been defined to ensure a correct semantic mapping. A TASTE project makes use of several kinds of models. Each of them is associated with a dedicated AADL subset. These models are:

  • DataView: automatically generated from ASN.1 source code.
  • Interface View: automatically generated from the Interface View diagram.
  • Hardware Library: provided by the Ocarina environment.
  • Deployment View: automatically generated from the Deployment View diagram.
  • Concurrency View: automatically generated by the TASTE Build Support utility.
  • Customised Properties: specified by the TASTE_IV_Properties and TASTE_DV_Properties files located in the config directory of the TASTE editor distribution.

All the AADL files that are involved in a TASTE project are either provided or automatically generated. It is thus not necessary – and even not recommended - for a TASTE end-user to edit the AADL models. Directly editing the provided or generated AADL files may lead to load errors and model corruption.

Within the TASTE editor, the AADL files can be loaded either in a generic way from the File main menu (Load), or for a particular kind of model from the contextual menus of the models browser (Load DataView, Load IV, Load DV, Load CV). The generic load process only works for AADL files that have been produced by version 2.0 or greater of the TASTE editor. Older files can be made compatible by adding a comment line at the beginning of the AADL file to specify which kind of TASTE model is concerned:

-- type dataview
-- type interfaceview
-- type deploymentview
-- type concurrencyview
-- type hwlibrary

Note that only one model of each kind can be loaded at a time. A new load action will replace the previously loaded model. When it is required to have access to several models of the same kind, the import menu must be used instead. This is in particular the case for reusing components from another Interface View model.

Also note that loading an IV model automatically loads the referenced DataView. Similarly, loading a DV model automatically loads the referenced HW Library and IV, as well as the DataView referenced by this IV. When a new DataView is explicitly or implicitly loaded, it is merged with the already loaded ones. This action may raise an error when the ASN.1 toolbox is not available (i.e. outside the TASTE VM), but does not prevent the DataView to be used for modelling activities.

File history

Click on a date/time to view the file as it appeared at that time.

Date/TimeThumbnailDimensionsUserComment
current15:00, 24 February 2021Thumbnail for version as of 15:00, 24 February 2021478 × 131 (6 KB)Mperrotin (talk | contribs)This file was uploaded from the clipboard (Category:Clipboard upload).
  • You cannot overwrite this file.

The following page links to this file: