Project

General

Profile

Actions

Bug #30206

open

FSR - Higher ASIL Concept Displays Incorrect ASIL and Base Requirement Lacks Color Code After Adding Requirement Branch (NON STD ASIL CONCEPTS - SME clarifucation needed)

Added by Vani Kunnatheri 2 months ago. Updated 3 days ago.

Status:
Not Resolved
Priority:
Medium
Start date:
02/14/2025
Due date:
% Done:

0%

Estimated time:
Steps To Reproduce:

1.Log into FSR
2. Locate a standard D , nonstandard C and B safety goals
3. Add a function against standard D
4.Re use it against non standard B
5.Delete it from B
6.Reuse against C
7.Add a requirement branch under C
8.Please observe

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

Description

1. I used the same FSR function for Standard D and Non-Standard B safety goals. Then, I deleted the function from Non-Standard B and added it to Non-Standard C . After adding a requirement branch under C , the higher ASIL concept failed on the added requirement branch, displaying C instead of D. Additionally, the base requirement does not display the correct color code.

2.I reused the same function and requirement across all possible combinations of safety goals and added a requirement branch under Non-Standard C. However, the base requirement for the Non-Standard ASIL safety goal lacks color in the Req ASIL column(except D)


Files

clipboard-202502140919-mjqqq.png (55.1 KB) clipboard-202502140919-mjqqq.png Vani Kunnatheri, 02/14/2025 07:49 PM
clipboard-202502140921-grkys.png (113 KB) clipboard-202502140921-grkys.png Vani Kunnatheri, 02/14/2025 07:51 PM
clipboard-202503070900-qqhvz.png (50 KB) clipboard-202503070900-qqhvz.png Vani Kunnatheri, 03/07/2025 07:30 PM
Actions

Also available in: Atom PDF