Skip to content
Snippets Groups Projects
Commit 03908e9e authored by Saad bin Abid's avatar Saad bin Abid
Browse files

Fixed layout for component_architecture.html and data_dictionary.html. 

Issue-Ref: 4007
Issue-Url: https://af3-developer.fortiss.org/issues/4007



Signed-off-by: default avatarSaad bin Abid <abid@fortiss.org>
parent be189229
No related branches found
No related tags found
1 merge request!31Task 4006 online help content
Hide whitespace changes
Inline Side-by-side
org.fortiss.af3.rcp.help/html/ModandSim/component_architecture.html
+ 1
− 1
View file @ 03908e9e
......@@ -60,7 +60,7 @@
</div>
</div>
<div class="box">
<button onclick="topFunction()" id="upBtn" title="Go to top">Top</button>
<h2>Creating a Component Architecture</h2>
<p>Following sub-sections discuss the creation of <i>Component Architecture</i></p>
......
org.fortiss.af3.rcp.help/html/ModandSim/data_dictionary.html
+ 81
− 47
View file @ 03908e9e
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--
Documentation of Defining a Data Dictionary.
@author becker
@ConQAT.Rating GREEN Hash: C359C5FBF27AA4D36ECA49D9504DA64A
-->
<!-- Documentation of Defining a Data Dictionary. -->
<html>
<head>
<link rel="stylesheet" type="text/css" href="../layout/stylesheet.css">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Defining a Data Dictionary using AutoFOCUS3 (AF3)</title>
</head>
<body>
<div class="header">
<div class="box">
<div class="navbar">
<!--a href="https://www.fortiss.org/" align="left">
<img src="fortiss-logo.png" width="90px" height="20px" align="left">
</a-->
<div class="dropdown">
<button class="btn" id="hamburger">
<label for="hamburger" class="hamburger">
<span class="hamburgerLine"></span>
<span class="hamburgerLine"></span>
<span class="hamburgerLine"></span>
</label>
</button>
<div class="dropdown-content">
<a href="../getting_started.html"> Main Page</a>
<a href="../requirements/MIRA.requirements.html">Requirements Engineering</a>
<a href="#">Deployment and Code Generation</a>
<a href="#">Design Space Exploration (DSE)</a>
<a href="#">Assurance Case Modeling</a>
<a href="#">Further Resources</a>
</div>
</div>
<div class="dropdown">
<button class="dropbtn">Modeling and Simulation <i class="triangle"></i></button>
<div class="dropdown-content">
<a href="model_element_attributes.html">Introduction to Graphical Modeling Interface</a>
<a href="component_architecture.html">Component Architecture Modeling</a>
<a href="code_specification.html">Behavior Modeling -> Code Specifications</a>
<a href="state_automaton.html">Behavior Modeling -> State Automata</a>
<a href="hierarchical_state_automaton.html">Behavior Modeling -> Hierarchical State Automata</a>
<a href="mode_automaton.html">Behavior Modeling -> Mode Automata</a>
<a href="simulation_with_af3.html">Simulation -> Simulation</a>
<a href="operatorpanels.html">Simulation -> Operator Panels</a>
<a href="operatorpanels_advanced.html">Simulation -> Advanced interface</a>
<a href="cosimulation_with_af3.html">Simulation -> Co-Simulation and FMI Support</a>
<a href="refactoring.html">Refactoring</a>
<a href="model_markers_view.html">On-the-fly Checks</a>
</div>
</div>
<div class="topnav-right">
<a href="mailto:af_user@lists.fortiss.org?subject=Reporting 'Data_Dictionary.html' Documentation Problem!&body= Dear Af3 team, I am reporting an issue related to 'modelling and simulation'.
{Please specify the problem precisely here.}.">Report a Problem?</a>
</div>
</div>
</head>
</div>
</div>
<div class="box">
<button onclick="topFunction()" id="upBtn" title="Go to top">Top</button>
<h2>Data Dictionary: Types and functions</h2>
<h2><u><font color="#336699">Data Dictionary: Types and functions</font></u></h2>
AF3 allows you to define your own datatypes and functions by using a socalled "Data Dictionary".
<br>
To create such a Data Dictionary, right-click at the root of your project and select "Data Dictionary", as shown below:
<p>AF3 allows you to define your own datatypes and functions by using a socalled "Data Dictionary". To create such a Data Dictionary, right-click at the root of your project and select "Data Dictionary", as shown below:</p>
<br><br>
<img src="./pictures/DataDictionary.Add.png">
<br><br>
You can then add the following elements to your Data Dictionary:
<p>You can then add the following elements to your Data Dictionary:
<ul>
<li>Enumeration</li>
<li>Structure</li>
<li>Array</li>
<li>Function</li>
</ul>
These can be added by drag-and-drop from the model elements palette or by the context menu (right-click)
<br>of the data dictionary itself in the model navigator.
</p>
<p>These can be added by drag-and-drop from the model elements palette or by the context menu (right-click) of the data dictionary itself in the model navigator.</p>
We describe below every of these elements in more details: what they consist of, how to define them,
<br>as well as the <i>syntax</i> to use to refer to the data items they define. The latter is particularly
<br>useful, e.g., in Guards and Actions of <a href="state_automaton.html"><i>State Automata</i></a> or in <a href="code_specification.html"><i>Code Specifications</i></a>.
<p>We describe below every of these elements in more details: what they consist of, how to define them, as well as the <i>syntax</i> to use to refer to the data items they define. The latter is particularly
useful, e.g., in Guards and Actions of <a href="state_automaton.html"><i>State Automata</i></a> or in <a href="code_specification.html"><i>Code Specifications</i></a>.</p>
<h3>Enumeration</h3>
An enumeration is a data type defined as a finite list of values. Variables of this type can only contain a value which belong to this list.
<br>This is similar to "unions" in C, or to "sum types" in functional languages.
<br>After having created an enumeration, you can add elements to it by drag and dropping "enumeration members" from the
<br>palette or by right-clicking the enumeration in the data dictionary editor.
<p> An enumeration is a data type defined as a finite list of values. Variables of this type can only contain a value which belong to this list. This is similar to "unions" in C, or to "sum types" in functional languages. After having created an enumeration, you can add elements to it by drag and dropping "enumeration members" from the
palette or by right-clicking the enumeration in the data dictionary editor.</p>
<p><i>Syntax</i>: an enumeration member can be accessed by writing its name followed by "()" (this allows to distinguish enumeration members from ports).
<br>For instance, referring to the elements of the enumeration defined below is done by writing "Green()", "Red()", "RedYellow()", "Yellow()".
For instance, referring to the elements of the enumeration defined below is done by writing "Green()", "Red()", "RedYellow()", "Yellow()". </p>
<br>
<img src="./pictures/DataDictionary.Enumeration.png">
<br><br>
<h3>Structure</h3>
A structure is a data type which allows to gather various values in one variable, each value being uniquely identified by a structure member <i>name</i>.
<br>One can for instance state a value shall always have a member called "x" of type integer and a member called "y" of type boolean.
<br>This is similar to "records" in C, or to "product types" in functional languages.
<br>After having created a structure, you can add elements to it by drag and dropping "structure members" from the
<br>palette or by right-clicking the structure in the data dictionary editor.
<p> A structure is a data type which allows to gather various values in one variable, each value being uniquely identified by a structure member <i>name</i>. One can for instance state a value shall always have a member called "x" of type integer and a member called "y" of type boolean.
This is similar to "records" in C, or to "product types" in functional languages. After having created a structure, you can add elements to it by drag and dropping "structure members" from the
palette or by right-clicking the structure in the data dictionary editor. </p>
<p><i>Syntax</i>: a structure member of a variable "v" can be accessed by writing "v.MEMBER_NAME".
<br>For instance, for the example structure mentioned in the previous paragraph, one would access the integer by "v.x" and the boolean by "v.y".
<br>Creating a structure is done with the syntax "{member_name_1: value_1, member_name_2: value_2, ...}". With the same example above: "{ x: 1, y: true }".
<p><i>Syntax</i>: a structure member of a variable "v" can be accessed by writing "<tt>v.MEMBER_NAME"</tt>.
For instance, for the example structure mentioned in the previous paragraph, one would access the integer by "<tt>v.x</tt>" and the boolean by "<tt>v.y</tt>".
Creating a structure is done with the syntax "<tt>{member_name_1: value_1, member_name_2: value_2, ...}</tt>". With the same example above: "<tt>{ x: 1, y: true }</tt>".
</p>
......@@ -71,12 +106,12 @@ A structure is a data type which allows to gather various values in one variable
Arrays are like usual C arrays, but <i>their size is defined in the datatype itself</i>.
<p><i>Syntax</i>: Given a variable "v" whose type is an array, the i-th element can be accessed by the expression
<br>"v[i]". The index starts from 0. Assigning a value x to the i-th element is done with the syntax "v[i] = x".</p>
"<tt>v[i]</tt>". The index starts from 0. Assigning a value x to the i-th element is done with the syntax "<tt>v[i] = x</tt>".</p>
<h3>Function</h3>
Functions denote small functions which can be used in various places in an AF3 project.
<br><i>Note:</i>Functions are not a type but are still defined in the data dictionary.
<p>Functions denote small functions which can be used in various places in an AF3 project. <i>Note:</i>Functions are not a type but are still defined in the data dictionary.
</p>
<p>Functions have:
<ul>
......@@ -86,24 +121,23 @@ Functions denote small functions which can be used in various places in an AF3 p
<li>a return type
<li>a definition
<i>Note:</i> the definition cannot contain local variables!
<br>(this means that practically, most function definitions contain only "if" and "return" statements.)
<i>Note:</i> the definition cannot contain local variables! (this means that practically, most function definitions contain only "if" and "return" statements.)
</ul>
(see next figure for an example).
</p>
<img src="./pictures/DataDictionary.Definitions.png">
<br><br>
<h3>Evaluator</h3>
If you want to check your defined functions, AutoFOCUS provides an Evaluator for the Data Dictionary.
<br>Simply click onto the Evaluator-Tab and insert commands into the lower field. The upper field shows the results of your inputs.
<br>As you can see in the following Example, the Function "tRed()" returns 5 as defined.
<p>If you want to check your defined functions, AutoFOCUS provides an Evaluator for the Data Dictionary. Simply click onto the Evaluator-Tab and insert commands into the lower field. The upper field shows the results of your inputs.
As you can see in the following Example, the Function "tRed()" returns 5 as defined. </p>
<br><br>
<img src="./pictures/DataDictionary.Evaluator.png">
<br><br>
</font>
</div>
<script src="../layout/jsscript/topBtn.js">
</script>
</body>
</html>
\ No newline at end of file
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment