From 7f136e0a1727c19607d8c11ed6c586a562fedf21 Mon Sep 17 00:00:00 2001 From: Johannes Eder <eder@fortiss.org> Date: Tue, 17 Mar 2020 17:42:21 +0100 Subject: [PATCH] Removed FOCUSer help Issue-Ref: 3938 Issue-Url: https://af3-developer.fortiss.org/issues/3938 Signed-off-by: Johannes Eder <eder@fortiss.org> --- .../html/getting_started.html | 11 - org.fortiss.af3.rcp.help/html/process.html | 38 - .../html/process_constraints.html | 791 ------------------ .../html/process_constraints_definition.html | 44 - .../html/process_definition.html | 37 - .../html/process_usage.html | 63 -- 6 files changed, 984 deletions(-) delete mode 100644 org.fortiss.af3.rcp.help/html/process.html delete mode 100644 org.fortiss.af3.rcp.help/html/process_constraints.html delete mode 100644 org.fortiss.af3.rcp.help/html/process_constraints_definition.html delete mode 100644 org.fortiss.af3.rcp.help/html/process_definition.html delete mode 100644 org.fortiss.af3.rcp.help/html/process_usage.html diff --git a/org.fortiss.af3.rcp.help/html/getting_started.html b/org.fortiss.af3.rcp.help/html/getting_started.html index 0a0a2f6..f2be2fc 100644 --- a/org.fortiss.af3.rcp.help/html/getting_started.html +++ b/org.fortiss.af3.rcp.help/html/getting_started.html @@ -161,22 +161,11 @@ Getting started help page. </td> </tr> <tr> - <td align="center" bgcolor="#c7d2dc" width="50%"> - <h2>FOCUSer - FOCUS procEss AwaReness</h2> - </td> <td align="center" bgcolor="#c7d2dc" width="50%"> <h2>Further Resources</h2> </td> </tr> <tr> - <td align="center" valign="top"><br /> - <a href="process.html"><img alt="" border="1" height="200" hspace="80" src="gettingStarted/img/FOCUSer.png" width="200"/></a><br/> - <br /> - <p style="margin-left: 50px;"><a href="process.html">Introduction</a><br/> - <a href="process_definition.html">Defining Processes</a><br/> - <a href="process_usage.html">Using Processes</a><br/> - <a href="process_constraints.html">Supported Constraints</a><br/></p> - </td> <td align="center" valign="top"><br /> <img alt="" border="1" hspace="80" src="gettingStarted/img/af3_logo.png" width="200" /><br /> <br /> diff --git a/org.fortiss.af3.rcp.help/html/process.html b/org.fortiss.af3.rcp.help/html/process.html deleted file mode 100644 index 85b2291..0000000 --- a/org.fortiss.af3.rcp.help/html/process.html +++ /dev/null @@ -1,38 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> - -<!-- - Documentation of FOCUSer - FOCUS procEss AwaReness. - - @author lucio - @ConQAT.Rating ---> - -<html> -<head> - <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> - <title>FOCUSer - Making an AutoFOCUS3 (AF3) Aware of Modelling Processes</title> -</head> -<body> - -<h1><u><font color="#336699">FOCUSer - FOCUS procEss AwaReness</font></u></h1> - -<h2><font color="#336699">1. Introduction</font></h2> - -FOCUSer is a system that allows guiding the modeler through a set of actions in order to build a model. It does so by highlighting problems in the model that are pertinent to the current state of development of the model and proposing new modeling objectives based on that same state.<br><br> - -The main concepts of the system are <b>constraint</b>, <b>objective</b> and <b>process</b>. <a href="process_constraints.html"><b>Constraints</b></a> are mechanisms that evaluate the state of the model against arbitrary properties and visually report errors or warnings to the IDE when those properties do not hold. An <b>objective</b> is composed of a set of <b>constraints</b>. In order to achieve an objective the modeler has to satisfy all constraints that objective entails. <a href="process_definition.html"><b>Processes</b></a> are composed of <b>objectives</b> that may depend on each other. In order to fulfill a process a modeler has to fulfill all of its objectives. Ideally, the modeler starts with objectives that have no dependencies and progressively fulfills objectives by following the dependency graph.<br><br> - -<img src="./pictures/FOCUSER_do-178c_with_constraints.png" style="max-height: 500px;"><br><br> - -In the image above we depict a process (on the left side of the picture) and a set of constraints used by that process (on the right side of the picture). Take for instance the objective "Requirement information is complete". In order to arrive to this objective the modeler will first have to fulfill its dependencies, in this case the "Requirements are defined" objective which implies satisfying the "All requirement packages have at least on requirement" constraint. Then, in order to fulfill the objective itself the fields "name", "ID", "rationale", "description" and "author" of all requirements have to be filled out, as stated by the objective's constraints. After this is done, and the "One aspect is defined for each requirement" objective is also fulfilled, the modeler can proceed to the "Requirements are approved by reviewer" objective.<br><br> - -Processes in FOCUSer are descriptive, rather than prescriptive. In practice this means that FOCUSer is non-invasive in the sense that it provides guidance to the user while giving him or her full freedom to select the next modeling actions. - -<h2><font color="#336699">2. <a href="process_usage.html">Making use of FOCUSer during model development</a></font></h2> - -<h2><font color="#336699">3. <a href="process_definition.html">Defining your own process</a></font></h2> - -<h2><font color="#336699">4. <a href="process_constraints.html">List of implemented constraints</a></font></h2> - -</body> -</html> \ No newline at end of file diff --git a/org.fortiss.af3.rcp.help/html/process_constraints.html b/org.fortiss.af3.rcp.help/html/process_constraints.html deleted file mode 100644 index 32fe5ca..0000000 --- a/org.fortiss.af3.rcp.help/html/process_constraints.html +++ /dev/null @@ -1,791 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> - -<!-- - Documentation of FOCUSer - FOCUS procEss AwaReness. - - @author lucio - @ConQAT.Rating ---> - -<html> -<head> - <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> - <title>FOCUSer - Making an AutoFOCUS3 (AF3) Aware of Modelling Processes</title> -</head> -<body> -<h2><font color="#336699">4. List of implemented constraints</font></h2> -This part of the documentation discusses the developed constraints that the user can manually activate in IDE for building the model development process (i.e., <a href="process_definition.html">Making use of FOCUSer during model development</a>). The implemented constraints reside in various packages of AF3. The following table provides the following information to the user of FOCUSer system, 1) the constraints that the user can manually activate (i.e., as shown to the User on IDE), 2) describes briefly the functionality of each of the constraint, 3) the location where the constraints reside in AF3 projects and 4) The ECore model element on which the constraint is applicable. - <br /> - <td valign="center"> - <table width="98%" align="center" cellpadding="0" cellspacing="0" border="0" bordercolor="#7290AA" style="border-style:solid; border-collapse:collapse; border-spacing:0"> - <tr> - <td valign="top"><table width="98%" align="center" cellpadding="0" cellspacing="0" border="1px" bordercolor="#7290AA" style="border-style:solid; border-collapse:collapse; border-spacing:0"> - <tr> - <td width="2%" align="center" bgcolor="#C7D2DC"><h2>Nr.</h2></td> - <td width="20%" align="center" bgcolor="#C7D2DC"><h2>Constraint to Manually Activate on IDE</h2></td> - <td width="30%" align="center" bgcolor="#C7D2DC"><h2>Description/Purpose</h2></td> - <td width="10%" align="center" bgcolor="#C7D2DC"><h2>Location (AF3 Package Name + Java Class)</h2></td> - <td width="10%" align="center" bgcolor="#C7D2DC"><h2>Applies to ECore Model Element</h2></td> - </tr> - - <tr> - </td> - <td align="left"> - <p style="margin-left:10px"> 1</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All requirements have an author"</p> - </td> - <td> - <p style="margin-left:10px"> The Author field of the requirement is not empty or null. </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.AuthorConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">2</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All requirements are reviewed as per the checklist"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Each element in the Checklist Tab of the requirement is set to "Approved" </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.CheckListReviewConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px"> 3</p> - </td> - - <td align="left"> - <p style="margin-left:10px"> "All component packages has at least one component"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The component package contains components. </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.ComponentExistsConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> ComponentArchitecture</p> - </td> - - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">4</p> - </td> - - <td align="left"> - <p style="margin-left:10px"> "All requirements should not have words \"and/or\" in their description"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The description of the requirement does not contain certain words "and/or" </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.DescriptionAndOrConstraint.java </p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">5</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All requirements have a description"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The description of the requirement is not empty or null. </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.DescriptionConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px"> 6</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All functional requirements should have at least one non-functional aspect defined"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> A functional requirement has at least one non-functional aspect. </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.FunctionalReqsHaveOneNonFunctionalReq.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px"> 7</p> - </td> - - <td align="left"> - <p style="margin-left:10px"> "All requirements having glossary terms that are fully defined"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> All of the glossary terms used in the description of the requirement are fully defined. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.GlossaryTermsDefinitionConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">8</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All requirements have an id"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The requirement has an id. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.IDConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - - - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">9</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All functional requirements should have \"input(s)/output(s)\" defined"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> A functional requirement has input/output defined. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.IdentifiedInputOutputDefinedConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - - - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">10</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All requirements should have only one aspect"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Each requirement has one or more aspects (either functional or non-functional) - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.MultipleAspectsConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">11</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All requirements have a name"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The requirement has a name. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.NameConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">12</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All non-functional requirements should have exactly one functional aspect defined"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> A non-functional requirement has exactly one non-functional aspect. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.NonFunctionalReqsHaveExactlyOneFunctionalReq.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">13</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "Only one requirement should define an safety level"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Only one requirement defines a safety integrity level. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.OnlyOneSILConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">14</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All requirements with parameters that have a type"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The parameterType of a constraint is non-empty and set to an appropriate type. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.ParameterTypeConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">15</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All requirements have a rationale"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The rationale of a requirement is non-empty. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.RationaleConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">17</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All requirement packages have at least one requirement"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The requirements package has at least one requirement. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.RequirementExistsConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> RequirementsContainer</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">18</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All components having traces to requirement are correct"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The component implementing the requirement is checked by the user if the trace to requirement exists and the check-box "Requirement Impl Correctly" is selected. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.RequirementImplementedCorrectlyConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">19</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All requirements have signals that are uniquely defined" </p> - </td> - <td align="left"> - <p style="margin-left:10px"> The signal has an unique name among all the signals defined. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.SignalConstraints.java (UniqueSignalNameConstraint)</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - - </tr> - <tr> - <td align="left"> - <p style="margin-left:10px">20</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All requirements with signals defined have a type" </p> - </td> - <td align="left"> - <p style="margin-left:10px"> The signal has a defined type (integer/boolean). - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.SignalConstraints.java (SignalTypeConstraint)</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - - </tr> - - - <tr> - <td align="left"> - <p style="margin-left:10px">21</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All requirements with signals should have initial value set and between ranges (i.e., [From,To]) for int data type and true/false for boolean data type" </p> - </td> - <td align="left"> - <p style="margin-left:10px"> The signal has a initial value set based on the type of the Signal. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.SignalConstraints.java (SignalInitialValueConstraint)</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">22</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All requirements have a source" </p> - </td> - <td align="left"> - <p style="margin-left:10px">The source of the requirement is set and non-empty. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.SourceConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">23</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All requirements traces are up to date." </p> - </td> - <td align="left"> - <p style="margin-left:10px">All traces are up-to-date. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.TraceConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Trace</p> - </td> - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">24</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All requirements are implemented" </p> - </td> - <td align="left"> - <p style="margin-left:10px">The requirement is traceable from some artifact. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.TraceNotEmptyConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Requirement</p> - </td> - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">25</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All components should have a meaningful name" </p> - </td> - <td align="left"> - <p style="margin-left:10px">The component has a meaningful name (i.e., No default names like "Component" or "Component1", "Component2"). - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.ComponentNameMeaningfulConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Component</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">26</p> - </td> - - <td align="left"> - <p style="margin-left:10px"> "All components should have a trace to requirement" </p> - </td> - <td align="left"> - <p style="margin-left:10px"> The component has a trace to a requirement. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.mira.constraints.ComponentToRequirementTraceExistsConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Component</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">30</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "If a component is traced to a functional requirement, its interface includes the one of the requirement."</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Every port in an interface requirement traced to a component is present in this component. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.specification.constraint.InterfaceTraceMatchConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Trace</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">33</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "Every top-level port of the component architecture shall be defined as a signal in the requirements."</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Every port of the top level component is defined a requirement signal. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.specification.constraint.TopComponentSignalsConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> ComponentArchitecture and Analysis</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">35</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All argument elements shall be connected to the safety argument structure"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The inspected argument element is connected to the whole argumentation structure. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.safetycases.constraint.ArgumentElementBaseInterconnectionConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> ContextualElement or SpinalElement</p> - </td> - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">36</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All argument elements shall have a name"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The inspected argument element base has a designated GSN name. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.safetycases.constraint.ArgumentElementBaseNameConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> ArgumentElementBase</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">37</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All argument elements shall be instantiated"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The inspected argument element is instantiated. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.safetycases.constraint.ArgumentElementInstantiatedConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> ArgumentElement</p> - </td> - - </tr> - <tr> - <td align="left"> - <p style="margin-left:10px">38</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All away argument elements shall be connected to an external argument element"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> That the inspected away argument element references an argument element located in another module. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.safetycases.constraint.AwayArgumentElementReferenceConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> AwayArgumentElement</p> - </td> - - </tr> - <tr> - <td align="left"> - <p style="margin-left:10px">39</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All optional connections are only for safety arguments patterns"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The inspected argument element the given safety case connection is marked as optional. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.safetycases.constraint.ConnectionIsOptionalConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> SafetyCasesConnection</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">40</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All connections with multiplicity are only for safety arguments patterns"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The inspected safety case connection is marked with multiplicity. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.safetycases.constraint.ConnectionMultiplicityConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> SafetyCasesConnection</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">41</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All goals shall be supported ultimately by a solution"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The inspected goal is supported by a solution. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.safetycases.constraint.GoalSupportingSolutionConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Goal</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">42</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All option entities are only for safety arguments patterns"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Option entities should not exist in a safety case but only in patterns. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.safetycases.constraint.OptionEntityExistanceConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> OptionEntity</p> - </td> - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">43</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All option entities shall be supported by options"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The inspected option entity is supported by goals. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.safetycases.constraint.OptionEntityOptionsConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> OptionEntity</p> - </td> - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">44</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All solutions shall be connected to an evidence artefact"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The inspected solution references to an evidence. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.safetycases.constraint.SolutionReferenceToEvidenceConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Solution</p> - </td> - - </tr> - - <tr> - <td align="left"> - <p style="margin-left:10px">46</p> - </td> - <td align="left"> - <p style="margin-left:10px"> "All strategies shall be supported by sub-goals!"</p> - </td> - <td align="left"> - <p style="margin-left:10px"> The inspected strategy is supported by sub-goals. - </p> - </td> - <td align="left"> - <p style="margin-left:10px"> org.fortiss.af3.safetycases.constraint.StrategySubgoalsConstraint.java</p> - </td> - <td align="left"> - <p style="margin-left:10px"> Strategy</p> - </td> - - </tr> - </table> -</body> - -</html> \ No newline at end of file diff --git a/org.fortiss.af3.rcp.help/html/process_constraints_definition.html b/org.fortiss.af3.rcp.help/html/process_constraints_definition.html deleted file mode 100644 index b176d4e..0000000 --- a/org.fortiss.af3.rcp.help/html/process_constraints_definition.html +++ /dev/null @@ -1,44 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> - -<!-- - Documentation of FOCUSer - FOCUS procEss AwaReness. - - @author lucio - @ConQAT.Rating ---> - -<html> -<head> - <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> - <title>FOCUSer - Making an AutoFOCUS3 (AF3) Aware of Modelling Processes</title> -</head> -<body> - - <li>The <b>Constraint</b> level: </li><br> Constraints are predicates that convey information about the model. When a constraint is active and evaluates to false, then errors or warnings are displayed in the IDE on top of the visible elements of the model those constraints relate to.<br><br> - A constraint needs to be defined programmatically. As an example we will define a constraint for the AF3 MIRA plugin that defines a software requirements gathering framework. This specific constraint evaluates if all requirements have a name.<br><br> - <ul> - <li> Step 1: Create your constraint as a java file in the <b>Constraint</b> folder in your plugin (you can simply copy, rename and modify a constraint if one exists). - <img src="./pictures/FOCUSER_constraint_plugin.png" style="max-height: 280px;"> - <br><br> - - <li> Step 2: Write the logic for the <b>verify</b> and the <b>isApplicable</b> methods. The <b>isApplicable</b> method checks for the correct type of model object to evaluate the constraint on. The <b>verify</b> methods contains the logic of the predicate.<br><br> - Note that a constraint class needs to inherit from the <b>AF3ProjectConstraintCheckerBase</b> and the <b>RequirementConstraintsGroup</b> classes. - <img src="./pictures/FOCUSER_constraint_class_definition.png" style="max-height: 300px;"> - <br><br> - - <li> Step 3: Activate the constraint in the base plugin (in this case MIRA), by adding the new constraint to the activator java class.<br><br> - <img src="./pictures/FOCUSER_activator_constraint.png" style="max-height: 100px;"><p> - <img src="./pictures/FOCUSER_activator_code.png" style="max-height: 100px;"> - <br><br> - - <li> Step 4: in the corresponding UI plugin (in our example for the MIRA plugin) in the <b>Constraint</b> folder, add the Java class that will manage the appearance of the constraint.<br><br> - <img src="./pictures/FOCUSER_constraint_plugin_ui.png" style="max-height: 180px;"><p> - <img src="./pictures/FOCUSER_constraint_plugin_java_ui.png" style="max-height: 500px;"> - - <li> Step 5: Activate the constraint in the corresponding UI plugin for MIRA, by adding the new constraint to the activator java class.<br><br> - <img src="./pictures/FOCUSER_constraint_ui_activator.png" style="max-height: 120px;"> - - </ul> - -</body> -</html> \ No newline at end of file diff --git a/org.fortiss.af3.rcp.help/html/process_definition.html b/org.fortiss.af3.rcp.help/html/process_definition.html deleted file mode 100644 index e8ad097..0000000 --- a/org.fortiss.af3.rcp.help/html/process_definition.html +++ /dev/null @@ -1,37 +0,0 @@ - <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> - -<!-- - Documentation of FOCUSer - FOCUS procEss AwaReness. - - @author abid - @ConQAT.Rating ---> - -<html> -<head> - <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> - <title>FOCUSer - Making an AutoFOCUS3 (AF3) Aware of Modeling Processes</title> -</head> -<body> - -<h2><font color="#336699">3. Defining your own process</font></h2> - -Defining a process using FOCUSer is done at two different levels: -<ul> - <li>The <b>Process </b> level: </li> <br> A FOCUSer process is defined in AF3's IDE as a set of objectives that depend on each other. Each objective is itself formed by a set of constraints that have been previously defined programmatically. How to define constraints is explained at the end of this section. In order to define a process you need to do the following:<br><br> - <ul> - <li> Step 1: In order to create a first objective double-click on your project and edit your constraint on the panel on the right.<br> - <img src="./pictures/FOCUSER_create_new_objective.png" style="max-height: 350px;"><br> - <li> Step 2: After naming the objective you can then select the constraints that should be active by ticking them off by selecting an appropriate constraint group. Note that for the objective to be fulfilled all of its constraints need to be satisfied by the model.<br><br> - <img src="./pictures/FOCUSER_select_constraints_for_objective.png" style="max-height: 400px;"><br><br> - The group name is associated with additional information as a triple [True, False, Total] where, 1) True: number of constraints that are satisfied in this group, 2) False: number of constraints that are not satisfied in the group and 3) Total: total number of constraints in the constraints group. It is to be noted here that this information appear when the objective is active (i.e., selected as current objective).<br><br> - <img src="./pictures/FOCUSER_ConstraintsGroupTripleExample.png" style="max-height: 400px;"><br><br> - <li> Step 3: Objectives can depend on other objectives, which semantically means that in order for the objective to be fulfilled its dependencies need to be first satisfied.<br> - <img src="./pictures/FOCUSER_constraints_objective_dependencies.png" style="max-height: 320px;"><br> - </ul> - <br><br> - <li>The <b>Constraint</b> level: </li><br> Constraints are predicates that convey information about the model. When a constraint is active and evaluates to false, then errors or warnings are displayed in the IDE on top of the visible elements of the model those constraints relate to.<br> - A constraint is <a href="https://af3-developer.fortiss.org/projects/autofocus3/wiki/Add_a_new_constraint_on_a_metamodel">programmatically</a> defined. -</ul> - -</body> diff --git a/org.fortiss.af3.rcp.help/html/process_usage.html b/org.fortiss.af3.rcp.help/html/process_usage.html deleted file mode 100644 index cb2acbc..0000000 --- a/org.fortiss.af3.rcp.help/html/process_usage.html +++ /dev/null @@ -1,63 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> - -<!-- - Documentation of FOCUSer - FOCUS procEss AwaReness. - - @author lucio - @ConQAT.Rating ---> - -<html> -<head> - <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> - <title>FOCUSer - Making an AutoFOCUS3 (AF3) Aware of Modeling Processes</title> -</head> -<body> - -<h2><font color="#336699">2. Making use of FOCUSer during model development</font></h2> - -The main functionality of FOCUSer is to restrict the error and warning messages to the ones that are relevant to the modeling task at hand. This is achieved by guiding the user through the selection and activation of objectives that should be accomplished next. - -<h3><font color="#336699">2.1. Current and Upcoming objectives</font></h3> - -The AF3 IDE presents to the user the two combo boxes that allow making use of FOCUSer: the <b>current objective</b> and the <b>upcoming objective</b>.<br><br> - -<img src="./pictures/FOCUSER_current_upcoming_objective.png" style="max-height: 170px;"><br><br> - -<ul> -<li> <b>Current objective: </b> the current objective box displays which objective is currently set, which in turns activates all the constraints related to that objective. As a result, all errors and warnings related to those constraints will appear in the IDE (but no others). By using this box the modeler can set any objective in the process at any time and make it the current objective. Note that constraints implied by objectives transitively found in the dependency tree of the current objective are also activated.<br><br> - -<li> <b>Upcoming objective: </b> the upcoming objective box displays which objectives should be accomplished next, given the ones that were already fulfilled.<br> -</ul> - -<h3><font color="#336699">2.2. Using the process as a modeling aid</font></h3> - -In order to demonstrate the capabilities of FOCUSer we will build a partial project for aiding the modeler in building requirements using AF3's MIRA framework. The process includes three objectives that depend on each other as indicated by the arrows in the following figure. In the figure the direction of the arrows defines the direction of the dependencies.<br><br> - -<img src="./pictures/FOCUSER_requirements_process.png" style="max-height: 350px;"><br><br> - -Note that an (empty) default configuration is always present in the project. In our process in the figure above the default configuration corresponds to the <i>"At least one requirement exists"</i> constraint.<br><br> - -Once the modeler starts a building a requirements model, the color of the current objective box is set to the color red. This indicates the objective has not yet been satisfied.<br><br> - -<img src="./pictures/FOCUSER_default_configuration.png" style="max-height: 200px;"><br><br><br> - -The modeler can then right-click on the error message to understand what the current required modeling actions are that will lead to fulfilling the active constraints.<br><br> - -<img src="./pictures/FOCUSER_constraint_message.png" style="max-height: 240px;"><br><br><br> - -Once a requirement has been added the color of the current objective is set to green and the upcoming objective is set to the one(s) that depend on it (in this case that all requirements should have a name).<br><br> - -<img src="./pictures/FOCUSER_default_configuration_OK.png" style="max-height: 180px;"><br><br><br> - -The modeler can then turn the upcoming objective into the current objective by selecting it from the combo box.<br><br> - -<img src="./pictures/FOCUSER_select_upcoming_objective.png" style="max-height: 180px;"><br><br><br> - -Note that it is possible for the modeler to understand which percentage of the objective at hand is already complete. This is achieved by hovering the mouse on the "current objective" combo box. The percentage is calculated in terms of the number of instances of the constraints that currently exist in the project. Note that for example for the "All requirements have a name" constraint, one instance of it will exist per requirement in the project.<br><br> - -<img src="./pictures/FOCUSER_percentage_complete.png" style="max-height: 260px;"><br><br><br> - - -</body> -</html> \ No newline at end of file -- GitLab