diff --git a/docs/features/analysis-infra/logging/docs/requirements/mw-fr_logging_req.rst b/docs/features/analysis-infra/logging/docs/requirements/mw-fr_logging_req.rst index 6bf1c427ecc..89a6e9c2364 100644 --- a/docs/features/analysis-infra/logging/docs/requirements/mw-fr_logging_req.rst +++ b/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 `. @@ -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` 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 `. @@ -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`. @@ -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 `. @@ -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. diff --git a/docs/features/baselibs/docs/requirements/index.rst b/docs/features/baselibs/docs/requirements/index.rst index f5ad55881b6..d4ab5509fd9 100644 --- a/docs/features/baselibs/docs/requirements/index.rst +++ b/docs/features/baselibs/docs/requirements/index.rst @@ -28,6 +28,7 @@ Requirements :security: NO :safety: QM :satisfies: stkh_req__functional_req__base_libraries + :satisfied_by: feat__baselibs :status: valid :tags: inspected @@ -39,6 +40,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__functional_req__base_libraries, stkh_req__dependability__automotive_safety + :satisfied_by: feat__baselibs :status: valid :tags: inspected @@ -50,6 +52,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__functional_req__base_libraries, stkh_req__dev_experience__prog_languages, stkh_req__dependability__automotive_safety + :satisfied_by: feat__baselibs :status: valid :tags: inspected @@ -61,6 +64,7 @@ Requirements :security: NO :safety: QM :satisfies: stkh_req__functional_req__base_libraries, stkh_req__dev_experience__prog_languages, stkh_req__overall_goals__reuse_of_app_soft + :satisfied_by: feat__baselibs :status: valid :tags: inspected @@ -72,6 +76,7 @@ Requirements :security: NO :safety: QM :satisfies: stkh_req__functional_req__base_libraries, stkh_req__overall_goals__reuse_of_app_soft + :satisfied_by: feat__baselibs :status: valid :tags: inspected @@ -83,6 +88,7 @@ Requirements :security: YES :safety: QM :satisfies: stkh_req__functional_req__base_libraries + :satisfied_by: feat__baselibs :status: valid :tags: inspected @@ -94,6 +100,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__functional_req__base_libraries + :satisfied_by: feat__baselibs :status: valid :tags: inspected @@ -105,6 +112,7 @@ Requirements :security: NO :safety: QM :satisfies: stkh_req__functional_req__base_libraries + :satisfied_by: feat__baselibs :status: valid :valid_from: v1.0.0 :tags: inspected @@ -121,6 +129,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__functional_req__base_libraries + :satisfied_by: feat__baselibs :status: valid :tags: inspected @@ -132,6 +141,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__functional_req__base_libraries + :satisfied_by: feat__baselibs :status: valid :tags: inspected @@ -143,6 +153,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__functional_req__base_libraries + :satisfied_by: feat__baselibs :status: valid :tags: inspected @@ -154,6 +165,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__functional_req__base_libraries, stkh_req__dependability__automotive_safety + :satisfied_by: feat__baselibs :status: valid :tags: inspected @@ -165,6 +177,7 @@ Requirements :security: YES :safety: ASIL_B :satisfies: stkh_req__functional_req__base_libraries + :satisfied_by: feat__baselibs :status: valid :tags: inspected @@ -176,10 +189,11 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__functional_req__base_libraries + :satisfied_by: feat__baselibs :status: valid :tags: inspected The base libraries shall provide a library for parallel execution of C++ callables with thread pool management. -.. needextend:: is_external == False and "__baselibs" in id +.. needextend:: is_external == False and "__baselibs" in id :+tags: baselibs diff --git a/docs/features/communication/docs/requirements/index.rst b/docs/features/communication/docs/requirements/index.rst index 167caedde52..8ccf88243c3 100644 --- a/docs/features/communication/docs/requirements/index.rst +++ b/docs/features/communication/docs/requirements/index.rst @@ -30,6 +30,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__app_architectures__support_time, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid The communication framework shall provide API to support a time-based architecture. @@ -40,6 +41,7 @@ Requirements :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process, stkh_req__app_architectures__support_data + :satisfied_by: feat__com_communication :status: valid The communication framework shall provide API to support a data-driven architecture. @@ -50,6 +52,7 @@ Requirements :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process, stkh_req__app_architectures__support_request + :satisfied_by: feat__com_communication :status: valid The communication framework shall provide API to support a request-driven architecture. @@ -60,6 +63,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__app_architectures__support_data,stkh_req__app_architectures__support_time, stkh_req__communication__safe, stkh_req__app_architectures__support_request + :satisfied_by: feat__com_communication :status: valid A communication interface consists of a combination of any number of the following elements: @@ -74,6 +78,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__app_architectures__support_time + :satisfied_by: feat__com_communication :status: valid An event-type is part of a communication interface and has: @@ -90,6 +95,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__app_architectures__support_request, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid A method is part of a communication interface and has: @@ -110,6 +116,7 @@ Requirements :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process, stkh_req__app_architectures__support_request + :satisfied_by: feat__com_communication :status: valid A signal is part of a communication interface and has: @@ -132,6 +139,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__app_architectures__support_time, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid Communication shall be cached based on the producer-consumer pattern. @@ -142,6 +150,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid Multiple service instances shall be able to offer the same interface. @@ -155,6 +164,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid A service instance is offered under one or more unique names by which it can be discovered. @@ -170,6 +180,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid The communication framework shall support versioning of service instances: @@ -186,6 +197,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid The interface to access service instances is agnostic to the binding used to communicate with the service. @@ -199,6 +211,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid The communication framework shall support stateless communication. @@ -213,6 +226,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid The communication framework shall support multiple service instances per software architecture element. @@ -226,6 +240,7 @@ Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid The communication framework shall provide service discovery to find available services during runtime. Service discovery shall consider version compatibility. Service discovery shall be handled implicitly (where possible). @@ -243,6 +258,7 @@ Mixed-Criticality safety systems :security: YES :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid The communication framework shall support safe communication involving communication partners on the same or multiple @@ -254,6 +270,7 @@ Mixed-Criticality safety systems :security: YES :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid Consumers with lower criticality shall not be able to corrupt data consumed by partners with higher criticality. @@ -264,6 +281,7 @@ Mixed-Criticality safety systems :security: YES :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid Consumers with lower criticality shall not be able to modify the order of data consumed by partners with higher @@ -275,6 +293,7 @@ Mixed-Criticality safety systems :security: YES :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid Consumers with lower criticality shall not be able to duplicate data consumed by other communication partners with @@ -286,6 +305,7 @@ Mixed-Criticality safety systems :security: YES :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid Consumers with lower criticality shall not be able to drop data before it is consumed by partners with higher @@ -301,6 +321,7 @@ Performance :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process,stkh_req__app_architectures__support_data, stkh_req__app_architectures__support_request + :satisfied_by: feat__com_communication :status: valid The communication framework shall enable Zero-Copy communication without copying to-be-transferred data. @@ -317,6 +338,7 @@ User friendly API for information exchange :security: NO :safety: QM :satisfies: stkh_req__dev_experience__prog_languages + :satisfied_by: feat__com_communication :status: valid The communication framework shall provide a public API for each supported programming language of S-CORE. @@ -327,6 +349,7 @@ User friendly API for information exchange :security: NO :safety: QM :satisfies: stkh_req__dev_experience__prog_languages + :satisfied_by: feat__com_communication :status: valid Each public API shall support the idioms of the programming language it is written in. @@ -337,6 +360,7 @@ User friendly API for information exchange :security: NO :safety: QM :satisfies: stkh_req__dev_experience__prog_languages + :satisfied_by: feat__com_communication :status: valid Each public API shall use core infrastructure of its programming language and accompanying standard libraries, @@ -354,6 +378,7 @@ Full testability for the user facing API :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid The public API shall be fully mockable. @@ -364,6 +389,7 @@ Full testability for the user facing API :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid The communication framework shall provide a fake binding. @@ -378,6 +404,7 @@ Multi-binding support :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid The communication framework shall support multiple bindings. @@ -391,6 +418,7 @@ Multi-binding support :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid The public API of the communication framework shall be binding-agnostic. @@ -404,6 +432,7 @@ Multi-binding support :security: NO :safety: ASIL_B :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid The association of a service instance and the appropriate binding shall be specified in the deployment configuration. @@ -416,6 +445,7 @@ Cross-VM Extensions :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid :valid_from: v1.0.0 @@ -427,6 +457,7 @@ Cross-VM Extensions :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid :valid_from: v1.0.0 @@ -440,6 +471,7 @@ Cross-VM Extensions :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid :valid_from: v1.0.0 @@ -451,6 +483,7 @@ Cross-VM Extensions :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid :valid_from: v1.0.0 @@ -462,6 +495,7 @@ Cross-VM Extensions :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid :valid_from: v1.0.0 @@ -473,6 +507,7 @@ Cross-VM Extensions :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid :valid_from: v1.0.0 @@ -484,6 +519,7 @@ Cross-VM Extensions :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid :valid_from: v1.0.0 @@ -495,6 +531,7 @@ Cross-VM Extensions :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid :valid_from: v1.0.0 @@ -506,6 +543,7 @@ Cross-VM Extensions :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid :valid_from: v1.0.0 @@ -517,6 +555,7 @@ Cross-VM Extensions :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid :valid_from: v1.0.0 @@ -528,6 +567,7 @@ Cross-VM Extensions :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid :valid_from: v1.0.0 @@ -539,6 +579,7 @@ Cross-VM Extensions :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid :valid_from: v1.0.0 @@ -550,6 +591,7 @@ Cross-VM Extensions :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid :valid_from: v1.0.0 @@ -565,6 +607,7 @@ Dynamic deployment at runtime :security: YES :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid Deployment configuration shall be read from an integrity-checked configuration file at runtime. @@ -578,6 +621,7 @@ Tracing :security: NO :safety: ASIL_B :satisfies: stkh_req__dev_experience__tracing_of_comm, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid The communication framework shall provide infrastructure to enable binding-agnostic, zero-copy, read-only tracing of @@ -592,6 +636,7 @@ Security Impact :security: YES :safety: QM :satisfies: stkh_req__communication__inter_process, stkh_req__dependability__security_features + :satisfied_by: feat__com_communication :status: valid The communication framework shall support an Access Control Lists in the deployment configuration. @@ -602,6 +647,7 @@ Security Impact :security: YES :safety: QM :satisfies: stkh_req__communication__inter_process, stkh_req__dependability__security_features + :satisfied_by: feat__com_communication :status: valid The communication framework shall support an Access Control List per service instance. @@ -612,6 +658,7 @@ Security Impact :security: YES :safety: QM :satisfies: stkh_req__communication__inter_process, stkh_req__dependability__security_features + :satisfied_by: feat__com_communication :status: valid The communication framework shall support an Access Control List for the communication partner offering a service @@ -624,6 +671,7 @@ Security Impact :security: YES :safety: QM :satisfies: stkh_req__communication__inter_process, stkh_req__dependability__security_features + :satisfied_by: feat__com_communication :status: valid The communication framework shall support an Access Control List for the communication partner consuming a service @@ -639,6 +687,7 @@ Safety Impact :security: YES :safety: ASIL_B :satisfies: stkh_req__communication__inter_process, stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid The communication framework shall support safe communication up to ASIL-B. diff --git a/docs/features/communication/ipc/docs/requirements/index.rst b/docs/features/communication/ipc/docs/requirements/index.rst index 41b3220a5dc..b691645195f 100644 --- a/docs/features/communication/ipc/docs/requirements/index.rst +++ b/docs/features/communication/ipc/docs/requirements/index.rst @@ -30,6 +30,7 @@ Requirements :security: NO :safety: QM :satisfies: stkh_req__communication__inter_process,stkh_req__app_architectures__support_data + :satisfied_by: feat__com_communication :status: valid IPC communication shall be possible without copying to-be-transferred data. @@ -40,6 +41,7 @@ Requirements :security: YES :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid The IPC binding shall ensure confidentiality of its communication. @@ -50,6 +52,7 @@ Requirements :security: YES :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid The IPC binding shall ensure integrity of its communication. @@ -60,6 +63,7 @@ Requirements :security: YES :safety: QM :satisfies: stkh_req__communication__inter_process + :satisfied_by: feat__com_communication :status: valid The IPC binding shall ensure availability of its communication, so that the availability is independent per diff --git a/docs/features/communication/some_ip_gateway/requirements/index.rst b/docs/features/communication/some_ip_gateway/requirements/index.rst index c47c740517e..9dc77b86b49 100644 --- a/docs/features/communication/some_ip_gateway/requirements/index.rst +++ b/docs/features/communication/some_ip_gateway/requirements/index.rst @@ -35,6 +35,7 @@ Functional Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__communication__safe + :satisfied_by: feat__com_communication :status: valid The SOME/IP Gateway shall support an interface to plug-in a E2E protection service implementation. @@ -45,6 +46,7 @@ Functional Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__communication__supported_net + :satisfied_by: feat__com_communication :status: valid The SOME/IP protocol implementation shall be fully compatible and complying with the SOME/IP protocol specification from `Open SOME/IP `_. @@ -55,6 +57,7 @@ Functional Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__communication__supported_net + :satisfied_by: feat__com_communication :status: valid The E2E protection implementation shall be fully compatible and complying with the E2E protocol specification from `some-ip.com `_. @@ -65,6 +68,7 @@ Functional Requirements :security: NO :safety: ASIL_B :satisfies: stkh_req__communication__supported_net + :satisfied_by: feat__com_communication :status: valid The Service Discovery implementation shall be fully compatible and complying with the SOME/IP service discovery specification from `Open SOME/IP `_. diff --git a/docs/features/frameworks/feo/requirements/feature_req.rst b/docs/features/frameworks/feo/requirements/feature_req.rst index 433779a4e81..936c379a2db 100644 --- a/docs/features/frameworks/feo/requirements/feature_req.rst +++ b/docs/features/frameworks/feo/requirements/feature_req.rst @@ -32,6 +32,7 @@ Definitions :security: NO :safety: ASIL_B :satisfies: stkh_req__app_architectures__support_time, stkh_req__app_architectures__support_data + :satisfied_by: feat__feo :status: valid An application consists of one or more activities. @@ -49,6 +50,7 @@ Definitions :security: NO :safety: ASIL_B :satisfies: stkh_req__app_architectures__support_time, stkh_req__app_architectures__support_data + :satisfied_by: feat__feo :status: valid Activities are mapped to threads within primary or secondary processes. @@ -66,6 +68,7 @@ Definitions :security: NO :safety: ASIL_B :satisfies: stkh_req__app_architectures__support_time, stkh_req__app_architectures__support_data, stkh_req__execution_model__processes + :satisfied_by: feat__feo :status: valid All activities within an application are arranged within a `Task Chain`. @@ -85,6 +88,7 @@ Definitions :security: NO :safety: ASIL_B :satisfies: stkh_req__app_architectures__support_time, stkh_req__app_architectures__support_data + :satisfied_by: feat__feo :status: valid * Service activities are a means to interact with the outside world, e.g. via @@ -98,6 +102,7 @@ Definitions :security: NO :safety: ASIL_B :satisfies: stkh_req__app_architectures__support_time, stkh_req__app_architectures__support_data + :satisfied_by: feat__feo :status: valid In order to execute activities in secondary processes, the executor makes @@ -121,6 +126,7 @@ Dynamic Architecture :security: NO :safety: ASIL_B :satisfies: stkh_req__app_architectures__support_time, stkh_req__app_architectures__support_data, stkh_req__execution_model__processes + :satisfied_by: feat__feo :status: valid The Application Lifecycle consists of 3 phases: Init, Run and Shutdown. @@ -131,6 +137,7 @@ Dynamic Architecture :security: NO :safety: ASIL_B :satisfies: stkh_req__app_architectures__support_time, stkh_req__app_architectures__support_data, stkh_req__execution_model__processes + :satisfied_by: feat__feo :status: valid Initialization of activities is done during application initialization. @@ -146,6 +153,7 @@ Dynamic Architecture :security: NO :safety: ASIL_B :satisfies: stkh_req__app_architectures__support_time, stkh_req__app_architectures__support_data, stkh_req__execution_model__processes + :satisfied_by: feat__feo :status: valid Each activity is stepped once within each execution of the task chain they belong to. @@ -158,6 +166,7 @@ Dynamic Architecture :security: NO :safety: ASIL_B :satisfies: stkh_req__app_architectures__support_time, stkh_req__app_architectures__support_data, stkh_req__execution_model__processes + :satisfied_by: feat__feo :status: valid Shutdown of activities is done during application shutdown. @@ -175,6 +184,7 @@ Supervision :security: NO :safety: ASIL_B :satisfies: stkh_req__dependability__safety_features_1, stkh_req__app_architectures__support_time, stkh_req__app_architectures__support_data + :satisfied_by: feat__feo :status: valid The framework shall provide the functionality to enable the reporting of @@ -187,6 +197,7 @@ Supervision :security: NO :safety: ASIL_B :satisfies: stkh_req__dependability__safety_features_1, stkh_req__app_architectures__support_time, stkh_req__app_architectures__support_data + :satisfied_by: feat__feo :status: valid The framework shall provide the functionality to enable the reporting of @@ -199,6 +210,7 @@ Supervision :security: NO :safety: ASIL_B :satisfies: stkh_req__dependability__safety_features_1, stkh_req__app_architectures__support_time, stkh_req__app_architectures__support_data + :satisfied_by: feat__feo :status: valid The framework shall provide the functionality to enable the reporting of @@ -211,6 +223,7 @@ Supervision :security: NO :safety: ASIL_B :satisfies: stkh_req__dependability__safety_features_1, stkh_req__app_architectures__support_time, stkh_req__app_architectures__support_data + :satisfied_by: feat__feo :status: valid The framework shall provide mechanisms to check after the computation of @@ -229,6 +242,7 @@ Error Handling for S-CORE v0.5 :security: YES :safety: ASIL_B :satisfies: stkh_req__dependability__safety_features_4, stkh_req__dependability__availability, stkh_req__execution_model__processes + :satisfied_by: feat__feo :status: valid If the primary process receives a termination signal, it shall call the shutdown @@ -243,6 +257,7 @@ Error Handling for S-CORE v0.5 :security: YES :safety: ASIL_B :satisfies: stkh_req__dependability__safety_features_4, stkh_req__dependability__availability, stkh_req__execution_model__processes + :satisfied_by: feat__feo :status: valid If not all secondary processes connect to the primary in time, the primary shall terminate itself. @@ -255,6 +270,7 @@ Error Handling for S-CORE v0.5 :security: YES :safety: ASIL_B :satisfies: stkh_req__dependability__safety_features_4, stkh_req__dependability__availability, stkh_req__execution_model__processes + :satisfied_by: feat__feo :status: valid If an error occurs during the execution of a startup function, the primary process shall abort calling @@ -269,6 +285,7 @@ Error Handling for S-CORE v0.5 :security: YES :safety: ASIL_B :satisfies: stkh_req__dependability__safety_features_4, stkh_req__dependability__availability, stkh_req__execution_model__processes + :satisfied_by: feat__feo :status: valid During initialization (i.e. in the startup function of an activity), activities shall check for resource allocation @@ -281,6 +298,7 @@ Error Handling for S-CORE v0.5 :security: YES :safety: ASIL_B :satisfies: stkh_req__dependability__safety_features_1, stkh_req__dependability__safety_features_4, stkh_req__dependability__availability, stkh_req__execution_model__processes + :satisfied_by: feat__feo :status: valid If a timeout occurs during startup, stepping or shutdown of an activity, the primary process shall shutdown all @@ -293,6 +311,7 @@ Error Handling for S-CORE v0.5 :security: YES :safety: ASIL_B :satisfies: stkh_req__dependability__safety_features_4, stkh_req__dependability__availability, stkh_req__execution_model__processes + :satisfied_by: feat__feo :status: valid If not all activities reach their initialized state within a certain period of time (startup timeout), @@ -305,6 +324,7 @@ Error Handling for S-CORE v0.5 :security: YES :safety: ASIL_B :satisfies: stkh_req__dependability__safety_features_1, stkh_req__dependability__availability, stkh_req__execution_model__processes + :satisfied_by: feat__feo :status: valid If an activity fails in the step function, the primary process shall call shutdown for all activities @@ -317,6 +337,7 @@ Error Handling for S-CORE v0.5 :security: YES :safety: ASIL_B :satisfies: stkh_req__dependability__safety_features_4, stkh_req__dependability__availability, stkh_req__execution_model__processes + :satisfied_by: feat__feo :status: valid If an activity fails in the shutdown function, the primary process shall shutdown all remaining activities diff --git a/docs/features/orchestration/requirements/index.rst b/docs/features/orchestration/requirements/index.rst index 806aa7cc1bf..361bfa2d584 100644 --- a/docs/features/orchestration/requirements/index.rst +++ b/docs/features/orchestration/requirements/index.rst @@ -37,6 +37,7 @@ Task Management :security: NO :safety: QM :satisfies: stkh_req__execution_model__processes + :satisfied_by: feat__orchestration :status: valid The executor shall provide a cooperative task runtime for async programming based on the definition of Rust's async model (see `Asynchronous Programming in Rust `). @@ -47,6 +48,7 @@ Task Management :security: NO :safety: QM :satisfies: stkh_req__execution_model__processes + :satisfied_by: feat__orchestration :status: valid The executor shall provide guidelines for dividing long-running operations into smaller, cooperatively yielding segments. @@ -57,6 +59,7 @@ Task Management :security: NO :safety: QM :satisfies: stkh_req__execution_model__processes + :satisfied_by: feat__orchestration :status: valid The system shall support execution of tasks containing blocking calls on dedicated OS threads isolated from cooperative scheduling. @@ -93,6 +96,7 @@ Thread Pool Configuration :security: NO :safety: QM :satisfies: stkh_req__execution_model__processes + :satisfied_by: feat__orchestration :status: valid Executor instances shall run tasks on a statically configured thread pool with a fixed thread count. @@ -103,6 +107,7 @@ Thread Pool Configuration :security: NO :safety: QM :satisfies: stkh_req__execution_model__processes + :satisfied_by: feat__orchestration :status: valid Threads within an Executor not involved in safety-critical tasks shall share identical OS-level priority. @@ -113,6 +118,7 @@ Thread Pool Configuration :security: NO :safety: QM :satisfies: stkh_req__execution_model__processes + :satisfied_by: feat__orchestration :status: valid Thread affinity to CPU cores shall be configurable per Executor instance. @@ -123,6 +129,7 @@ Thread Pool Configuration :security: NO :safety: QM :satisfies: stkh_req__execution_model__processes + :satisfied_by: feat__orchestration :status: valid Executor instances shall isolate their thread pools from each other. @@ -136,6 +143,7 @@ Task Scheduling :security: NO :safety: QM :satisfies: stkh_req__execution_model__processes + :satisfied_by: feat__orchestration :status: valid Cooperative tasks within an Executor shall execute without internal priority distinctions. @@ -146,6 +154,7 @@ Task Scheduling :security: NO :safety: QM :satisfies: stkh_req__execution_model__processes + :satisfied_by: feat__orchestration :status: valid The Executor shall support FIFO or fairness-based scheduling among cooperative tasks. @@ -156,6 +165,7 @@ Task Scheduling :security: NO :safety: QM :satisfies: stkh_req__execution_model__processes + :satisfied_by: feat__orchestration :status: valid Scaling of Executor resources shall be achieved through additional Executor instances rather than dynamic thread scaling. @@ -172,6 +182,7 @@ Program Definition :security: NO :safety: ASIL_B :satisfies: stkh_req__execution_model__processes, stkh_req__app_architectures__support_time + :satisfied_by: feat__orchestration :status: valid The Orchestrator shall provide a runtime-static Program abstraction representing computation logic as execution graphs. @@ -182,6 +193,7 @@ Program Definition :security: NO :safety: ASIL_B :satisfies: stkh_req__execution_model__processes, stkh_req__app_architectures__support_time + :satisfied_by: feat__orchestration :status: valid Programs shall explicitly define sequential, parallel, conditional execution flows, loops, and timing contracts. @@ -192,6 +204,7 @@ Program Definition :security: NO :safety: ASIL_B :satisfies: stkh_req__execution_model__processes, stkh_req__app_architectures__support_time + :satisfied_by: feat__orchestration :status: valid Programs shall support explicit event-based synchronization and trigger conditions. @@ -202,6 +215,7 @@ Program Definition :security: NO :safety: ASIL_B :satisfies: stkh_req__execution_model__processes, stkh_req__app_architectures__support_time + :satisfied_by: feat__orchestration :status: valid Programs shall contain integrated fault-handling logic and execution monitors to enforce timing constraints. @@ -215,6 +229,7 @@ API Design :security: NO :safety: ASIL_B :satisfies: stkh_req__execution_model__processes, stkh_req__app_architectures__support_time + :satisfied_by: feat__orchestration :status: valid The Orchestrator shall offer a code-first API to integrate directly with application logic without external DSL/IDL. @@ -228,6 +243,7 @@ Execution Model :security: NO :safety: ASIL_B :satisfies: stkh_req__execution_model__processes, stkh_req__app_architectures__support_time + :satisfied_by: feat__orchestration :status: valid Each Program shall be deployed exclusively on a single Executor instance. @@ -238,6 +254,7 @@ Execution Model :security: NO :safety: ASIL_B :satisfies: stkh_req__execution_model__processes, stkh_req__app_architectures__support_time + :satisfied_by: feat__orchestration :status: valid Executors may host multiple Programs to support resource sharing. @@ -248,6 +265,7 @@ Execution Model :security: NO :safety: ASIL_B :satisfies: stkh_req__execution_model__processes, stkh_req__app_architectures__support_time + :satisfied_by: feat__orchestration :status: valid Programs shall communicate exclusively through explicitly defined events. @@ -274,6 +292,7 @@ Observability Requirements :security: NO :safety: QM :satisfies: stkh_req__execution_model__processes, stkh_req__dev_experience__tracing_of_exec + :satisfied_by: feat__orchestration :status: valid The Executor and Orchestrator shall expose structured tracing points correlating user-space task scheduling with OS-level scheduling. @@ -284,6 +303,7 @@ Observability Requirements :security: NO :safety: QM :satisfies: stkh_req__execution_model__processes, stkh_req__dev_experience__tracing_of_exec + :satisfied_by: feat__orchestration :status: valid Observability shall capture task lifecycle events, Executor queue metrics, and mapping of user-space tasks to OS threads. @@ -294,6 +314,7 @@ Observability Requirements :security: NO :safety: QM :satisfies: stkh_req__execution_model__processes, stkh_req__dev_experience__tracing_of_exec + :satisfied_by: feat__orchestration :status: valid Observability shall provide visibility into Program execution flow, event synchronization points, and timing violations. @@ -304,6 +325,7 @@ Observability Requirements :security: NO :safety: QM :satisfies: stkh_req__execution_model__processes, stkh_req__dev_experience__tracing_of_exec + :satisfied_by: feat__orchestration :status: valid Tracing points shall integrate seamlessly with established tracing frameworks like Perfetto and LTTng. @@ -317,6 +339,7 @@ External Supervision Requirements :security: NO :safety: QM :satisfies: stkh_req__execution_model__processes + :satisfied_by: feat__orchestration :status: valid Executor and Orchestrator frameworks shall expose health indicators for integration with external supervisory systems. @@ -327,6 +350,7 @@ External Supervision Requirements :security: NO :safety: QM :satisfies: stkh_req__execution_model__processes + :satisfied_by: feat__orchestration :status: valid Frameworks shall internally verify task-level health status based on timing constraints and fault-handling execution. @@ -340,6 +364,7 @@ General Constraints :security: NO :safety: QM :satisfies: stkh_req__execution_model__processes + :satisfied_by: feat__orchestration :status: valid The Executor and Orchestrator shall maintain determinism and scalability suitable for mixed-criticality environments. diff --git a/docs/modules/feo/feo/docs/requirements/component_requirements.rst b/docs/modules/feo/feo/docs/requirements/component_requirements.rst index a5d87adfee9..e5e52184d30 100644 --- a/docs/modules/feo/feo/docs/requirements/component_requirements.rst +++ b/docs/modules/feo/feo/docs/requirements/component_requirements.rst @@ -29,6 +29,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__application + :satisfied_by: comp__feo_main :status: valid An application consists of one or more activities executed in one or multiple operating system processes. @@ -46,6 +47,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__activity + :satisfied_by: comp__feo_main :status: valid Each activitiy is mapped to exactly one thread within the primary or one of the secondary processes. @@ -62,6 +64,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__task_chain + :satisfied_by: comp__feo_main :status: valid All activities within an application are arranged within a `Task Chain`. @@ -82,6 +85,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__application, feat_req__feo__agent + :satisfied_by: comp__feo_main :status: valid The component shall implement a scheduler (aka executor) that manages the execution of activities in correct order. @@ -93,6 +97,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__service_activity + :satisfied_by: comp__feo_main :status: valid The component shall enable the implementation and execution of Service Activities, which are a means to interact @@ -108,6 +113,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__agent + :satisfied_by: comp__feo_main :status: valid In order to execute activities in secondary processes, the Scheduler shall use agents running in the secondary @@ -125,6 +131,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__activity_init, feat_req__feo__activitiy_step, feat_req__feo__activity_shutdown, feat_req__feo__activity + :satisfied_by: comp__feo_main :status: valid Each activity shall be mapped to one thread. The mapping cannot be changed at runtime. @@ -137,6 +144,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__application_lifecycle + :satisfied_by: comp__feo_main :status: valid The Application Lifecycle shall consists of 3 phases: Init, Run and Shutdown. @@ -148,6 +156,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__activity_init + :satisfied_by: comp__feo_main :status: valid Initialization of Activities shall be done during application initialization. @@ -162,6 +171,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__activitiy_step, feat_req__feo__activity_init, feat_req__feo__activity + :satisfied_by: comp__feo_main :status: valid Each Activity shall be stepped once within each execution of the Task Chain they belong to. @@ -175,6 +185,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__activity_shutdown + :satisfied_by: comp__feo_main :status: valid Shutdown of activities shall be done during application shutdown. @@ -189,6 +200,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__activity, feat_req__feo__task_chain + :satisfied_by: comp__feo_main :status: valid The component shall provide a configuration mechanism that supports configuring @@ -204,6 +216,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__activity + :satisfied_by: comp__feo_main :status: valid It shall be possible to define the component configuration in a pre-defined configuration file. @@ -215,6 +228,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__activity + :satisfied_by: comp__feo_main :status: valid The mapping of activities to threads is done in the component configuration and cannot be changed at runtime. @@ -226,6 +240,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__alive_supervision + :satisfied_by: comp__feo_main :status: valid The component shall provide the functionality to enable the reporting of @@ -239,6 +254,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__deadline_supervision + :satisfied_by: comp__feo_main :status: valid The component shall provide the functionality to enable the reporting of @@ -252,6 +268,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__logical_supervision + :satisfied_by: comp__feo_main :status: valid The component shall provide the functionality to enable the reporting of @@ -265,6 +282,7 @@ FEO Component Requirements :security: NO :safety: ASIL_B :satisfies: feat_req__feo__trustable_computation + :satisfied_by: comp__feo_main :status: valid The component shall provide mechanisms to check after the computation of @@ -282,6 +300,7 @@ Error Handling for S-CORE v0.5 :security: YES :safety: ASIL_B :satisfies: feat_req__feo__response_term_request + :satisfied_by: comp__feo_main :status: valid If the primary process receives a termination signal, it shall call the shutdown @@ -296,6 +315,7 @@ Error Handling for S-CORE v0.5 :security: YES :safety: ASIL_B :satisfies: feat_req__feo__secondary_conn_timeout + :satisfied_by: comp__feo_main :status: valid If not all secondary processes connect to the primary in time, the primary shall terminate itself. @@ -308,6 +328,7 @@ Error Handling for S-CORE v0.5 :security: YES :safety: ASIL_B :satisfies: feat_req__feo__act_startup_error + :satisfied_by: comp__feo_main :status: valid If an error occurs during the execution of a startup function, the primary process shall abort calling @@ -322,6 +343,7 @@ Error Handling for S-CORE v0.5 :security: YES :safety: ASIL_B :satisfies: feat_req__feo__act_alloc_error + :satisfied_by: comp__feo_main :status: valid During initialization (i.e. in the startup function of an activity), activities shall check for resource allocation @@ -334,6 +356,7 @@ Error Handling for S-CORE v0.5 :security: YES :safety: ASIL_B :satisfies: feat_req__feo__act_timeout + :satisfied_by: comp__feo_main :status: valid If a timeout occurs during startup, stepping or shutdown of an activity, the primary process shall shutdown all @@ -346,6 +369,7 @@ Error Handling for S-CORE v0.5 :security: YES :safety: ASIL_B :satisfies: feat_req__feo__startup_timeout + :satisfied_by: comp__feo_main :status: valid If not all activities reach their initialized state within a certain period of time (startup timeout), @@ -358,6 +382,7 @@ Error Handling for S-CORE v0.5 :security: YES :safety: ASIL_B :satisfies: feat_req__feo__act_stepping_error + :satisfied_by: comp__feo_main :status: valid If an activity fails in the step function, the primary process shall call shutdown for all activities @@ -370,6 +395,7 @@ Error Handling for S-CORE v0.5 :security: YES :safety: ASIL_B :satisfies: feat_req__feo__act_shutdown_error + :satisfied_by: comp__feo_main :status: valid If an activity fails in the shutdown function, the primary process shall shutdown all remaining activities