diff --git a/org.fortiss.af3.rcp.help/html/getting_started.html b/org.fortiss.af3.rcp.help/html/getting_started.html index 0f3d062b421c7ec462fe6a0f03670a8036e6e297..17dd05a880b2c571063427929b65df37aaeaeffd 100644 --- a/org.fortiss.af3.rcp.help/html/getting_started.html +++ b/org.fortiss.af3.rcp.help/html/getting_started.html @@ -164,6 +164,40 @@ + +
+
+ +
+
+ diff --git a/org.fortiss.af3.rcp.help/html/reuse/.ratings b/org.fortiss.af3.rcp.help/html/reuse/.ratings new file mode 100644 index 0000000000000000000000000000000000000000..e60b19183be68ad2513acd69e2baf14c81a23328 --- /dev/null +++ b/org.fortiss.af3.rcp.help/html/reuse/.ratings @@ -0,0 +1,9 @@ +feature-model.html be3ae7703dd88249e1913160bcebe940c51095c3 RED +presence-conditions.html f0a242ca40a6ba39e60d844c82dbf38dcac8c99f RED +reuse+variability.MainPage.html 11995af223712c783510b02c78f3b5fe783b3d7c GREEN +reuse-elements.html 906957fb0f9249e8ec90e6fe5241b7d8a771ca25 GREEN +reuse-functionality.html ddf18a3d4752fe9dedcd49a1c40839e57b7c6fca GREEN +reuse-intro.html 5ae5c2de8f6fa9eae5c685b7e0342cb2429eb415 GREEN +reuse-library.html 23794d81cdd34881c4b229513a44865ca71d4170 GREEN +variability-modeling.html 90a9dd2c8d460f41a75908fd02f641e9f45a7f86 RED +variant-generation.html a784e06a99c0e1a02a6baedf5cb7dabf9857c53c RED diff --git a/org.fortiss.af3.rcp.help/html/reuse/feature-model.html b/org.fortiss.af3.rcp.help/html/reuse/feature-model.html new file mode 100644 index 0000000000000000000000000000000000000000..be3ae7703dd88249e1913160bcebe940c51095c3 --- /dev/null +++ b/org.fortiss.af3.rcp.help/html/reuse/feature-model.html @@ -0,0 +1,48 @@ + + + + + + + + + + + + + Feature Model + + + +
+
+ +
+
+
+ + + + +

Feature Models

+ + +
+ + + + + + \ No newline at end of file diff --git a/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_createAlternative.PNG b/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_createAlternative.PNG new file mode 100644 index 0000000000000000000000000000000000000000..4aaa7c703383aa948c6774e6712eefef6a599a3b Binary files /dev/null and b/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_createAlternative.PNG differ diff --git a/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_createConstraint.PNG b/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_createConstraint.PNG new file mode 100644 index 0000000000000000000000000000000000000000..2047484dd4c63d08d5664f746ada8d3574f38eaa Binary files /dev/null and b/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_createConstraint.PNG differ diff --git a/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_createFeature.PNG b/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_createFeature.PNG new file mode 100644 index 0000000000000000000000000000000000000000..d1959f3111f3fcd19502dae388641d5a03e52e00 Binary files /dev/null and b/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_createFeature.PNG differ diff --git a/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_createModel.png b/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_createModel.png new file mode 100644 index 0000000000000000000000000000000000000000..0c2f914f87a505b52017d2e9f6ae6023313b3a75 Binary files /dev/null and b/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_createModel.png differ diff --git a/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_editConstraint.PNG b/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_editConstraint.PNG new file mode 100644 index 0000000000000000000000000000000000000000..18cb3142ff247825cbcdb6d837b91b663f85eefc Binary files /dev/null and b/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_editConstraint.PNG differ diff --git a/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_optional.PNG b/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_optional.PNG new file mode 100644 index 0000000000000000000000000000000000000000..ae01c80212fefce277287e2b941e7612fe6273a4 Binary files /dev/null and b/org.fortiss.af3.rcp.help/html/reuse/pictures/fm_optional.PNG differ diff --git a/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_add_to_lib_complete.PNG b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_add_to_lib_complete.PNG new file mode 100644 index 0000000000000000000000000000000000000000..0976d3ebba76b35e8b58eb007ad8ef4e84a90a2c Binary files /dev/null and b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_add_to_lib_complete.PNG differ diff --git a/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_concept.PNG b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_concept.PNG new file mode 100644 index 0000000000000000000000000000000000000000..70b6ecfd14709c7697f240e73f1ecf72f426c02c Binary files /dev/null and b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_concept.PNG differ diff --git a/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_context_menu.PNG b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_context_menu.PNG new file mode 100644 index 0000000000000000000000000000000000000000..27ce024160ad7cdb8e860de8aa7aa0efe9934a6f Binary files /dev/null and b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_context_menu.PNG differ diff --git a/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_create_lib_complete.PNG b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_create_lib_complete.PNG new file mode 100644 index 0000000000000000000000000000000000000000..5acae2ea99c651d39236ebd02878cb77daf60784 Binary files /dev/null and b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_create_lib_complete.PNG differ diff --git a/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_drag_n_drop_complete.PNG b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_drag_n_drop_complete.PNG new file mode 100644 index 0000000000000000000000000000000000000000..44514d17a96e4d2ba0c4274c9056d31038ffbdba Binary files /dev/null and b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_drag_n_drop_complete.PNG differ diff --git a/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_libraries_in_views.PNG b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_libraries_in_views.PNG new file mode 100644 index 0000000000000000000000000000000000000000..72598ce9ccb670d110470c6e2a702f5b2f327708 Binary files /dev/null and b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_libraries_in_views.PNG differ diff --git a/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_manage_complete.PNG b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_manage_complete.PNG new file mode 100644 index 0000000000000000000000000000000000000000..55989bdb56b1a08fa210c23d01eb8e26949e6a2a Binary files /dev/null and b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_manage_complete.PNG differ diff --git a/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_update_from_lib_complete.PNG b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_update_from_lib_complete.PNG new file mode 100644 index 0000000000000000000000000000000000000000..63123a5627e8a71a0983eecccd3533d6f8c8ce23 Binary files /dev/null and b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_update_from_lib_complete.PNG differ diff --git a/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_update_in_lib_complete.PNG b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_update_in_lib_complete.PNG new file mode 100644 index 0000000000000000000000000000000000000000..6f8317041f8ee4c5bb71e602ee5ed1ef87750aa6 Binary files /dev/null and b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_update_in_lib_complete.PNG differ diff --git a/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_view.PNG b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_view.PNG new file mode 100644 index 0000000000000000000000000000000000000000..cc9ed9ac5c027b56aabb258c23cd2ffc366e847b Binary files /dev/null and b/org.fortiss.af3.rcp.help/html/reuse/pictures/reuse_view.PNG differ diff --git a/org.fortiss.af3.rcp.help/html/reuse/pictures/workspace_structure.PNG b/org.fortiss.af3.rcp.help/html/reuse/pictures/workspace_structure.PNG new file mode 100644 index 0000000000000000000000000000000000000000..c597b4bea8453286d0f107e7a4d6781ba183ac14 Binary files /dev/null and b/org.fortiss.af3.rcp.help/html/reuse/pictures/workspace_structure.PNG differ diff --git a/org.fortiss.af3.rcp.help/html/reuse/presence-conditions.html b/org.fortiss.af3.rcp.help/html/reuse/presence-conditions.html new file mode 100644 index 0000000000000000000000000000000000000000..f0a242ca40a6ba39e60d844c82dbf38dcac8c99f --- /dev/null +++ b/org.fortiss.af3.rcp.help/html/reuse/presence-conditions.html @@ -0,0 +1,48 @@ + + + + + + + + + + + + + Presence Conditions + + + +
+
+ +
+
+
+ + + + +

Presence Conditions

+ + +
+ + + + + + \ No newline at end of file diff --git a/org.fortiss.af3.rcp.help/html/reuse/reuse+variability.MainPage.html b/org.fortiss.af3.rcp.help/html/reuse/reuse+variability.MainPage.html new file mode 100644 index 0000000000000000000000000000000000000000..11995af223712c783510b02c78f3b5fe783b3d7c --- /dev/null +++ b/org.fortiss.af3.rcp.help/html/reuse/reuse+variability.MainPage.html @@ -0,0 +1,87 @@ + + + + + + + + + + + + Reuse and Variability + + + + +
+
+ +
+
+
+ + + +
+ +
+
+ + + + + + + + + + \ No newline at end of file diff --git a/org.fortiss.af3.rcp.help/html/reuse/reuse-elements.html b/org.fortiss.af3.rcp.help/html/reuse/reuse-elements.html new file mode 100644 index 0000000000000000000000000000000000000000..906957fb0f9249e8ec90e6fe5241b7d8a771ca25 --- /dev/null +++ b/org.fortiss.af3.rcp.help/html/reuse/reuse-elements.html @@ -0,0 +1,64 @@ + + + + + + + + + + + + + Reuse Elements + + + +
+
+ +
+
+
+ + + + +

Reuse Elements

+ There does not exist a specific reuse element type but rather it is possible to enable the reuse possibility for almost every element in AF3. +

+ Currently, the following AF3 elements are supported in reuse libraries: + + If you think an AF3 element is missing for reuse, please contact the AF3 developer team. +

+ + If one of the AF3 elements above is added to a reuse library, it is now possible to reuse it from the reuse library and insert it again in the same project but also in other projects of the same workspace or even of other workspaces (see here). + In addition, it is possible that you (or another AF3 user who got the referenced reuse library from you) modify the reused element in another project/environment and update the connected reuse element inside the referenced reuse library with this modification (see here). + If the updated reuse library is then brought back to your workspace (or was already there all the time), you have the possibility to propagate the modification of the somewhere else reused element to your original AF3 element by updating this reuse element via the modified reuse library (see here). +

+
+ + + + + + \ No newline at end of file diff --git a/org.fortiss.af3.rcp.help/html/reuse/reuse-functionality.html b/org.fortiss.af3.rcp.help/html/reuse/reuse-functionality.html new file mode 100644 index 0000000000000000000000000000000000000000..ddf18a3d4752fe9dedcd49a1c40839e57b7c6fca --- /dev/null +++ b/org.fortiss.af3.rcp.help/html/reuse/reuse-functionality.html @@ -0,0 +1,184 @@ + + + + + + + + + + + + + Reuse Functionality + + + +
+
+ +
+
+
+ + + + +

Reuse Functionality

+ Content of this page: + + + +

Creating a reuse library

+ It is not needed to create a new reuse library without any content. + This is why the possibility to create a new reuse library exists only during the dialog for adding a reuse element to a library. + +

+ In the first dialog window of adding a reuse element to a library, you can push at the bottom the button "Create new library". + The name of the reuse library needs to be chosen in the next window. it is not possible to choose a name which is already taken by another reuse library in the same workspace. + +

+ + +

+ Afterwards, the process of adding a reuse element to a library will be continued, but the target reuse library will now be the newly created one. + Attention: If the process of adding a reuse element to a library is not successfully finished, the creation of the new reuse library will not be successful, too. + +

+ If, for whatever reason, you want to have an empty reuse library, you can create a reuse library with a dummy reuse element and then delete the dummy element via the reuse view. + + + + + +

Adding an element to a reuse library

+ If you have a possible reuse element and want to store it in a reuse library, you just need to start and follow the following dialog wizard. + If the wanted reuse library does not exist yet, you can create it during the adding process (see here). + +

+ Right click on the possible reuse element in the model navigator to open the standard element context menu. + In this menu you can find the entry "Add to Reuse Library". Select it and follow the upcoming dialog. + You will first need to specify the target library (or create a new one). + Afterwards, you will need to choose the name with which the element should be stored in the library. You cannot choose names of already existing reuse elements in the same library. + If your element contains external references, an additional dialog window will appear and help you managing these references for the reuse. + +

+ + +

+ Finally, a deep copy of your element will be stored in the selected library and the original element should have a reference to it. + You can check that by looking into the model elements view or the reuse view and see if the new element appears there in the correct library. Maybe you need to refresh the views first. + To check the reuse reference/specification of the original element, you can open again the context menu of this element in the model navigator and control if it has new entries for updating its referenced library element and updating itself via the library element. + + + + + +

Reusing an element from a reuse library

+ As soon as you have saved a reuse element in a reuse library (or received a library with reuse elements from other developers), you can reuse it everywhere as long as its type fits to the target place (e.g. a component can be reused in a component architecture but not in a requirement list). + In order to reuse the element, you just select it in the model elements view (usually in the right side). With a drag and drop you can then place it where you want it in the same way as for any standard model elements. + However, in contrast to the standard elements, the placed element will have already all the content of the original element that was reused, and it will have a reuse reference/specification to its origin in the reuse library. + Through this reference, it is now always possible to get all updates/modifications of the original reuse element and also to update the origin yourself. + +

+ + +

+ If the wanted element for reuse is not shown in the model elements view, it is either not correctly added to a reuse library that is present in the current workspace, or it does not fit to the current active editor. + If you for example have the component editor open, you can only see all possible reuse components but no reuse entries for the data dictionary. + If you open the data dictionary editor, you will not see anymore the reusable components but now the reusable data dictionary entries are visible in the model elements view. + + + + +

Updating an element inside a reuse library

+ If a possible reuse element was copied/added into a reuse library or if it is a reuse element that was reused out of a library, it has always a reference to its counterpart in the reuse library. + Via this reference, it is now possible to update the counterpart inside the reuse library with the current (probably updated) version of the reuse element in the project. + +

+ This can be done by right-clicking on the respective element in the model navigator and choosing the "Update In Reuse Library" entry in the opened context menu. A dialog wizard will open up and guide you through the update. +
+ If the element has multiple references to libraries, the first request will be about the target library. Afterwards, an overview is given about what will be updated with what and where. When this was confirmed, an option to change the name of the element in the library will open and finally the update will be executed. + If your element contains external references, an additional dialog window will appear and help you managing these references for the reuse. If the reuse reference to the library is outdated and the reuse element cannot be found in the library, you will get this information, the update process will be cancelled and the wrong reference will be removed. + +

+ + +

+ Together with updating a reuse element inside a project via a library element it is now possible to quickly propagate new changes of an element to its reused twin elements via the reuse libraries. + + + + +

Updating a reused element via a reuse library

+ If a possible reuse element was copied/added into a reuse library or if it is a reuse element that was reused out of a library, it has always a reference to its counterpart in the reuse library. + Via this reference, it is now possible to update the reuse element in the project with the current (probably updated) version of its counterpart inside the reuse library. + +

+ This can be done by right-clicking on the respective element in the model navigator and choosing the "Update From Reuse Library" entry in the opened context menu. A dialog wizard will open up and guide you through the update. +
+ If the element has multiple references to libraries, the first request will be about the target library (which is then actually the source of the update). Afterwards, an overview is given about what will be updated with what and where. When this was confirmed, an option to change the name of the reused element in the project will open and finally the update will be executed. + If your element contains external references, an additional dialog window will appear and help you managing these references for the reuse. If the reuse reference to the library is outdated and the reuse element cannot be found in the library, you will get this information, the update process will be cancelled and the wrong reference will be removed. + +

+ + +

+ Together with updating a referenced library element it is now possible to quickly propagate new changes of an element to its reused twin elements via the reuse libraries. + + + + +

Managing the reuse libraries and their element

+ To be able to easily manage the reuse libraries and elements, we have implemented a dedicated view/editor for the reuse feature. + As it is shown in the pictures in the section about reuse libraries and below, this editor is a table containing (in separate rows) all found reuse libraries in the current workspace. The library rows can be unfolded and will then also present the contained reuse elements in sub-rows. + +

+ The editor should be instantiated automatically when starting the AF3 environment. It is located by default in the bottom panel as a separate tab called "Reuse Libraries". + If it is not there, you can open it by searching for "Reuse" with Ctrl+3 and selecting the "Reuse Libraries" in the view category. However, the editor should be opened and actively displayed every time when a reuse action is executed (independent of being already existent or not). +
+ Besides showing the names of the reuse libraries and their reuse elements, the table also provides information about the related UUIDs, comments and when the related objects were updated the last time. + +

+ With the help of the editor, it is possible to rename or delete single reuse elements or whole reuse libraries by right-clicking on the respective names and choosing the wanted action from the context menu. + The comments can be modified by directly double-clicking into the comment cell of the wanted object. + +

+ + +

+ If a reuse library was updated externally or added as folder into the workspace during runtime, it will not be shown automatically in the editor. + To achieve this, the button "Refresh Libraries" needs to be pushed in the top left corner of the editor. The time of the last refresh is shown on the right side of the button. + +

+ Finally, it is possible to search for text in all the cells of the editor via the search box in the top left corner of the editor. + With this help you can for example find libraries and reuse elements updated on a specific date or find all reusable controller components across all libraries (if you added all of them with "controller" in their name). + + + +
+ + + + + + \ No newline at end of file diff --git a/org.fortiss.af3.rcp.help/html/reuse/reuse-intro.html b/org.fortiss.af3.rcp.help/html/reuse/reuse-intro.html new file mode 100644 index 0000000000000000000000000000000000000000..5ae5c2de8f6fa9eae5c685b7e0342cb2429eb415 --- /dev/null +++ b/org.fortiss.af3.rcp.help/html/reuse/reuse-intro.html @@ -0,0 +1,54 @@ + + + + + + + + + + + + + Reuse Introduction + + + +
+
+ +
+
+
+ + + + +

Reuse Introduction

+ During software development it is very useful/efficient if you can reuse already existing code/artifacts. To enable this also for AutoFOCUS3 (AF3), we have implemented the concept of reuse libraries.

+ An overview over reuse libraries is given here and the contained reuse elements are explained here. + How to use the reuse functionality is shown here. All these actions can easily be accessed via a drag&drop panel and by a context menu. + A separate reuse view exist for a simple management of reuse libraries and their reuse elements.

+ All of this makes it easier, faster and safer to move AF3 elements from one project to another one (also on different devices) or to reuse recurring model parts in all projects.

+ + + +
+ + + + + + \ No newline at end of file diff --git a/org.fortiss.af3.rcp.help/html/reuse/reuse-library.html b/org.fortiss.af3.rcp.help/html/reuse/reuse-library.html new file mode 100644 index 0000000000000000000000000000000000000000..23794d81cdd34881c4b229513a44865ca71d4170 --- /dev/null +++ b/org.fortiss.af3.rcp.help/html/reuse/reuse-library.html @@ -0,0 +1,71 @@ + + + + + + + + + + + + + Reuse Library + + + +
+
+ +
+
+
+ + + + +

Reuse Library

+ A reuse library is an own structure and serves as container for reuse elements. It can be seen as storage of model elements that might get reused in the future. +

+ + Multiple reuse libraries can exist in an AF3 environment. Although we are using UUIDs to differentiate between them, we suggest to always have different names for the libraries and hence we are preventing name duplicates as far as we can. +

+ + The following example shows several reuse libraries represented inside the reuse view as containers for reuse elements: + +

+ + The reuse libraries from above with their reuse elements is also available for drag&drop from the model elements view: + +

+ + Reuse libraries are independent of AF3 projects and can be accessed by all AF3 projects that are in the same workspace as the reuse libraries. This is why you have a separate directory for the libraries besides the AF3 projects. + As it can be seen in the figure below, an AF3 workspace contains a AF3-Project-Directory with all your AF3 models/projects and a AF3-Reuse-Directory with all the reuse libraries. If you have not used reuse libraries before, you might need to create first one reuse library to be able to see this reuse directory. +

+ + +

+ + Inside this reuse directory, each reuse library has its own folder (with its name and UUID as folder name). This makes it easy to move complete reuse libraries from one AF3 workspace to another one (also on different devices). + Inside a reuse library folder, we have placed the whole content of the library with all of its AF3 elements as one AF3 file with the file ending .af3_lib. + This af3_lib file is based on the XML format (like the standard af3 model file), what makes manual changes possible. However, we recommend to only change the reuse libraries and its elements from within AF3 (see reuse functionality). + +
+ + + + + + \ No newline at end of file diff --git a/org.fortiss.af3.rcp.help/html/reuse/variability-modeling.html b/org.fortiss.af3.rcp.help/html/reuse/variability-modeling.html new file mode 100644 index 0000000000000000000000000000000000000000..90a9dd2c8d460f41a75908fd02f641e9f45a7f86 --- /dev/null +++ b/org.fortiss.af3.rcp.help/html/reuse/variability-modeling.html @@ -0,0 +1,61 @@ + + + + + + + + + + + + + Variability Modeling + + + +
+
+ +
+
+
+ + + + +

Variability Modeling and Product-Line Engineering

+ AutoFOCUS3 is capable of modeling variability across viewpoints to support product-line engineering and planed reuse. The implemented tooling concept follows a classical 150% approach with feature modeling. + Hereby, the features<\i> (or configuration options) which shall be different between the system variants can be modeled in one central feature model. + The optional or alternative model elements in all viewpoints can then be linked to these features via a so called presence conditions. + Finally, system variants can be automatically generated by AutoFOCUS3 after selecting/deselecting features for a variant. + +

+ Help on these aspects of variability management in AutoFOCUS3 can be found here: +

+

+

+

+
+ + + + + + \ No newline at end of file diff --git a/org.fortiss.af3.rcp.help/html/reuse/variant-generation.html b/org.fortiss.af3.rcp.help/html/reuse/variant-generation.html new file mode 100644 index 0000000000000000000000000000000000000000..a784e06a99c0e1a02a6baedf5cb7dabf9857c53c --- /dev/null +++ b/org.fortiss.af3.rcp.help/html/reuse/variant-generation.html @@ -0,0 +1,48 @@ + + + + + + + + + + + + + Feature Model + + + +
+
+ +
+
+
+ + + + +

Variant Generation

+ + +
+ + + + + + \ No newline at end of file diff --git a/org.fortiss.af3.rcp.help/html/templates/navBarContent.html b/org.fortiss.af3.rcp.help/html/templates/navBarContent.html index 528cf54cf2a92b3ce5749e2e83922fe7f8e61081..5a04bb4fa6b6a20121d1999e39e6e09c4af66cd9 100644 --- a/org.fortiss.af3.rcp.help/html/templates/navBarContent.html +++ b/org.fortiss.af3.rcp.help/html/templates/navBarContent.html @@ -96,6 +96,24 @@ Quantitative Assessment of Assurance Cases Assurance Case Maintenance + + +