Project

General

Profile

Actions
Copy link

Bug #2550

closed

FSR Allocate the ASIL value to the element does not display the Higher value to the parent requirement refer sheet

Added by Anonymous almost 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Medium
Assignee:
-
Start date:
08/02/2017
Due date:
% Done:

0%

Estimated time:
Steps To Reproduce:

1. Click on FSR
2. Decompose the function
3. With Different ASIL value to the requirement

MODULES:
FST
Build Cycle:
Cycle 0
Customer:
Issue Dependency:
700

Description

FSR Allocate the ASIL value to the element does not display the Higher value to the parent requirement

Files

Download all files
ScreenShot175.bmp (463 KB) ScreenShot175.bmp Anonymous, 08/02/2017 05:05 PM
ScreenShot288.bmp (1.65 MB) ScreenShot288.bmp Anonymous, 09/07/2017 06:19 PM
Actions
Copy link
 #1

Updated by User Admin almost 8 years ago

  • Status changed from New to Open
Actions
Copy link
 #2

Updated by Anonymous almost 8 years ago

  • Status changed from Open to In Progress
Actions
Copy link
 #3

Updated by Anonymous almost 8 years ago

  • Status changed from In Progress to Resolved
Actions
Copy link
 #4

Updated by Anonymous almost 8 years ago

  • Status changed from Resolved to Not Resolved
Actions
Copy link
 #5

Updated by Anonymous almost 8 years ago

  • Status changed from Not Resolved to Resolved
Actions
Copy link
 #6

Updated by Anonymous almost 8 years ago

Here it taks the Higher ASIL value for the subdivided function , but if the individual requirement is allocated with the ASIL value is not taking the highers response

Actions
Copy link
 #7

Updated by Anonymous almost 8 years ago

  • Subject changed from FSR Allocate the ASIL value to the element does not display the Higher value to the parent requirement to FSR Allocate the ASIL value to the element does not display the Higher value to the parent requirement refer sheet
Actions
Copy link
 #8

Updated by Anonymous almost 8 years ago

  • Status changed from Not Resolved to Closed
Actions
Copy link
 #9

Updated by Anonymous over 7 years ago

  • Project changed from EwQIMS SP700 to EwQIMS SP710
  • Status changed from Closed to Reopen
  • Issue Dependency set to 700

Issue reported in 700 it got Reopened in 710

Actions
Copy link
 #10

Updated by Anonymous over 7 years ago

  • Status changed from Reopen to Fixed with Hotfix
Actions
Copy link
 #11

Updated by Anonymous over 7 years ago

  • Status changed from Fixed with Hotfix to Not Fixed with Hotfix
Actions
Copy link
 #12

Updated by Anonymous over 7 years ago

  • Status changed from Not Fixed with Hotfix to Resolved
Actions
Copy link
 #13

Updated by Anonymous over 7 years ago

  • Status changed from Resolved to Not Resolved
Actions
Copy link
 #14

Updated by Anonymous over 7 years ago

  • Build Cycle changed from Cycle 4 to Cycle 3
Actions
Copy link
 #15

Updated by Anonymous over 7 years ago

  • Build Cycle changed from Cycle 3 to Cycle 0
Actions
Copy link
 #16

Updated by Anonymous over 7 years ago

  • Status changed from Not Resolved to Fixed in Dev
Actions
Copy link
 #17

Updated by Anonymous over 7 years ago

  • Status changed from Fixed in Dev to Resolved
Actions
Copy link
 #18

Updated by Anonymous over 7 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF