Bug #28223
closedFSR- Issue with Non Standard ASIL Safety Goals
0%
1.Log into FST
2.Go to Safetuy Goals page in the HARA menu.
3.Create a safety goal and choose a value from the drop down.
4.Go to FSR page.
5.Add a function and Requirement against the Safety goal.
6.Please observe the cell boarders of the last element.
7.Double click and allocate a non standard ASIL value against a child.
8.Observe the Cell boarder.
9.Deallocate the same element and observe the boarders.
10. Edit the Requirement and observe the updated value and 'Reqt ASIL' column.
11.Observe the ASIL column in the VOC page.
Description
1. Even after adding the function and requirement, the last elements' borders are not populating for a non-standard ASIL safety goal.
2. If we allocate a cell, it reflects in its adjacent cell.
3. When allocated for one element, the missed borders display, but when we deallocate it, they disappear
4. When editing the initially added FSR requirement for the first time, it does not reflect the changes, although the 'Reqt ASIL' is populated.
5. In the VOC page, ASIL is displayed as 'Standard ASIL' in bold letters
Suggestions :
1. Suggesting bringing up the 'Reqt ASIL' values when adding function and requirement against the non-standard ASIL
2. When allocating a higher non-standard ASIL to the child, the 'Reqt ASIL' should be updated to the highest value.
3. If we enable the option to right-click and choose 'Allocate ASIL', it should only display non-standard ASIL value.
Files
Updated by Vani Kunnatheri 11 months ago
Test cases :
http://14.194.186.13:8080/testlink/linkto.php?tprojectPrefix=EwQIMS&item=testcase&id=EwQIMS-41259
http://14.194.186.13:8080/testlink/linkto.php?tprojectPrefix=EwQIMS&item=testcase&id=EwQIMS-41260
http://14.194.186.13:8080/testlink/linkto.php?tprojectPrefix=EwQIMS&item=testcase&id=EwQIMS-41261
http://14.194.186.13:8080/testlink/linkto.php?tprojectPrefix=EwQIMS&item=testcase&id=EwQIMS-41263
Updated by Gopinath Ramamoorthy 11 months ago
- MODULES FST added
- MODULES deleted (
RFD)
Updated by Manivannan Uppiliappan 11 months ago
- Status changed from Open to Resolved
Updated by Vani Kunnatheri 11 months ago
- Status changed from Resolved to Not Resolved
Updated by Manivannan Uppiliappan 10 months ago
- Status changed from Not Resolved to Resolved
Updated by Vani Kunnatheri 10 months ago
- Status changed from Resolved to Closed
Closed in SP 11.3.0 Cycle 1