Project

General

Profile

Actions

Bug #2766

closed

FSR- Add a function (1) to the Safety Goal (C) and Add function 2 to safety Goal (B) now decompose the function (1) under Function (2), here system does not changes the ASIL parent ASIL value. refer sheet

Added by Anonymous over 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Start date:
09/07/2017
Due date:
% Done:

0%

Estimated time:
Steps To Reproduce:

1. Click on FST
2. Add Function 1 to SG C
3. Add Function 2 to SG B
4. Decompose Function 1 to SG D
Refer sheet

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

Description

FSR- Add a function (1) to the Safety Goal (C) and Add function 2 to safety Goal (B) now decompose the function (1) under Function (2), here system does not changes the ASIL parent ASIL value. refer sheet


Files

ScreenShot283.bmp (1.95 MB) ScreenShot283.bmp Anonymous, 09/07/2017 02:44 PM
Actions #1

Updated by User Admin over 7 years ago

  • Status changed from New to Open
Actions #2

Updated by Anonymous over 7 years ago

  • Status changed from Open to TBD
Actions #3

Updated by Anonymous over 7 years ago

  • Project changed from EwQIMS SP700 to EwQIMS SP730
  • Build Cycle changed from Cycle 9 to Cycle 0
Actions #4

Updated by Anonymous over 7 years ago

  • Status changed from TBD to Resolved
Actions #5

Updated by Anonymous about 7 years ago

  • Status changed from Resolved to Not Resolved
Actions #6

Updated by Anonymous about 7 years ago

  • Status changed from Not Resolved to Resolved

Discussed with QA, this is a functionality and not an issue

Actions #7

Updated by Anonymous about 7 years ago

  • Status changed from Resolved to Not Resolved

In the HARA Document ASIL value is generated. The Generated ASIL value is Used in FSR. Now change the ASIL Value in Hara Document by changing the Operation Situation Exposure value. The ASIL Value is getting changed in Hara Document but it is not getting changed in FSR Document.

Actions #8

Updated by Anonymous about 7 years ago

  • Status changed from Not Resolved to Resolved
Actions #9

Updated by Anonymous about 7 years ago

  • Status changed from Resolved to Closed

Issue closed on 23-02-2017 in Cycle-4

Actions

Also available in: Atom PDF