Merge branch '3949' into 'master'

3949

See merge request !22

org.fortiss.af3.rcp.help/html/.ratings

-MIRA.aspects.html 05fd84eace5f6694244a7949657aa3fc3e93df02 RED
-MIRA.aspects2.html e761406ccf2f1caec8b1744999283aa51cc7f27a RED
-MIRA.export_report.html c26f9ecc02518415966d711c6f9cc263335a445c RED
-MIRA.glossary.html f9e5c3db7e70ec740a4da58167433059e86811b1 RED
-MIRA.glossary2.html f0f4ff9b771d96001bdac388b88590716581c573 RED
-MIRA.requirement_source.html 0ba593ffb01e972c1a4928ffe3d7c5856d9ffffd RED
-MIRA.requirement_source2.html 5fc52fcd8527b0b0c1418b88a9a51affc641aaa2 RED
-MIRA.requirements.html e88d7fafe58af7e6b22926bb153f53af262103f5 RED
-MIRA.requirements_analysis.html 7cdd8ed3604b697c8e8f09ab251d9a0087005f70 RED
-MIRA.requirements_analysis2.html d8a27745b2db24883e473f4a819337d4268cb261 RED
-MIRA.what_is_MIRA.html 3b6528f3da42ff9dc142251243e8340307540740 RED
+MIRA.glossary.html 72db44909e982b0a3999054fbbf3dc589cb235d1 GREEN
+MIRA.requirements.html b0cc481d8fce753a834572074d96b4ef35b4a308 GREEN
+MIRA.requirements_analysis.html 8201ce94671b5d1ad453dee4b23257452de5a004 GREEN
 af3_faq.html 5fcc2680c2ababe82b6f8bf9bffc120d08476ac8 GREEN
 code_specification.html 6abb0c1e49b2545e5b3d81444481689ca5bbd611 RED
 component_architecture.html 5a01c22bbfb55839ef8d05e5850a926173f9452c RED
@@ -16,7 +8,6 @@ cosimulation_with_af3.html a2daa6bb9a39083cf2498df26df54572f69c38da RED
 data_dictionary.html 1cfdcfe5879e210456f78095a8b7b4790ab409af RED
 getting_started.html 0a0a2f68bda7f69787169714c140c265db0c7bbe RED
 hierarchical_state_automaton.html cebd924f514cd50f229c7745e173f76bd0c0038b RED
-library.html 4dcbc369f70cc5ba943404da07e15955df65b3fc RED
 loading_standard_examples.html a2693477f0afb902f2899d12b3166f01378f6d8d RED
 mode_automaton.html dc395eab03cb6920580f54e317c3d203e64cb496 RED
 model_element_attributes.html 778a7ff5b5be649b43ec014dd0f7098fd70a6e10 RED
@@ -24,11 +15,6 @@ model_markers_view.html 9b555dfff011f385fdde640f81ddfe0e5b5edf40 RED
 model_testing.html 1337b89d2933f98c3ce76fb70a5e2f96c34c8613 RED
 operatorpanels.html a5343a0ad3a8421da55bf809e831b61d968c5623 RED
 operatorpanels_advanced.html f48da6255d25f04cf83e5c181bfeba5c537bcfd4 RED
-process.html 85b2291750c54d14d06aada3803c2cc9fbf6b2fd RED
-process_constraints.html 32fe5cad678907d6e610ff69af49656ea4383105 RED
-process_constraints_definition.html b176d4e6070e292abe1cfd38920f2f7bc6bb7ed1 RED
-process_definition.html e8ad097c1bab232f067b4fc614a8389245b7e89c RED
-process_usage.html cb2acbc3b8200c452d4de3aebc91a5bcdd49d9a6 RED
 refactoring.html cdfd1f78f6cb543ad3643eecf8f7c5f5130fe9b6 RED
 safety.html 5f7d5b677b31bc916ec2c62d82b44502c0705a2d RED
 scheduling.html 94646464662c1745795ab1954dfcc5f469fdaee7 RED

org.fortiss.af3.rcp.help/html/MIRA.glossary.html

@@ -31,24 +31,6 @@ You can create multiple glossary nodes with specific names (set in the propertie
 In the context menu of the glossary node you can then create glossary entries by clicking <i>Entry</i>.
 <br><br> 
 <img src="./pictures/MIRA.Glossary.NewEntry.png">
-<br><br>
-
-An alternative way to create a new glossary entry is to select a word in glossary entry, requirement source element or requirement editor, right-click on it and choose <i>Create glossary entry</i>. 
-If no glossary exists yet, a new one is created; if multiple glossaries exist, you are asked where the entry should be created. 
-<br><br> 
-<img src="./pictures/MIRA.Glossary.ContextMenu.png">
-<br><br>
-If no word is selected in the editor while choosing <i>Create glossary entry</i>, an appropriate word will be automatically chosen according to the actual context.
-The chosen word is displayed in a confirmation dialog. Click the button <i>OK</i> to create a new glossary entry with this word. 
-If there is no appropriate word, an error dialog will appear.
-<br><br> 
-<img src="./pictures/MIRA.Glossary.ConfirmDialog.png">
-<br>
-Confirm dialog
-<br><br> 
-<img src="./pictures/MIRA.Glossary.ErrorDialog.png">
-<br>
-Error dialog
 
 <h2><font color="#336699">Glossary Overview</font></h2> 
 
@@ -77,81 +59,6 @@ You can add as many pictures as you want.
 Each image has a description field which can be used to give information about the picture and to number the pictures.
 If you click on an added picture, it should be displayed in full resolution in your systems picture viewer.  <br> 
 When you add a picture it is copied into the <i>Images</i> folder in the project directory, next to your .af3_20 file. 
-If you want to send the model file to someone else, you should also send the <i>Images</i> folder.
- 
-<h2><font color="#336699">Consolidating Glossary Entries</font></h2>
-
-The <i>status</i> field supports the consolidation of glossary entries (and requirement sources). We assume that there are two groups of persons involved in the consolidation process. 
-The first group of people documents the glossary entries; we call these persons the requirements engineers.  
-The second group of people has to agree on the terms in the glossary; we call these persons now the decision makers. 
-These groups can of course overlap or even be identically. Typically, these two groups are defined when a project starts. Typical members of decision makers are for example the client or the product manager.
-
-<br><br>
-Every requirement engineer can document new glossary terms and add definitions, abbreviations and so on. The status for new terms is <i>new</i>. 
-
-When a requirements engineer decides that the <i>new</i> term is sufficiently described, he can set the status to <i>in consolidation</i>.
-
-For a terms that is <i>in consolidation</i>, the decision makers have to agree on that term, its definition and so on. 
-When all decision makers agree, then the status of this term can be set to <i>consolidated</i>.
-
-If a term is <i>consolidated</i> and a decision maker thinks that this term is not defined correctly, then he/she can set the status back to <i>new</i> which triggers a new round of consolidation.
-
-<br><br>
-
-The <i>status</i> field can be filtered in the <i>Glossary Overview</i> in order to determine the list of terms that are 
-<i>new</i>, <i>in consolidation</i> or <i>consolidated</i>.
-
-<h2><font color="#336699">Connection between Glossaries, Requirement Source Elements and Requirements</font></h2>
-
-<br>
-After you specified your glossary entries, they will be highlighted when you use the terms in the glossary entries, requirement source elements and requirements specifications. 
-Blue color is used to mark a <i>name</i> or an <i>abbreviation</i> of a glossary term as well as requirement sources.
-Red is used to mark a <i>synonym</i>.
-
-<br><br>
-The highlighting function features correct recognition of multiple word terms that are split by blanks or special characters.
-Also terms surrounded by special characters like brackets or slashes are correctly highlighted.
-An additional feature is the maintained highlighting with terms followed by plural "s" or "es" endings.
-
-<br><br> 
-<img src="./pictures/MIRA.Glossary.Highlighting.png">
-<br><br>
-Furthermore matching glossary entries and requirement source element will be presented to you when you start typing a name and pause for a second. 
-If you choose one of the suggestions, the rest of the name will be inserted automatically. 
-<br><br> 
-<img src="./pictures/MIRA.Glossary.Autocomplete.png">
-<br><br>
-
-When you hold the mouse cursor for a second on a highlighted term, a pop-up will show additional information. 
-In the pop-up you can see the definition of the glossary entry/requirement source element and whether the marked occurrence is an abbreviation
- or a synonym of this entry/element. If the entry contains images, the first image is shown in the pop-up window as well. 
- When you click on the name in the pop-up, the editor for this glossary entry/requirement source element will be opened. 
-<br><br>
-<img src="./pictures/MIRA.Glossary.PopupHover.png">
-<br><br>
-If there are two or more requirement source elements and/or glossary entries with the same name, <i>Stakeholder</i> has the highest priority, and then <i>Document</i>,
-then <i>External system</i>, and at last <i>Glossary Entry</i>. Name with higher priority is in the front of pop-up and the highlight color is the color of the name/term with highest priority.
-<br><br>
-<img src="./pictures/MIRA.RequirementSource.Priority.png">
-<br><br>
-The glossaries always belong to one <i>Requirements Analysis</i> node. The glossary entries of one <i>Requirements Analysis</i> node will not be highlighted in another <i>Requirements Analysis</i> node. 
-<br><br>
-<h2><font color="#336699">Glossary Occurrences</font></h2>
-<br>
-By double-clicking onto a Glossary Entry, an overview over all glossary entry occurrences page is opened as a second window.
-<br><br>
-In the usage statistics section, the number of <b>exact</b> occurrences of the glossary term in <i>Documents</i>, <i>Requirements</i> or another <i>Glossary Entries</i> is given,
-as well as in <i>Arrays</i>, <i>Enumerations</i> and <i>Structures</i> which are found in the data dictionaries.
-The Filter option helps to filter the list of occurrences. Each element of the list can be opened by double-clicking the entry in the <i>Overview</i> section.
-<br><br>
-Additionally, the search can be extended to similar words via the <i>Similarity</i> slider. Similar terms are then included in the overview list. 
-The similarity is calculated based on the <a href="http://en.wikipedia.org/wiki/Levenshtein_distance">Levenshtein Distance</a>. Every step of the
-slider increases the search distance by 1, thereby allowing more words with bigger differences in the overview list. The similarity search respects plural endings and special chars to a certain extent. 
-Words shorter than 4 letters, for example abbreviations, are excluded from the similarity search, 
-as this would lead to bulk lists containing nonsense.
-
-<br><br>
-<img src="./pictures/MIRA.Glossary.GlossaryOccurences.png">
-
+If you want to send the model file to someone else, you should also send the <i>Images</i> folder. 
 </body>
 </html>
\ No newline at end of file

org.fortiss.af3.rcp.help/html/MIRA.requirements.html

@@ -27,7 +27,7 @@ Change the name of a <i>Requirements</i> node in the properties view. You also c
 
 <p>By double-clicking on the <i>Requirements</i> node, an overview over all requirements opens.<br />
 <br />
-<img src="./pictures/MIRA.Requirements.RequirementOverview.png" /><br />
+<img src="./pictures/MIRA.RequirementsOverview.png" /><br />
 <br />
 The list of requirements can be sorted by clicking on the column headers of the overview list. You can filter the requirements by inserting a filter text in the filter section. Double-clicking on a column opens the corresponding requirement source element.</p>
 
@@ -42,269 +42,5 @@ The list of requirements can be sorted by clicking on the column headers of the
 <p>To add a new requirement, open the context menu of the requirements node. You can choose between the following requirement types:</p>
 
 <p><img src="./pictures/MIRA.Requirements.NewRequirement.png" /><br />
-<br />
-<br />
-<br />
-Requirements consist of four respectively five sections:</p>
-
-<ul>
-	<li><i>General</i>: Here all requirements management fields are located together with the fields describing the requirement informal.</li>
-	<li><i>Images</i>: Here you can add images to the entry.</li>
-	<li><i>Detail</i>: The specific fields for this requirements type are shown in this tab. Only for specific requirements.</li>
-	<li><i>Traces</i>: Relations between requirements and to architecture are managed here.</li>
-	<li><i>Safety</i>: Here you can specify safety-related information.</li>
-	<li><i>Comment</i>: This tab is for comments.</li>
-</ul>
-
-<p><img src="./pictures/MIRA.Requirements.Sections.png" /></p>
-
-<h3><font color="#336699">Section General</font></h3>
-
-<p>In this section you can enter typical requirement management information.<br />
-<br />
-The <i>Document Reference</i> connects the requirement with a source <i>Document</i> from the <i>Requirement Sources</i>. You can add a page number for local documents. When clicking on the reference, the document opens automatically at that page.</p>
-
-<h3><font color="#336699">Section Images</font></h3>
-
-<p>For further description of the entry you can add pictures in the <i>Images</i>-section. To add a picture click on the <i>Add</i> button and choose an image file in the dialog. You can add as many pictures as you want. If you add a picture, it will be copied into the <i>images</i> folder in the <i>AF3-Project-Directory</i>, next to your .af3_20 file. If you want to send the model file to someone else, you should also send the <i>images</i> folder. Each image has a description field which can be used to give information about the picture and to number the pictures. If you click on an added picture, it should be displayed in full resolution in your systems picture viewer.<br />
-&nbsp;</p>
-
-<h3><font color="#336699">Section Detail</font></h3>
-
-<p>This section contains the typical information for this kind of requirement.<br />
-&nbsp;</p>
-
-<h3><font color="#336699">Section Traces</font></h3>
-
-<p>Requirements can be traced to other requirements to document relations between requirements or to components to document the realization of requirements in the architecture.</p>
-
-<h4><font color="#336699">Traces within requirements</font></h4>
-
-<p>Requirements can be connected with each other by <i>traces</i> with different <i>relation types</i>.<br />
-<br />
-<img src="./pictures/MIRA.Requirements.TracesWithinRequirements.png" /><br />
-<br />
-Relation types are:</p>
-
-<ul>
-	<li><i>Conflicted</i>: a conflict between requirements was detected, which has to be analyzed further</li>
-	<li><i>Contradicting</i>: requirements are irresolvable contradicting each other</li>
-	<li><i>Override</i>: the <i>source</i> requirement(s) is/are overridden by the <i>target</i> requirement(s)</li>
-</ul>
-
-<p>Differentiation of relation type in static relation types and process-dependent relation types:</p>
-
-<ul>
-	<li>static relation types are conserved after the refining process</li>
-	<li>process-dependent relation types like <i>is conflicted with</i> have to be removed during the refining process</li>
-</ul>
-
-<p>Static relation types:</p>
-
-<ul>
-	<li><i>is contradicting to</i></li>
-	<li><i>is overridden by</i> - <i>overrides</i></li>
-</ul>
-
-<p>Process-dependent relation types:</p>
-
-<ul>
-	<li><i>is conflicted with</i></li>
-</ul>
-
-<p><img src="./pictures/MIRA.RequirementTypes.png" /><br />
-<br />
-Assign the source and target requirements by clicking the assign button.<br />
-A dialog will be opened where you can place the source and target requirements by dragging and dropping the requirements in the leftmost column. The middle column contains all referred source requirements while the rightmost column comprises all target requirements. Requirements can be removed by double-clicking.<br />
-<br />
-<img src="./pictures/MIRA.AssignRequirements.png" /><br />
-
-<h4><font color="#336699">Traces to component architectures</font></h4>
-
-<p>Traces to a component document the realization of requirements in the component architecture. To set a trace to a component, press the <i>Add</i> button to create a new trace. To add a component, press the <img src="./pictures/MIRA.Requirements.ComponentButton.png" /> button. To delete a trace, select the row by clicking on the left side of the column. Then press the <i>Remove</i> button.<br />
-<br />
-<img src="./pictures/MIRA.Requirements.TracesToArchitecture.png" /><br />
-
-<h3><font color="#336699">Section Safety</font></h3>
-
-<p>In this section you can specify the safety properties of the requirement.<br />
-<br />
-<img src="./pictures/MIRA.Requirements.Safety.png" /><br />
-<br />
-Whenever the <i>Safety Relevance</i> of a trace link from the requirement to a component is set to <i>yes</i>, the SIL-level is relevant for the linked component.</p>
-
-<h2><font color="#336699">Formal Specification</font></h2>
-
-<p>A requirement can be formalized to a partial formal model, a <i>Formal Specification</i>. To create a formal specification open the context menu of the requirement and select <i>Formal Specification</i>.<br />
-<br />
-<img src="./pictures/MIRA.NewFormalSpecification.png" /><br />
-<br />
-Within a formal specification different kind of models like component architectures, state machines, etc. can be used. For more information see <i>Modeling and simulation</i>. Formal specifications can be used as input for the generation of test cases, see <a href="model_testing.html">Model-based Testing</a>.<br />
-<br />
-<img src="./pictures/MIRA.FormalSpecification.png" /><br />
-&nbsp;</p>
-
-<h2><font color="#336699">Requirement Hierarchy</font></h2>
-
-<p>The button <i>Show Requirement Hierarchy</i> opens a view, where all relations of the current requirement are shown, divided by relation types. Double-clicking on the requirements in the hierarchy opens the corresponding requirement in the editor.<br />
-<br />
-<img src="./pictures/MIRA.ShowRequirementHierarchy.png" /></p>
-
-<h2><font color="#336699">Review Requirements</font></h2>
-
-<p>MIRA offers support for an automatic review of the requirements. Furthermore, it also offers the possibility to save the results of manual review.<br />
-&nbsp;</p>
-
-<h3>Automatic requirements review</h3>
-
-<p>The button <i>Review Requirements</i> syntactically checks the structure of the textual requirements and its relations with predefined automatic checks. Requirements, that do not pass one of these checks, are marked with a decoration and details on the results are shown in the warning list of the <i>Model Markers</i>.<br />
-<br />
-<img src="./pictures/MIRA.Verification.png" /><br />
-<br />
-<br />
-<br />
-This list gives an overview over the automatic checks for the distinct requirements types (A: all requirements types, I: only interface behaviour requirements):<br />
-&nbsp;</p>
-
-<table border="1">
-	<thead>
-		<tr>
-			<th>Req. type</th>
-			<th>Quality factor</th>
-			<th>Quality indicator</th>
-			<th>Check ID</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>A</td>
-			<td>Completeness</td>
-			<td>Existance of title and description</td>
-			<td>E1.4</td>
-		</tr>
-		<tr>
-			<td>A</td>
-			<td>Completeness</td>
-			<td>Existance of a complete description, TODO has to be empty</td>
-			<td>E1.5</td>
-		</tr>
-		<tr>
-			<td>A</td>
-			<td>Nonredundancy</td>
-			<td>Nonredundancy of title or description</td>
-			<td>E2.1</td>
-		</tr>
-		<tr>
-			<td>A</td>
-			<td>Traceability</td>
-			<td>Requirement status at least analyzed</td>
-			<td>E7.2</td>
-		</tr>
-		<tr>
-			<td>A</td>
-			<td>Prioritization</td>
-			<td>Requirement prioritized</td>
-			<td>E8</td>
-		</tr>
-		<tr>
-			<td>A</td>
-			<td>Consistency</td>
-			<td>Requirements not conflicted</td>
-			<td>E9.1</td>
-		</tr>
-		<tr>
-			<td>I</td>
-			<td>Implementation</td>
-			<td>Requirement connected to component in the component architecture</td>
-			<td>E11</td>
-		</tr>
-	</tbody>
-</table>
-
-<p>&nbsp;</p>
-
-<p><br />
-Additionally, automatic checks on the traces between requirements and from requirements to architecture are performed (A: all trace types, D: only directed relations, U: only undirected relations, E: only traces to component architectures):</p>
-
-<p>&nbsp;</p>
-
-<table border="1">
-	<thead>
-		<tr>
-			<th>Trace type</th>
-			<th>Quality factor</th>
-			<th>Quality indicator</th>
-			<th>Check ID</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>A</td>
-			<td>Completeness</td>
-			<td>Existance of author.</td>
-			<td>E1.4</td>
-		</tr>
-		<tr>
-			<td>U,D</td>
-			<td>Completeness</td>
-			<td>Existance of trace type.</td>
-			<td>E1.4</td>
-		</tr>
-		<tr>
-			<td>U</td>
-			<td>Completeness</td>
-			<td>Existance of at least two target requirements in the trace.</td>
-			<td>E1.5</td>
-		</tr>
-		<tr>
-			<td>D</td>
-			<td>Completeness</td>
-			<td>Existance of at least one source and at least one target requirement in the trace.</td>
-			<td>E1.5</td>
-		</tr>
-		<tr>
-			<td>E</td>
-			<td>Completeness</td>
-			<td>Existance of a target component in the trace.</td>
-			<td>E1.5</td>
-		</tr>
-		<tr>
-			<td>A</td>
-			<td>Nonredundancy</td>
-			<td>No duplicated traces.</td>
-			<td>E2.2</td>
-		</tr>
-		<tr>
-			<td>A</td>
-			<td>Traceability</td>
-			<td>Trace status is analyzed.</td>
-			<td>E7.2</td>
-		</tr>
-		<tr>
-			<td>A</td>
-			<td>Consistency</td>
-			<td>No cyclic dependencies between directed traces.</td>
-			<td>E2.1</td>
-		</tr>
-	</tbody>
-</table>
-
-<p>&nbsp;</p>
-
-<h3><font color="#336699">Support for manual reviews</font></h3>
-
-<p><a id="check" name="check"></a>During the creation of each requirement automatically a list of checks for the manual review is created in a second tab called <i>Checklist</i>. The list is extracted from a XML-template, which can be modified. At the moment, this XML-template is contained in the source-folder of MIRA.<br />
-<br />
-<img src="./pictures/MIRA.Checklist.png" /></p>
-
-<p>&nbsp;</p>
-
-<p>&nbsp;</p>
-
-<p>&nbsp;</p>
-
-<p>&nbsp;</p>
-
-<p>&nbsp;</p>
 </body>
 </html>

org.fortiss.af3.rcp.help/html/MIRA.requirements_analysis.html

@@ -28,40 +28,13 @@ In the same way, you can add more requirements analysis nodes to your project.
 
 By double-clicking on the <i>Requirements Analysis</i> node, an overview over all requirements opens.
 
-<br><br>
-<img src="./pictures/MIRA.StatisticsOverview.png">
-<br><br>
-
-The number of all artifacts is summed up in the statistics section.
-
 <br><br>
 <img src="./pictures/MIRA.RequirementsOverview.png">
 <br><br>
 
 The list of requirements can be sorted by clicking on the column headers of the overview list. 
 
-You can filter the requirements by inserting filter text in the filter section. Double-clicking on a column opens the corresponding requirement.
-
-<br><br>
-
-Below the requirements overview is an overview of all requirement trace that can also be filtered and sorted.
-
-<br><br>
-<img src="./pictures/MIRA.RequirementsTraces.png">
-
-
-<h2><font color="#336699">Export Report</font></h2>
-
-You can export the information contained in the <i>Requirements Analysis</i> as Html or Word-documents.</li> 
-
-<br><br>
-Click right on the <i>Requirements Analysis</i> node. This opens the context menu, where you select <i>Export Report</i>.
-This opens a dialog where the information can be saved as a html- or doc-files (note that the generation of doc-files is supported on Windows, only).
-
-<br><br>
-<img src="./pictures/MIRA.ExportReport.png">
-<br><br>
-
+You can filter the requirements by inserting filter text in the filter section. Double-clicking on a requirement opens the corresponding requirement.
 
 </body>
 </html>
\ No newline at end of file

org.fortiss.af3.rcp.help/html/MIRA.requirements_analysis2.html

-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<!--
- Documentation of MIRA - Model-based Integrated Requirements Analysis.
- 
- @author becker
- @ConQAT.Rating YELLOW Hash: 26C75A61229717DC7D05E53111B31834
--->
-
-<html>
-<head>
-	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-	<title>MIRA - Creating a Requirements Analysis using AutoFOCUS3 (AF3)</title>
-</head>
-<body>
-
-<h1><u><font color="#336699">MIRA - Model-based Integrated Requirements Analysis</font></u></h1>
-
-<h2><font color="#336699">Create a Requirements Analysis Node</font></h2>
-
-To create a new <i>Requirements Analysis Node</i> in project, open the context menu of the project by right-clicking on the project and select <i>Requirements Analysis</i>.
-
-<br><br>
-<img src="./pictures/MIRA.NewAnalysis.png">
-<br><br>
-
-In the same way, you can add more requirements analysis nodes to your project.
-
-<h2><font color="#336699">Requirements overview</font></h2> 
-
-By double-clicking on the <i>Requirements Analysis</i> node, an overview over all requirements opens.
-
-<br><br>
-<img src="./pictures/MIRA.StatisticsOverview.png">
-<br><br>
-
-The number of all artifacts is summed up in the statistics section.
-
-<br><br>
-<img src="./pictures/MIRA.RequirementsOverview.png">
-<br><br>
-
-The list of requirements can be sorted by clicking on the column headers of the overview list. 
-
-You can filter the requirements by inserting filter text in the filter section. Double-clicking on a column opens the corresponding requirement.
-
-<br><br>
-
-Below the requirements overview is an overview of all requirement trace that can also be filtered and sorted.
-
-<br><br>
-<img src="./pictures/MIRA.RequirementsTraces.png">
-
-
-<h2><font color="#336699">Export Report</font></h2>
-
-You can export the information contained in the <i>Requirements Analysis</i> as Html or Word-documents.</li> 
-
-<br><br>
-Click right on the <i>Requirements Analysis</i> node. This opens the context menu, where you select <i>Export Report</i>.
-This opens a dialog where the information can be saved as a html- or doc-files (note that the generation of doc-files is supported on Windows, only).
-
-<br><br>
-<img src="./pictures/MIRA.ExportReport.png">
-<br><br>
-
-
-</body>
-</html>
\ No newline at end of file

org.fortiss.af3.rcp.help/html/getting_started.html

@@ -75,6 +75,7 @@ Getting started help page.
 												<a href="MIRA.requirements_analysis.html">Requirements Analysis</a><br />
 												<a href="MIRA.requirements.html">Requirements</a><br />
 												<a href="MIRA.glossary.html">Glossary</a><br />
+												</p>
 
 												<p style="margin-left: 320px;">&nbsp;</p>
 												</td>