Bug #29208: FSR - Adding a same requirement for different FSR Functions, system does not display the higher ASIL value.(Refer Description) - SP 11.2.0.17 Patches - OMNEX ISSUE TRACKER

Actions

Copy link

Bug #29208

closed

FSR - Adding a same requirement for different FSR Functions, system does not display the higher ASIL value.(Refer Description)

Added by Shankar Narayanan 8 months ago. Updated 6 months ago.

Status:

Closed

Priority:

Medium

Assignee:

Manivannan Uppiliappan

Start date:

10/04/2024

Due date:

% Done:

Estimated time:

Steps To Reproduce:

1. Log in to the FST.
2. Select the Functional Safety Requirement menu
3. For Safety goal 1 add a Function and Requirement and Observe the ASIL value
4. Now for safety goal 2, add a different Function and same requirement of safety goal 1.
5. Observe the ASIL value for Safety goal 2
6. Now decompose SG 2 to two different Functions/Requirements and observe the ASIL
7. Add the function of SG 2 in the SG 1 new row
8.Now the ASIL for last row alone changes properly

MODULES:

FST

Build Cycle:

Cycle 1

Customer:

Issue Dependency:

Dev Commitment to Resolve in::

Description

Adding a same requirement for different FSR Functions, system does not display the higher ASIL value. And after doing this, I could not able to allocate ASIL to child elements.

But if the same set of Functions and requirements are added to another Safety goal, then it shows the the last decomposed requirement with correct ASIL value.

NOTE:As discussed with Nikhil, ASIL value is liable on the FSR Function set only. It does not change on the basis of requirement.

Files

Download all files

2024-10-04 FSR 1.png (85.9 KB) 2024-10-04 FSR 1.png		Shankar Narayanan, 10/04/2024 10:14 AM
2024-10-04 FSR 2.png (98.9 KB) 2024-10-04 FSR 2.png		Shankar Narayanan, 10/04/2024 10:14 AM