FMEDA - Functional safety - ISSUES

As described in the SRS, the state of the PCM-SMs can change between one display of the dialog and the next. But, it can also change after pressing the Add button or the Delete button. The SAME logic should apply, since the number of PCM-SMs is changing in all of these cases. Here is the part of the SRS that describes this:

Note that the state of the PCM-SMs can change between one display of the dialog and the next. The only difference between opening the dialog for the first time and subsequent times is that there could be DFailU/DCauU properties after the first time. FTA0920: So, based on their existence and validity, do the following for the checkbox and textbox fields when opening the dialog:
If there are valid DFailU/DCauU property values then
If #PCM-SMs >= 1 then
Enable SM Name and Diag Cov fields
Display DFailU/DCauU properties in the fields
Don’t check the checkbox
Else
Delete DFailU/DCauU properties
Don’t check the checkbox
Else
Delete DFailU/DCauU properties, if any (could be invalid –
one property but not the other or Diag Cov not valid)
If #PCM-SMs = 0 then
Disable SM Name and Diag Cov fields
Don’t check the checkbox
Else If #PCM-SMs = 1 then
Disable SM Name and Diag Cov fields
Display PCM-SM properties in the fields
Check the checkbox
Else If #PCM-SMs >= 2 then
Enable SM Name and Diag Cov fields
Don’t check the checkbox

Since this dialog saves data to the DB (such as the Edit SM Dist values) and the Add/Delete PCM-SMs, the Cancel button should be renamed to Close, since Cancel implies the user can cancel all actions done in the dialog and this is not true. The different, then, between OK and Close will be that OK will do the required verifications (such as making sure FM Dist = 100), whereas Close means close the dialog without verifications.