Commit 1114b9c3 authored by Sebastian Bergemann's avatar Sebastian Bergemann
Browse files

Moved developer info from user docu into developer docu

Issue-Ref: 4204
Issue-URL: af3#4204

Signed-off-by: Sebastian Bergemann's avatarSebastian Bergemann <>
parent f1aa1d6e
Pipeline #34229 failed with stage
documentation.html c61291c1f8f77b6a418ba24cd29c2cfa7f661696 GREEN
documentation.html 99fa035c6b4de639d7ca4cd73380a02d3e364e80 YELLOW
......@@ -15,11 +15,24 @@
<p>This plugin contains the basic functionality of reuse in AF3 projects.
With it a user can create reuse libraries that are stored in a separate local project.
These libraries can store supported reuse elements (which are standard AF3 elements to
which a reuse specification is added). The stored reuse elements are displayed in the model
which a reuse specification is added; see below). The stored reuse elements are displayed in the model
elements view and can be drag & dropped from there in AF3 projects. They are still linked
with their libraries, which is why the elements can be updated at any time from the library
and vice versa (update the original element inside the library). Currently supported AF3
elements for reuse are: components, requirements and entries of data dictionaries.</p>
elements for reuse are: components, tasks, requirements and entries of data dictionaries (functions, structures, enumerations).</p>
<p>If an AF3 element supports reuse libraries, it can get a reuse specification (not directly visible in AF3).
As soon as it has at least one reuse specification, the AF3 element is now a reuse element. It looks still
like the usual AF3 element and can also be used like before, but it has now at least one reference to a reuse
library via this reuse specification (or several reuse libraries if it has several reuse specifications).
If an AF3 element has a reuse specification, it means that an identical AF3 element ("deep copy") exists now
in this referenced reuse library. It is now possible to reuse this AF3 element 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
(and exchange updates). </p>
<p>Through the UUIDs and the reuse specifications it is ensured that you can only propagate modifications
between (reuse) elements that are connected due to their (reuse) origin. </p>
<h1><font size="5" style="font-size: 20pt">Package description</font></h1>
<p>The plugin contains the following packages (besides standard ones):
Supports Markdown
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