Commit 399b8dd2 authored by Simon Barner's avatar Simon Barner
Browse files

GREEN (with minor cleanup)

Issue-Ref: 3753
Issue-Url: #3753

Signed-off-by: Simon Barner's avatarSimon Barner <barner@fortiss.org>
parent d06ef8f4
Pipeline #33664 passed with stage
documentation.html 308baf89cb44b7f4c1b8f03a69fcb62bebe2b478 RED
documentation.html 7dd45a152071aaefcfa192955f2b563ba53e5b6c GREEN
......@@ -9,16 +9,9 @@ These relationships are created between entry and exit connectors.
References to argument elements in different modules are possible via away elements.
</p>
<h2>Package description</h2>
<ul>
<li><tt>safetycases.constraint</tt>: constraint-checkers.</li>
<li><tt>safetycases.library</tt>: classes for dealing with the library of safety cases.</li>
<li><tt>safetycases.library.prototypes</tt>: prototypes for the library of safety cases.</li>
<li><tt>safetycases.utils</tt>: utility functions for safety cases.</li>
</ul>
<h2>Metamodel description</h2>
The <i>safety cases metamodel</i> contains the following classes and interfaces:
<ul>
<li><tt>Goal</tt>: the class for the Goal argument element.</li>
<li><tt>Solution</tt>: the class for the Solution argument element.</li>
<li><tt>Strategy</tt>: the class for the Strategy argument element.</li>
......@@ -29,7 +22,6 @@ The <i>safety cases metamodel</i> contains the following classes and interfaces:
<li><tt>SafetyCasesConnector</tt>: the father class for the two type of connectors in safety cases.</li>
<li><tt>EntryConnector</tt>: the class for the entry connector.</li>
<li><tt>ExitConnector</tt>: the class for the exit connector.</li>
<ul>
</ul>
</body></html>
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