Project

General

Profile

Actions

Bug #28460

closed

HARA-OS : Exposure Value Changes in HARA Page or Operational Situation Do Not Trigger Alerts -Multi branch OS

Added by Vani Kunnatheri 10 months ago. Updated 9 months ago.

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

0%

Estimated time:
Steps To Reproduce:

1.Log into FST
2.Select FSR page
3.Select the Focus element.
4.Add a Function and Requirement against a standard safety goal.
5.Make a allocation to a child.
6.Go back to HARA page.
7.Add one more malfunction branch under the Operational situation to make it as a multi branch one.
8.Double click on the Exposure column and observe .

MODULES:
FST
Build Cycle:
Cycle 1
Customer:
Issue Dependency:
Dev Commitment to Resolve in::

Description

Even after an FSR function and requirement are allocated to a child, it is possible to go back to the HARA page or Operational Situation page and change the Exposure value if the Operational Situation has multiple branches. No alert is thrown, and the ASIL is recalculated, but the changes do not reflect in the allocations on the FSR page


Files

exposure change.png (172 KB) exposure change.png Vani Kunnatheri, 07/08/2024 08:23 PM
Actions

Also available in: Atom PDF