Project

General

Profile

Feature #3500

Feature #3009: [safety-maintenance] Safety Case Maintenance

[safety-maintenance] Check button for viewing challenge impact traces

Added by Carmen Carlan about 2 years ago. Updated 5 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Start date:
08/31/2018
Due date:
% Done:

100%

Estimated time:

SimpleTrafficLights_AF3Tour.af3_23 (310 KB) SimpleTrafficLights_AF3Tour.af3_23 Carmen Carlan, 10/23/2019 04:32 PM

History

#1 Updated by Johannes Eder over 1 year ago

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

#2 Updated by Carmen Carlan about 1 year ago

  • Status changed from New to Resolved
  • Assignee changed from Anonymous to Carmen Carlan

#3 Updated by Carmen Carlan about 1 year ago

  • Subject changed from [safety] Check button for viewing challenge impact traces to [safety-maintenance] Check button for viewing challenge impact traces

#4 Updated by Carmen Carlan about 1 year ago

The user can select in the Properties view if he or she wants to visualize the change impact analysis results (impacted GSN nodes are depicted in different colors).

#5 Updated by Carmen Carlan about 1 year ago

The user can select in the Contex Menu of any ArgumentModule if he or she wants to visualize the change impact analysis results (impacted GSN nodes are depicted in different colors).

#6 Updated by Carmen Carlan about 1 year ago

  • % Done changed from 0 to 100

#7 Updated by Carmen Carlan about 1 year ago

Carmen Carlan wrote:

The user can select in the Contex Menu of any ArgumentModule if he or she wants to visualize the change impact analysis results (impacted GSN nodes are depicted in different colors).

The buttons are: "Do not show challenged elements" and "Show challenged elements"

#8 Updated by Simon Barner about 1 year ago

  • Status changed from Resolved to Feedback

Please provide a model with which the effects of the buttons can be tested. I.e., briefly describe the expected effects of the applying the "Do not show challenged elements" and the "Show challenged elements" button.

#9 Updated by Simon Barner 12 months ago

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

#10 Updated by Carmen Carlan 11 months ago

Simon Barner wrote:

Please provide a model with which the effects of the buttons can be tested. I.e., briefly describe the expected effects of the applying the "Do not show challenged elements" and the "Show challenged elements" button.

Attached the model, which contains an argument module within the safety cases, where elements are annotated as "challenged" or "potentially impacted". These annotations are depicted also visually as the nodes have different colors, depending on their state (the challenged nodes are red, whereas the potentially impacted nodes are yellow)- The user may right-click on the argument module and select the button "Do not show challenged elements". This would make the different coloring of challenged and potentially impacted nodes disappear. When the user wants to again visualize such maintainance-specific annotations, he/she can right-click again on the argument module and press the "Show challenged elements" button.

#11 Updated by Simon Barner 11 months ago

  • Assignee changed from Simon Barner to Carmen Carlan
Code reviewed (https://git.fortiss.org/af3/af3/tree/3500-ShowingImpactTraces), please check:
  • ChangeAffectionSolved
  • ShowHideChallengedElements
Further, the use of the feature (and the related context menu entries) is not very intuitive. I suggest the following (can also be moved to additional ticket(s))
  • Extend documentation with a state machine that explains the different states an element can be in (challenged, private, ... everything that can be toggled in the context menu and that can assign a different color to an element)
  • Establish visual correspondence between context menu element (e.g. the icon or at least the color of the icon shown in the menu) and the effect it has in the diagram (e.g., display the icon as a decoration, e.g. the lock symbol to mark private elements, the new color of an element, ...)

#12 Updated by Carmen Carlan 5 months ago

  • Assignee changed from Carmen Carlan to Johannes Eder

Please reject this issue - it's absolute

#13 Updated by Johannes Eder 5 months ago

  • Status changed from Feedback to Rejected
  • Assignee deleted (Johannes Eder)

Also available in: Atom PDF