From 246cd3ff7c7a3715ef9ee065df5fff5cd6b11119 Mon Sep 17 00:00:00 2001 From: Punam Verma Date: Tue, 31 Oct 2023 13:29:02 -0700 Subject: [PATCH] Per PR review, created a new requirement for no notifications --- .../interuss/f3548/notification_requirements.md | 9 +++++++++ .../validate_no_notification_operational_intent.md | 2 +- 2 files changed, 10 insertions(+), 1 deletion(-) create mode 100644 monitoring/uss_qualifier/requirements/interuss/f3548/notification_requirements.md diff --git a/monitoring/uss_qualifier/requirements/interuss/f3548/notification_requirements.md b/monitoring/uss_qualifier/requirements/interuss/f3548/notification_requirements.md new file mode 100644 index 0000000000..d0cff3adda --- /dev/null +++ b/monitoring/uss_qualifier/requirements/interuss/f3548/notification_requirements.md @@ -0,0 +1,9 @@ +# ASTM F3548-21 notifications requirement + +While ASTM F3548-21 does not specifically prohibit sending notifications for operational intent changes when those notifications were not specifically prescribed by a notification that an operational intent may be relevant to a subscription (response from the DSS), InterUSS expects that notifications will only be sent at these particular times. +SCD0085 requirement states only a positive requirement (preconditions satisified => notification must be sent). +It doesn't establish a negative requirement (preconditions not satisfied => no notifications may be sent). +As these negative requirements are reasonable and related to SCD0085, interUSS has added it as a requirement for testing. +This can happen in following situations - + - If a USS was unable to write an entity reference to the DSS, it should not erroneously notify that operational intent, to another USS subscribed in the area. + - A USS wrote an entity reference to the DSS, and was not notified of any other USS subscription, so it should not send a notification to any USS. So the USS shall (OnlyPrescribedNotifications) only send operational intent notifications when prescribed by SCD0085. diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/data_exchange_validation/test_steps/validate_no_notification_operational_intent.md b/monitoring/uss_qualifier/scenarios/astm/utm/data_exchange_validation/test_steps/validate_no_notification_operational_intent.md index e534f77f39..3cabd872fa 100644 --- a/monitoring/uss_qualifier/scenarios/astm/utm/data_exchange_validation/test_steps/validate_no_notification_operational_intent.md +++ b/monitoring/uss_qualifier/scenarios/astm/utm/data_exchange_validation/test_steps/validate_no_notification_operational_intent.md @@ -7,4 +7,4 @@ This step verifies when a flight is not created, it is also not notified by chec ## Expect Notification not sent check -**[astm.f3548.v21.SCD0085](../../../../../requirements/astm/f3548/v21.md)** +**[interuss.f3548.notification_requirements](../../../../../requirements/interuss/f3548/notification_requirements.md)**