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

fixed refactoring.html layout.

parent 5948afaf
No related branches found
No related tags found
1 merge request!31Task 4006 online help content
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--
Documentation of the refinement functionality of AF3.
@author mou
@ConQAT.Rating GREEN Hash: CE126443570E8B101333C88A63B23B86
-->
<!-- User documentation for refactoring feature. -->
<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>Refactorings in AutoFOCUS (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="data_dictionary.html">Data Dictionary: Types and Functions</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 Operator Panels</a>
<a href="cosimulation_with_af3.html">Simulation -> Co-Simulation and FMI Support</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 'refactoring.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>
<h1><u><font color="#336698">Refactorings in AutoFOCUS (AF3)</font></u></h1>
<h2>Refactorings in AutoFOCUS (AF3)</h2>
<p>The following sections will discuss the refactoring feature of AF3</p>
<h3>Renaming</h3>
<h2><font color="#336699">Renaming</font>
</h2>
<p>AF3 offers the possibility to rename a type or a value, and to <i>propagate</i> the change to the rest of the model.
To do so, right-click on the element that you want to rename in the data dictionary, and select the "Rename refactoring..." option:</p>
AF3 offers the possibility to rename a type or a value, and to <i>propagate</i> the change to the rest of the model.
To do so, right-click on the element that you want to rename in the data dictionary, and select the "Rename refactoring..." option:
<br><br>
<img src="./pictures/refactoring_renaming_menu.png">
<br><br>
A dialog pops up requesting the new name:
<br><br>
<p>A dialog pops up requesting the new name:</p>
<img src="./pictures/refactoring_renaming_dialog.png">
<br><br>
When pressing "OK", occurrences of the type or value will be replaced automatically:
<p> pressing "OK", occurrences of the type or value will be replaced automatically:
typically in ports in the component architecture, or in transitions of state automata.
According to the remark displayed in the dialog, notice that AF3 will do its best to find all occurrences, but it is not guaranteed that all
of these are found.
of these are found.</p>
<h2><font color="#336699">Pack components</font></h2>
<h3>Pack components</h3>
<p>The "Pack Component" feature allows the user to select several components in a component diagram editor and wrap them into a new component.
To use this feature, select a set of components (only the components: no ports or channels!), right-click, and select "Pack Component" in the context menu of the model navigator.</p>
The "Pack Component" feature allows the user to select several components in a component diagram editor and wrap them into a new component.
<br><br>
To use this feature, select a set of components (only the components: no ports or channels!), right-click, and select "Pack Component" in the context menu of the model navigator.
<br><br>
<img src="./pictures/refactoring_packing_unpacked.png">
<br><br>
A new component gathering all the selected components will then be created automatically by AF3.
Note however that the position and size of the new component need to be adjusted manually.
<br><br>
<p>A new component gathering all the selected components will then be created automatically by AF3.<br>
<b><u>Note:</u></b> however that the position and size of the new component need to be adjusted manually.</p>
<img src="./pictures/refactoring_packing_packed.png">
<br><br>
</div>
<script src="../layout/jsscript/topBtn.js">
</script>
</body>
</html>
</html>
\ No newline at end of file
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment