Project

General

Profile

Feature #3170

Feature #3784: [safety-creation] Creating and manipulating safety cases

[safety-creation] Revival of safety case typed patterns

Added by Carmen Carlan almost 3 years ago. Updated 7 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
-
Start date:
08/29/2017
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

Subtasks

Support #3064: [safety] Eliminate Requirements Patterns ViewClosed

Support #3171: [safety] Refactor ComponentInstantiationWizardPageBackend classRejected

Feature #3172: [safety] Refactor ComponentsInstantiationWizardPageBackend classRejected

Support #3173: [safety] Get rid off RequirementsPatternsView viewRejected

Support #3174: Refactor InstantiationOfGSNElementsUtils classClosed

History

#1 Updated by Simon Barner over 2 years ago

  • Target version changed from AF3 2.12 Post-release to AF3 2.13 RC1 (Feature Freeze)

#2 Updated by Carmen Carlan over 2 years ago

  • Target version changed from AF3 2.13 RC1 (Feature Freeze) to AF3 2.14 RC1 (Feature Freeze)

#3 Updated by Carmen Carlan over 1 year ago

  • Target version changed from AF3 2.14 RC1 (Feature Freeze) to AF3 2.15 RC1 (Feature Freeze)

Rename: Add to Pattern Library
Rename: Disconnect from Library (appears twice)
Re-evaluate the types of variables
Constraints on the variables
Type of context: “variable declaration”
Word → Variable
Name
Type
GSN Element
Parameterized safety claim
Database
Safety Claim Pattern (of type Parameterized safety claim)
Instantiation of a variable
Propagation if it’s in a context
Check if the variable does not already exist
Patterns information
No scroll bar
Safety Claim Pattern → Property section
Is instantiated
Words and Sentences → Property section
Is instantiated

#4 Updated by Johannes Eder over 1 year ago

  • Target version changed from AF3 2.15 RC1 (Feature Freeze) to AF3 2.16 RC1 (Feature Freeze)

#5 Updated by Carmen Carlan about 1 year ago

Enabling typed claims. The claims in argument elements within patterns may contain word in curly brackets that shall be then replaced with information specific to the system the pattern is instantiated for. While such claims may be written as strings in the corresponding text field in the \textit{Properties View} of any GSN-based entity, in ExplicitCase we also enable the specification of typed claims. After writing the text of the claim in the corresponding text field, by pressing the declare variable button in the Properties View, the user may create for each world in curly brackets a variable, declaring the variable's type and name.

Instantiation of optional relationships. When instantiating a pattern, the user may right-click on relationships annotated as optional and select the \textit{Delete relationship} button. If the target argument element of the respective relationship is not connected to any other part of the argumentation, then the respective element is deleted, together with the respective relationship. If the target argument element is a strategy or goal and it does not have any other parents, then, together with the relationship and its target argument element also all the children elements (i.e., subgoals, strategies, contextual elements) are deleted.

Instantiation of generalized relationships. If the multiplicity annotation of a relationship is set to true, the user may right-click on the respective relationship and, if wanted, may multiply the argumentation targeted by this relationship, by pressing the \textit{Multiply} button. As the argumentation targeted by a relationship we consider the targeted argumentation element and all the other elements connected to it. When the button is pressed, a dialog opens where the user can select how many instances of the argumentation targeted by the relationship shall be created.

Typed instantiation of claims. If the claim of a node in the instantiated pattern is typed (i.e., it contains variables), the user can press the \textit{Instantiate claim} button in the in the Properties View. When this button is pressed, a dialog appears enabling the instantiation of the claim's variables. The words in the curly brackets of a to be instantiated element for which no variable has been declared are to be instantiated manually, in the text field, by replacing the respective words with a string.

#6 Updated by Carmen Carlan about 1 year ago

  • Subject changed from [safety] Revival of safety case typed patterns to [safety-creation] Revival of safety case typed patterns

#7 Updated by Carmen Carlan about 1 year ago

  • Parent task set to #3784

#8 Updated by Alexander Diewald 12 months ago

  • Target version changed from AF3 2.16 RC1 (Feature Freeze) to AF3 2.17 (Feature Freeze)

#9 Updated by Carmen Carlan 5 months ago

  • Assignee changed from Carmen Carlan to Liana Soima
  • Target version changed from AF3 2.17 (Feature Freeze) to AF3 2.18 - Feature Freeze
  • Disconnect from Library (appears twice)
  • Rename: Add to Patterns Library
  • Patterns do not appear in Model Elements view unless one is newly created
  • When adding a new pattern, make sure that all GSN nodes do not have references to system models, they do not entail annotations regarding change impact analysis and the away entities have no references to other nodes

#10 Updated by Carmen Carlan 7 days ago

Updated tasks:

Rename: Add to Pattern Library
Rename: Disconnect from Pattern Library (appears twice)

Patterns do not appear in Model Elements view unless one is newly created

When adding a new pattern, make sure that all GSN nodes do not have references to system models, they do not entail annotations regarding change impact analysis and the away entities have no references to other nodes

Enabling typed claims: For example, user can add to a claim @component(<no component>). This can be later on instantiated by CTRL+SPACE with references to components in logical architecture. The newly referenced component will be added to the GSN contruct's list of referenced elements

Instantiation of optional relationships: When instantiating a pattern, the user may right-click on relationships annotated as optional and select the \textit{Delete relationship} button. If the target argument element of the respective relationship is not connected to any other part of the argumentation, then the respective element is deleted, together with the respective relationship. If the target argument element is a strategy or goal and it does not have any other parents, then, together with the relationship and its target argument element also all the children elements (i.e., subgoals, strategies, contextual elements) are deleted.

Instantiation of generalized relationships. First, implement them properly (as in the GSN standard: https://scsc.uk/scsc-141B) If the multiplicity annotation of a relationship is set to true, the user may right-click on the respective relationship and, if wanted, may multiply the argumentation targeted by this relationship, by pressing the \textit{Multiply} button. As the argumentation targeted by a relationship we consider the targeted argumentation element and all the other elements connected to it. When the button is pressed, a dialog opens where the user can select how many instances of the argumentation targeted by the relationship shall be created.

Patterns information: No scroll bar, Make it more user friendly

Also available in: Atom PDF