Add satisfied_by requirement links

docs/features/analysis-infra/logging/docs/requirements/mw-fr_logging_req.rst

@@ -25,6 +25,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support local timestamps for each log entry.
@@ -35,6 +36,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support original timestamps for routed log entries.
@@ -45,6 +47,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support timestamp synchronization for log entries coming from different :term:`logging nodes <logging node>`.
@@ -55,6 +58,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging framework shall support a log level for each log entry.
@@ -65,6 +69,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging framework shall prioritize logs in case of resource conflicts to ensure critical logs are not lost.
@@ -75,6 +80,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support logging of early startup events to capture critical initialization information.
@@ -85,6 +91,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support :term:`logging entity identifiers<logging entity identifier>` for each log entry.
@@ -95,6 +102,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support filtering by :term:`log levels <Log level>`.
@@ -105,6 +113,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support filtering by :term:`logging entity identifiers<logging entity identifier>`.
@@ -115,6 +124,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall detect and report any message loss.
@@ -125,6 +135,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall provide mechanisms to handle message loss gracefully.
@@ -137,6 +148,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall allow context-specific :term:`log level` activation at runtime to enable fine-grained control over logging behavior.
@@ -147,6 +159,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support user application as log source.
@@ -157,6 +170,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support :term:`component` features and :term:` platform` as log sources.
@@ -167,6 +181,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support console as a log sink.
@@ -177,6 +192,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support local file system as log sink.
@@ -189,6 +205,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support cloud-native drives via network as log sinks.
@@ -199,6 +216,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support network channels, including a second dedicated Ethernet channel, as log sinks.
@@ -209,6 +227,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall ensure logs appear on stdout when running unit tests.
@@ -219,6 +238,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__boot_logging
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support logging of data to memory which survives a reboot
@@ -230,6 +250,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support configuration of :term:`log levels <Log level>`.
@@ -240,6 +261,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support configuration of the log storage device.
@@ -250,6 +272,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support multiple log storage devices.
@@ -260,6 +283,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support configurable :term:`log storage strategy`.
@@ -270,6 +294,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall allow configuration of internal buffers sizes.
@@ -280,6 +305,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall allow configuration of storage size per log file.
@@ -290,6 +316,7 @@ Requirements
    :security: YES
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall allow configuration of permission settings for log access.
@@ -300,6 +327,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall allow configuration of log filters.
@@ -310,6 +338,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall allow configuration of logging entity IDs.
@@ -320,6 +349,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support on-demand functionality, such as enabling or disabling log storage.
@@ -330,6 +360,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall provide fallback configurations, such as application-wide or system-wide defaults.
@@ -340,6 +371,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall allow extensions for custom log types.
@@ -350,6 +382,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    In case of recoverable error, the logging :term:`framework` shall continue the current operations.
@@ -360,6 +393,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    In case of non-recoverable error, the logging :term:`framework` shall deactivate silently and set an error state reported on shutdown.
@@ -370,6 +404,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall ensure that user applications are not affected by logging :term:`framework` errors.
@@ -380,6 +415,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support QNX and Linux operating systems (encapsulated via OSAL).
@@ -390,6 +426,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support, stkh_req__dev_experience__prog_languages
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support C++, Rust, and Python programming languages.
@@ -400,6 +437,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall minimize storage resource consumption.
@@ -410,6 +448,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall minimize communication channel resource consumption.
@@ -420,6 +459,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall minimize runtime resource consumption.
@@ -430,6 +470,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall have low impact on overall system performance.
@@ -440,6 +481,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall provide:term:` QoS` for handling overflows or dropping log messages.
@@ -451,6 +493,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support, stkh_req__overall_goals__enable_cooperation
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall be :term:`DLT` compatible.
@@ -463,6 +506,7 @@ Requirements
    :security: YES
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support, stkh_req__dependability__security_features
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall ensure that only authorized users can access log files.
@@ -473,6 +517,7 @@ Requirements
    :security: NO
    :safety: ASIL_B
    :satisfies: stkh_req__functional_req__safe_comput
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall support the ASIL level of the user function to ensure compliance with the safety requirements of the application.
@@ -485,6 +530,7 @@ Requirements
    :security: NO
    :safety: QM
    :satisfies: stkh_req__dev_experience__logging_support
+   :satisfied_by: feat__logging
    :status: valid
 
    The logging :term:`framework` shall be classified according to the overall system's safety concept if logging information is part of the verification strategy.