This affects DMS-REQ-0004, DMS-REQ-0392 (new), DMS-REQ-0391 (new), and DMS-REQ-0393 (new).

Associated LVVs (verification elements):
DMS-REQ-0393: LVV-18299
DMS-REQ-0392: LVV-18298
DMS-REQ-0391: LVV-18297 (test case: LVV-T1867), LVV-18911 (test case: LVV-T1868)
DMS-REQ-0004: LVV-175 (LVV-T35, LVV-T95), LVV-9740 (LVV-T1276), LVV-9803 (LVV-T102)

Requested additional VEs for DMS-REQ-0392 and 0393:

Slack message:

Hi Austin - when you get a chance, could you please create some additional verification elements? LVV-18298 and LVV-18299 have multiple parameters to be tested, so I would like to have one LVV for each of those parameters. (LVV-18298 has 5 requirement parameters, so needs 5 VEs, and LVV-18299 has 2 parameters.) You can use the following names for them:
DMS-REQ-0392-V-01: Fraction of Alerts Transmitted
DMS-REQ-0392-V-02: Max Alert Failure Fraction
DMS-REQ-0392-V-03: Latency of Reporting Transients
DMS-REQ-0392-V-04: Peak Number of Alerts
DMS-REQ-0392-V-05: Max Fraction of Visits With Alert Delays

DMS-REQ-0393-V-01: Average Number of Alerts Per Visit
DMS-REQ-0393-V-02: Peak Number of Alerts Per Visit

Newly added verification elements:
LVV-19218: DMS-REQ-0392-V-05: Max Fraction of Visits With Alert Delays
LVV-19217: DMS-REQ-0393-V-02: Peak Number of Alerts Per Visit
LVV-19216: DMS-REQ-0392-V-04: Peak Number of Alerts
LVV-19215: DMS-REQ-0392-V-03: Latency of Reporting Transients
LVV-19214: DMS-REQ-0392-V-02: Max Alert Failure Fraction

All of these VEs now have place-holder Test Cases associated with them.

looks good