Project

General

Profile

Actions

Bug #28930

closed

HARA - Editing Exposure, Severity, and Controllability Values in Branching Scenarios Allows ASIL Recalculation Despite Existing FSR Allocations or Decompositions

Added by Vani Kunnatheri 8 months ago. Updated 7 months ago.

Status:
Closed
Priority:
Medium
Start date:
08/16/2024
Due date:
% Done:

0%

Estimated time:
Steps To Reproduce:

1.Log into FST
2.Select the HARA page
3.Add branch of details and calculate the ASIL.
4.Assign a safety goal against the ASIL
5.Go to FSR
6.Add a Function and Requirement
7.allcoate to a child
8.Go to HARA
9.Add a safety goal branch
10.Try to change the Exposure, severity and Controllability values of the Existing using Safety goal.
11.Please observe.

MODULES:
FST
Build Cycle:
Cycle 3
Customer:
Issue Dependency:
Dev Commitment to Resolve in::
ISSUE TYPE:
EXISTING

Description

In certain branching scenarios, it is possible to edit the Exposure, Severity, and Controllability values and recalculate the ASIL, even if there are existing allocations on the FSR page or if the function has been decomposed.

Please find the scenarios:
There is a Safety Goal 1 with an FSR Child Allocation or Decomposition, other safety goal or ASIL doesnt have any allocations.

1) Under One operational situation, if there are 2 Safety Goal branches (Safety Goal 1 and Safety goal2)
It's possible to update Exposure, Severity and Controllability values in HARA page and Exposure value in Operational Situation page.

2)Under One operational situation, if there are 2 Effect Branches ,
It's possible to update Exposure value in the HARA page and Operational Situation page.

3)Under One operational situation, if there are 2 Malfunction branches , It's not possible to update any values in the HARA page, but possible to update Exposure in the Operational Situation page.


Files

ASIL Mismatch in FSR.png (66.7 KB) ASIL Mismatch in FSR.png Vani Kunnatheri, 08/16/2024 12:31 AM
ASIL mismatch in FSR 1.png (60.4 KB) ASIL mismatch in FSR 1.png Vani Kunnatheri, 08/16/2024 12:31 AM
Actions #1

Updated by Vani Kunnatheri 8 months ago

  • Description updated (diff)
Actions #2

Updated by Vani Kunnatheri 8 months ago

Bug id in 112016: #28931

Actions #3

Updated by Manivannan Uppiliappan 8 months ago

  • Status changed from New to Open
  • Assignee changed from chitra Kalangiam to Manivannan Uppiliappan
Actions #4

Updated by Manivannan Uppiliappan 8 months ago

  • Status changed from Open to Resolved
Actions #5

Updated by Vani Kunnatheri 8 months ago

  • Status changed from Resolved to Not Resolved
  • How do we missed in Testing ? set to missed branching scenarios

Kindly check the patches , still same issue exists in FSR Decomposition

Actions #6

Updated by Manivannan Uppiliappan 7 months ago

  • Status changed from Not Resolved to Resolved
Actions #7

Updated by Vani Kunnatheri 7 months ago

  • Status changed from Resolved to Closed

verified and closed in cycle 4

Actions

Also available in: Atom PDF