[safety-maintenance] Manual maintenance annotations
The user may manually annotate any GSN node as \textit{to be maintained} by right-clicking on the node and selecting the corresponding button within the displayed context menu. After pressing such a button a dialog opens , where the user has to select the type of impact, i.e., challenged, potentially impacted or actually impacted. Furthermore, in the same dialog, the user may optionally input information regarding the change impacting the node, namely he or she can reference the changed artefact (either AF3 native model elements or external files) or assurance case node and select the change type from a list of predefined types of changes, list created during the preparation of the assurance case for maintenance (see the previous paragraph). When the desired change is not within the list, the user may also write the type of change in the Define Change Type text field. In the model, the change impacting the node is added to the list of current changes affecting the respective node. After the user deals with the impact of certain changes on a node, he or she may press the Change Impact Solved button of the node’s context menu. Pressing this button will open a dialog where the user can select the changes whose impact has been solved and delete them . The node’s to be maintained attribute will be set to false only when the impact of all changes has been dealt with.
(from redmine: issue id 3783, created on 2019-07-28, closed on 2020-04-06)
- Relations:
- child #3732 (closed)
- child #3986 (closed)
- parent #3009